Closed samiahlroos closed 2 months ago
works with https://github.com/ihanick/anydbver/releases/tag/v0.1.6
anydbver deploy node0 psmdb:latest,replica-set=rs0,role=shard node1 psmdb:latest,replica-set=rs0,role=shard,master=node0 node2 psmdb:latest,replica-set=rs0,role=shard,master=node0 node3 psmdb:latest,replica-set=rs1,role=shard node4 psmdb:latest,replica-set=rs1,role=shard,master=node3 node5 psmdb:latest,replica-set=rs1,role=shard,master=node3 node6 psmdb:latest,replica-set=cfg0,role=cfg node7 psmdb:latest,replica-set=cfg0,role=cfg,master=node6 node8 psmdb:latest,replica-set=cfg0,role=cfg,master=node6 node9 psmdb:latest mongos-cfg:cfg0/node6,node7,node8 mongos-shard:rs0/node0,node1,node2,rs1/node3,node4,node5
When creating a sharded cluster like this:
anydbver creates /etc/rs0-keyfile on shard servers and /etc/cfg0-keyfile on config. File name doesn't matter, but content does, and shard servers have different content from config. This results in sh.addShard() failing.
Copying keyFile contents from cfg to shard servers and restarting fixes it.