db-authentication rolling-restart-parallel database mongo
command is dependent on show database parallel-upgrade-plan
.
If show database parallel-upgrade-plan
does not provide any output, then do not use db-authentication rolling-restart-parallel database mongo
. Instead use db-authentication rolling-restart database mongo
command.
Example: If show database parallel-upgrade-plan
displays the following output:
admin@orchestrator[an-dbmaster]# show database parallel-upgrade-plan
BATCH MODULE HOST ADDRESS
------------------------------------------------------
1 mongo-node-101 an-dbmaster 192.168.11.40
1 mongo-node-102 an-dbcontrol-0 192.168.11.41
1 mongo-node-103 an-dbcontrol-1 192.168.11.42
2 mongo-node-104 an-pers-db-0 192.168.11.43
3 mongo-node-105 an-pers-db-1 192.168.11.44
then, db-authentication rolling-restart-parallel database mongo
combines 101, 102 and 103 in batch 1 and restarts all of them at the same time.
After batch 1, node 104 from batch 2 is restarted followed by node 105 (from batch 3). So, all the nodes from same batch are
restarted in parallel. However nodes from different batch are restarted in sequential manner.
A batch_interval parameter can be added as follows:
admin@orchestrator[an-master]# db-authentication rolling-restart-parallel batch_interval 8
database mongo
where, batch_interval is an integer and accepts range between 8 to 60. By default, the value is 10. It represents the delay
duration in seconds between processing of 2 subsequent batches. After executing this command, batch-wise status can be tracked
using db-authentication rolling-restart-parallel-status database mongo
command.