{"id":10522,"date":"2021-03-15T09:00:07","date_gmt":"2021-03-15T16:00:07","guid":{"rendered":"https:\/\/www.couchbase.com\/blog\/?p=10522"},"modified":"2021-09-03T15:30:58","modified_gmt":"2021-09-03T22:30:58","slug":"upgrading-couchbase-community-edition","status":"publish","type":"post","link":"https:\/\/www.couchbase.com\/blog\/es\/upgrading-couchbase-community-edition\/","title":{"rendered":"Actualizaci\u00f3n de Couchbase Community Edition"},"content":{"rendered":"

Why Enterprise Edition<\/h4>\n

Couchbase Server is generally available in three flavors: Community Edition (CE), Enterprise Edition (EE) and Couchbase Cloud (DBaaS).\u00a0 Many customers start with Community Edition. They download CE and use it completely free to run development, test and production workloads. CE includes some basic availability, security and performance features. However, EE can be useful for heavy production workloads. For instance, CE has limited concurrency (maximum of 4 cores per node). Index replicas are not available. Analytics and Eventing services are not available.\u00a0 CE doesn’t have multi-dimensional scaling (MDS) and supports only the following combinations of services on the nodes: “Data”<\/strong>, “Data, Index, Query”<\/strong>, “Data, Index, Query, Full Text Search”<\/strong>. For more information check out a detailed comparison of Community and Enterprise editions.<\/p>\n

Upgrading From Couchbase Community Edition<\/h4>\n

What if you are already using Community Edition and want to upgrade to Enterprise? The easiest option would be to setup a separate EE cluster and use XDCR (Cross Data Center Replication) to move data from one cluster to another. However, provisioning a new EE cluster might be costly and time consuming, especially for on-premises deployments. In that case, another option would be to run a rolling online upgrade.\u00a0 Some CE to EE upgrade considerations<\/a>\u00a0 are available in Couchbase documentation.<\/p>\n

Show Me How to Upgrade<\/h4>\n

For this blog article I recorded a short video about upgrading Couchbase Community Edition cluster. I followed the rolling online upgrade process with an extra spare node. To make the upgrade more realistic, I ran a N1QL workload simulator (a program called n1qlback<\/a>) throughout the whole upgrade process. I used the standard travel-sample bucket with 10 global secondary indexes (GSI) . One of the objectives of this test was to show that there would be no interruption or errors for the query flow while dropping and re-creating indexes, adding and removing nodes with different editions of Couchbase. Below is the list of upgrade steps.<\/p>\n

    \n
  1. Add one extra EE node into the CE cluster<\/li>\n
  2. Re-create secondary indexes from one of the CE nodes over to the EE node.<\/li>\n
  3. Drop the secondary indexes on the CE node<\/li>\n
  4. Remove a CE node from the cluster.<\/li>\n
  5. Uninstall CE on the removed node and install EE.<\/li>\n
  6. Bring EE node back into the cluster.<\/li>\n
  7. Repeat this process for other CE nodes.<\/li>\n<\/ol>\n