[SERVER-1679] need to be a way to quickly detect a loss of primary state in a replica set if one is not calling getlasterror Created: 25/Aug/10  Updated: 12/Jul/16  Resolved: 16/Nov/10

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

Type: Improvement Priority: Major - P3
Reporter: Dwight Merriman Assignee: Dwight Merriman
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to JAVA-275 with default write concern (no getLas... Closed
Participants:

 Description   

it would be bad to do writes for an hour and then discover the node transitioned to secondary 59 minutes ago.

of course one call getlasterror today, but this is solveable without that so we should do it.

one possible solution: close all connections on a transition from primary->secondary.



 Comments   
Comment by Dwight Merriman [ 16/Nov/10 ]

sockets now close on stepdown

Comment by auto [ 04/Oct/10 ]

Author:

{'login': 'dwight', 'name': 'Dwight', 'email': 'dwight@10gen.com'}

Message: SERVER-1679 need to be a way to quickly detect a loss of primary state in a replica set if one is not calling getlasterror
http://github.com/mongodb/mongo/commit/eedcd0f469a95427865634441fc81ed9018d3e71

Generated at Thu Feb 08 02:57:43 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.