Replace production couch node 1 #6116
Conversation
dannyroberts
force-pushed
the
dmr/replace-production-couch-node-1
branch
from
b72266b
to
bf6d105
Compare
dannyroberts
force-pushed
the
dmr/replace-production-couch-node-1
branch
from
bf6d105
to
387d2a8
Compare
| @@ -0,0 +1,2 @@ | |||
| target_allocation: | |||
There was a problem hiding this comment.
Curious what this file is used for?
There was a problem hiding this comment.
In https://confluence.dimagi.com/display/saas/Replace+a+Couch+node+in+Couch+cluster, it's the PLAN_FILE that is used in phase 2.
There was a problem hiding this comment.
Taking a stab at answering this cause why not 😅 I believe we reference this migration file when running cchq ${ENV} migrate-couchdb ${PLAN_FILE} plan in phase 2 of adding this node. And then it looks like that file is used to allocate shards properly via couchdb-cluster-admin.
So then the syntax here is saying that we have three nodes and should make three copies of data across these nodes, which might be the same as saying 1 copy per node?
There was a problem hiding this comment.
Dang Danny beat me to it haha
There was a problem hiding this comment.
Yeah but you said it better, Graham :)
There was a problem hiding this comment.
Thanks @dannyroberts and @gherceg. That was super helpful :)
https://dimagi-dev.atlassian.net/browse/SAAS-14844
This PR will be applied using Phase 2 of https://confluence.dimagi.com/display/saas/Replace+a+Couch+node+in+Couch+cluster (applied to just this one node replacement).
Environments Affected
production