draft-1

Author: rao-shwe

modules/ROOT/nav.adoc

@@ -325,7 +325,8 @@ include::cli:partial$cbcli/nav.adoc[]
    **** xref:rest-api:rest-name-node.adoc[Naming a Node]
    **** xref:rest-api:rest-configure-memory.adoc[Configuring Memory]
    **** xref:rest-api:rest-get-memory-information.adoc[Getting Memory Information]
-   **** xref:rest-api:rest-set-up-services.adoc[Assigning Services]
+   **** xref:rest-api:rest-set-up-services.adoc[Assigning Services to a New Node]
+   **** xref:rest-api:rest-set-up-services-existing-nodes.adoc[Assigning Services to an Existing Node]
    **** xref:rest-api:rest-name-cluster.adoc[Naming a Cluster]
 
    *** xref:rest-api:rest-adding-and-removing-nodes.adoc[Node Addition and Removal]

modules/introduction/partials/new-features-80.adoc

@@ -59,6 +59,23 @@ curl --get -u <username:password> \
     -d clusterLabels=none|uuidOnly|uuidAndName
 ----
 
+[#section-new-feature-800-services]
+=== Services
+
+https://jira.issues.couchbase.com/browse/MB-60349[MB-60349]::
+Now you can add or remove non-Data Services dynamically on existing nodes in a cluster, without adding or removing nodes.
+Rebalancing is automatically triggered to evenly distribute service workloads.
+These are the services that can be modified:
+
+** `index` (Index Service)
+** `n1ql` (Query Service)
+** `fts` (Search Service)
+** `cbas` (Analytics Service)
+** `eventing` (Eventing Service)
+** `backup` (Backup Service)
+
+You can modify these services using the Couchbase xref:manage:manage-nodes/modify-services-on-nodes-and-rebalance.adoc#modify-mds-services-from-ui[UI], xref:rest-api:rest-set-up-services-existing-nodes.adoc[REST API], or xref:manage:manage-nodes/modify-services-on-nodes-and-rebalance.adoc#modify-mds-services-using-cli[CLI].
+
 [#section-new-feature-data-service]
 === Data Service
 

modules/learn/pages/clusters-and-availability/nodes.adoc

@@ -87,9 +87,8 @@ Alternatively, the default itself can be changed, provided that it does not requ
 The available node must be at stage 2 or 3: that is, it must have been started, and may have had its data, index, analytics, and eventing paths configured.
 However, it cannot have been provisioned in any way: if the routine for joining is executed on a provisioned node, an error is flagged, and the operation fails.
 +
-Note that services can nevertheless be assigned to the new node during the join operation itself.
-The
-memory quota for each service defaults to the setting for the existing cluster.
+NOTE: Services can be assigned to the new node during the join operation or on-demand.
+The memory quota for each service defaults to the setting for the existing cluster.
 An error occurs if the new node does not have sufficient memory.
 +
 If Couchbase Web Console is used to perform the join, the data, index, analytics, and eventing paths can be modified as part of the join operations.
@@ -150,14 +149,25 @@ Fast failover can be achieved by deploying an arbiter node, which is a node that
 Such a deployment ensures that the Cluster Manager automatically deploys critical system infrastructure on the arbiter node, rather than on any other, so as to avoid clashes.
 This may lead to several seconds of latency reduction, when a busy cluster undergoes failover.
 
-For information about service deployment with:
+=== Deploying Services on a Node
 
-* The REST API, see xref:rest-api:rest-set-up-services.adoc[Assigning Services].
+You can add services to a new node when adding the node to a cluster.
+
+You can also add or remove non-Data Services on an existing node in a cluster, without adding or removing nodes.
+
+For information about the deployment of services on a new node using:
+
+* The REST API, see xref:rest-api:rest-set-up-services.adoc[Assigning Services to a New Node].
 
 * Couchbase Server Web Console during node-addition and node-joining, see the demonstrated uses of checkboxes, in xref:manage:manage-nodes/add-node-and-rebalance#arbiter-node-addition[Add a Node and Rebalance] and in xref:manage:manage-nodes/join-cluster-and-rebalance#arbiter-node-join[Join a Cluster and Rebalance].
 
 * The CLI during node-addition, see xref:cli:cbcli/couchbase-cli-server-add[server-add].
 
+For information about adding or removing non-Data Services on an existing node in a cluster, using:
+
+* The xref:manage:manage-nodes/modify-services-on-nodes-and-rebalance.adoc#modify-mds-services-from-ui[UI] and xref:manage:manage-nodes/modify-services-on-nodes-and-rebalance.adoc#modify-mds-services-using-cli[CLI], see xref:manage:manage-nodes/modify-services-and-rebalance.adoc[Modify Services and Rebalance].
+* The REST API, see xref:rest-api:rest-set-up-services-existing-nodes.adoc[Assigning Services to an Existing Node].
+
 [#Node Quantity]
 == Node Quantity
 

modules/learn/pages/services-and-indexes/services/analytics-service.adoc

@@ -112,9 +112,13 @@ This continuous data ingestion allows operational and analytic queries to run co
 
 Due to the large scale and duration of operations it is likely to perform, the Analytics Service should be run _alone_, on its node or nodes in the cluster, _with no other Couchbase Service running on the Analytics nodes_.
 
-For the practical steps required to initialize or join a cluster, and to deploy services, see
-xref:manage:manage-nodes/create-cluster.adoc[Create a Cluster].
-For information on how to run analytic queries, see the xref:analytics:introduction.adoc[Introduction] to Couchbase Analytics.
+For more information about:
+
+* Initializing a cluster, see xref:manage:manage-nodes/create-cluster.adoc[Create a Cluster].
+
+* Adding or removing services on a node, see xref:manage:manage-nodes/modify-services-and-rebalance.adoc[Modify Services and Rebalance].
+
+* How to run analytic queries, see the xref:analytics:introduction.adoc[Introduction] to Couchbase Analytics.
 
 [WARNING]
 .Non-Uniform Memory Access (NUMA)
@@ -125,3 +129,7 @@ NUMA architectures divide memory into different zones, each with a specific CPU,
 Couchbase Analytics is not configured to align with the NUMA architecture.
 Deploying Couchbase Analytics on a server with the NUMA architecture may result in uneven memory distribution, increased latency, and degraded performance. Specifically, queries can become slower, and overall system efficiency can drop as memory access times vary significantly.
 ====
+
+== See Also
+
+* For information about adding or removing an Analytics Service on a node, see xref:manage:manage-nodes/modify-services-and-rebalance.adoc[Modify Services and Rebalance].

modules/learn/pages/services-and-indexes/services/backup-service.adoc

@@ -44,7 +44,7 @@ the Cluster Manager elects one of them to be the leader.
 The leader is responsible for:
 
 * Dispatching backup tasks.
-* Adding and removing nodes from the Backup Service.
+* Adding and removing the Backup Service on nodes.
 * Cleaning orphaned tasks.
 * Ensuring that all Backup Service nodes can reach the global storage locations.
 
@@ -224,3 +224,4 @@ You may want to experiment with different thread settings to find a balance betw
 * See xref:rest-api:backup-rest-api.adoc[Backup Service API] for information about using the Backup Service from the REST API.
 * To learn about the port numbers the Backup Service uses, see xref:install:install-ports.adoc[Couchbase Server Ports].
 * For a list of Backup Service audit events, see xref:audit-event-reference:audit-event-reference.adoc[Audit Event Reference].
+* For information about adding or removing a Backup Service on a node, see xref:manage:manage-nodes/modify-services-and-rebalance.adoc[Modify Services and Rebalance].

modules/learn/pages/services-and-indexes/services/data-service.adoc

@@ -48,8 +48,9 @@ For further information, see xref:buckets-memory-and-storage/memory.adoc[Memory]
 For information on how to activate, see
 xref:manage:manage-buckets/flush-bucket.adoc[Flush a Bucket].
  ** *Expiry Pager*: Scans for items that have expired, and erases them from memory and disk; after which, a _tombstone_ remains for a default period of 3 days.
-The expiry pager runs every 10 minutes by default: for information on changing the interval, see `cbepctl` xref:cli:cbepctl/set-flush_param.adoc[set flush_param].
-For more information on item-deletion and tombstones, see xref:data/expiration.adoc[Expiration].
+The expiry pager runs every 10 minutes by default.
+For information about changing the interval, see xref:rest-api:rest-bucket-create.adoc#expirypagersleeptime[expiryPagerSleepTime].
+For more information about item-deletion and tombstones, see xref:data/expiration.adoc[Expiration].
  ** *Batch Reader*: Enhances performance by combining changes made to multiple items into _batches_, which are placed on the disk queue, to be written to disk.
 * *Scheduler*: A pool of threads mainly used for handling I/O.
 The threads are divided into four kinds, which run independently of and without effect on one another:
@@ -61,3 +62,10 @@ The threads are divided into four kinds, which run independently of and without
 
 +
 For more information on the Data Service' threading model, see xref:buckets-memory-and-storage/storage-settings.adoc[Storage Properties].
+
+
+To add or remove a data service on a node:
+
+. xref:manage:manage-nodes/remove-node-and-rebalance.adoc[Remove a Node and Rebalance].
+
+. Then xref:manage:manage-nodes/add-node-and-rebalance.html[add the node] back to the cluster along with adding or removing the data service.

modules/learn/pages/services-and-indexes/services/eventing-service.adoc

@@ -13,3 +13,5 @@ Events include changes made to specified items, and the arrival of scheduled poi
 The Eventing Service depends on the xref:services-and-indexes/services/data-service.adoc[Data Service], which must therefore be running on at least one cluster node.
 
 For information on using the Eventing Service, see xref:eventing:eventing-overview.adoc[Eventing Service: Fundamentals].
+
+For information about adding or removing an Eventing Service on a node, see xref:manage:manage-nodes/modify-services-and-rebalance.adoc[Modify Services and Rebalance].

modules/learn/pages/services-and-indexes/services/index-service.adoc

@@ -68,3 +68,7 @@ _Secondary_ Indexes, often referred to as _Global Secondary Indexes_ or _GSIs_,
 Secondary Indexes can be created on specified fields; placed on specific cluster-nodes; and replicated.
 
 For information on using the Indexing Service, see xref:indexes:indexing-overview.adoc[].
+
+== See Also
+
+* For information about adding or removing an Index Service on a node, see xref:manage:manage-nodes/modify-services-and-rebalance.adoc[Modify Services and Rebalance].

modules/learn/pages/services-and-indexes/services/query-service.adoc

@@ -43,3 +43,7 @@ Note the degree of parallelism with which operations are frequently performed, r
 The Query Service supports queries made in {sqlpp}.
 As well as providing a rich variety of query-options, {sqlpp} allows statements to be _prepared_, so that the parsing and compiling of plans is completed prior to execution; and permits _consistency-levels_ to be configured.
 For detailed information, see xref:n1ql:n1ql-language-reference/index.adoc[{sqlpp} Language Reference].
+
+== See Also
+
+* For information about adding or removing a Query Service on a node, see xref:manage:manage-nodes/modify-services-and-rebalance.adoc[Modify Services and Rebalance].

modules/learn/pages/services-and-indexes/services/search-service.adoc

@@ -64,3 +64,7 @@ In Couchbase Server 6.6 Enterprise Edition and later, the _Flex Index_ feature p
 For detailed information, see xref:n1ql:n1ql-language-reference/flex-indexes.adoc[Flex Indexes].
 
 To use the Search Service in {sqlpp}, the Query, Index, and Search Services must all be running on the cluster.
+
+== See Also
+
+* For information about adding or removing a Search Service on a node, see xref:manage:manage-nodes/modify-services-and-rebalance.adoc[Modify Services and Rebalance].