[SERVER-26986] Drop all connections when transitioning to ROLLBACK or REMOVED states Created: 10/Nov/16  Updated: 14/Nov/16  Resolved: 14/Nov/16

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Mathias Stearn Assignee: Mathias Stearn
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-24574 Tag internal connections KeepOpen to ... Closed
Operating System: ALL
Sprint: Repl 2016-11-21
Participants:

 Description   

Whenever we transition out of PRIMARY, or into ROLLBACK or REMOVED, we call a function to close all connections. With SERVER-24574, however, that call now only closes non-internal connections, where it used to close all connections.
We should think about whether or not this is safe for transitions to ROLLBACK or REMOVED, and may want to just go ahead and close all (including internal) connections in those cases as it is much easier to reason about the system if you don't have to worry about time going backwards on a single connection.



 Comments   
Comment by Mathias Stearn [ 14/Nov/16 ]

We decided that connection dropping cannot be correctly used to detect ROLLBACK or REMOVED transitions.

Comment by Mathias Stearn [ 10/Nov/16 ]

I put this in 3.3 Required so we can make the decision before we have a stable release that with this behavior.

Generated at Thu Feb 08 04:13:48 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.