Step 1: Verify Cluster Readiness for a Patch
Before you apply a patch, check that the cluster is ready for a patch to be applied. In addition to the prerequisites, consider verifying that the cluster utilizes best practices which will facilitate a more optimal patch installation.
Patch Install Prerequisites
Before you apply a patch on the cluster, verify that all CLDB nodes are running and that container 1 is fully replicated on each CLDB node.
Run maprcli dump containerinfo -ids 1 -json
. In the output, all CLDBs
should be listed under ActiveServers
and each node should report a VALID
state.
...
"data":[
{
"ContainerId":1,
"Epoch":3,
"Master":"<masterCLDB_IP>:5660--3-VALID",
"ActiveServers":{
"IP:Port":[
"<masterCLDB_IP>:5660--3-VALID",
"<slaveCLDB_IP>:5660--3-VALID",
"<slaveCLDB_IP>:5660--3-VALID"
]
},
"InactiveServers":{
},
"UnusedServers":{
},
...
For more information, see dump containerinfo
Best Practices for Patch Installation
- The volume min replication setting should be greater than or equal to 2 for CLDB volume.
- This ensures that container 1 always has at least two valid copies. Run the
following command to list the current replication setting:
maprcli dump volumeinfo -volumename mapr.cldb.internal -json
- No under replicated volumes should exist on the cluster.
- Run the following command to check for under-replicated volumes:
For more information, see maprcli alarm list.maprcli alarm list
- Each CLDB node should be configured to have a minimum of 3 disks in its storage pool.
- Run the following command on each CLDB node to get a list of the disks configured
for each storage pool:
mrconfig sp list [-v]