|
garo, we're working on this issue in SERVER-6376 with intention to prevent dropping connections in all cases where it is possible – in certain cases it's unavoidable (where the primary may be caused to change or a node's visibility may change). Watch that ticket as we'll update as it progresses.
|
|
Still hoping that this would resolved in the future. Having the cluster dropping primary when it's not really needed gives the DBA and ops team unnecessary problems and downtime when maintaining the cluster.
|
|
We will still probably want to close all connections on the removed node, but we shouldn't need to close them on the primary or secondaries that didn't have their config changed.
|
|
Yes, this was by design to be overly cautious when we first implemented Replica Sets, but you're right, this is probably unnecessary now and could be removed.
|
Generated at Thu Feb 08 03:12:36 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.