Module 4 - Initialize and Provision a Couchbase Node_01 - Hands-on Couchbase DBA | Kishore Uppala

[Music] hi friends welcome back in this module uh we are going to discuss about these bullet points how to set up a couch-based node it involves two phases initialization and provision a walkthrough on adding and removing nodes and we will also discuss about the failover and failover types and how to rebalance the cluster and when a rebalance usually pops up in the cluster that we are going to see and recovering a node post failover we will also discuss about the types of failover delta and full and we can also see use of server groups in couch base so initialization versus provisioning after installation and starting of the couch-based server a node must be initialized and provisioned so basically what happens in initialization phase so we will define the disk path for all the services we are going to use like data index query eventing and analytic service we define the path so basically we use same path on all the nodes of the cluster if you want you can give individual paths for each node that you can define in the initialization phase provisioning phase all the details including full administration credentials and the list of services you are going to assign for that specific node and the memory quota definition are established in the provision stage initialization can be performed explicitly and independently of provisioning as prior process in order to have create custom disk paths here is a command to initialize a node with click you need to provide data path index path and analytics path like this along with cluster admin credentials this is the expected message post successful initialization of the node initializing a node with rest api we are using post method and calling node slash self slash controller settings and we are providing the paths like this if you see here the flash is represented as percentage to f the path is slash or pt slash couch space slash wire slash slip slash couch base slash data like this we are providing paths for index analytics and eventing services so this command initializes the disk paths for data index analytics and eventing service provisioning keynotes credentials and memory allocations are inherited which means if you provide credentials admin credentials that will be inherited suppose you allocated data service for a node with specific memory settings and if you are adding one more data service node the same memory settings will be inherited for that node as well service assignments are made independent for each node which means you can allocate different types of services for each and individual node independently you can assign data service for one node in the cluster you can assign index and query services combined to a different node this is the command to provision a node with cli so we are providing admin credentials and services field we are allocating data index query services with a cluster ram size of 512 mb this cluster ram size means for the data service cluster index ram size is 256 mb so for the data service we are allocating 512 mb ram and for index service we are allocating 256 mb ram query service doesn't require any ram and this question can be asked in the interviews as well whether query service require any ram or not no it doesn't provision a node with the rest api these are the service flags for each service so if you want to allocate data service you can call it as kb these are the specific flags for each and individual service again using post method here in hyphen d services we are allocating kb which is nothing but data service nickel which is nothing but query service index which is nothing but index service after that in this specific call command we are allocating memory quota 256 for data service index memory quota 256 mb for index service and nickel which is query service doesn't need any ram in the next video we can see how to practically initialize and provision a node