[SERVER-10540] "couldn't update slave" error messages are not meaningful Created: 16/Aug/13  Updated: 11/Jul/16  Resolved: 09/Sep/13

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

Type: Improvement Priority: Minor - P4
Reporter: Thomas Rueckstiess Assignee: Matt Dannenberg
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Backwards Compatibility: Minor Change
Participants:

 Description   

Change the two error messages in rs_sync.cpp to make them more meaningful and explain better what the problem is.

OCCASIONALLY warning() << "couldn't update slave " << rid << " no entry" << rsLog;
OCCASIONALLY log() << "couldn't update slave " << rid << " not init" << rsLog;



 Comments   
Comment by auto [ 09/Sep/13 ]

Author:

{u'username': u'dannenberg', u'name': u'matt dannenberg', u'email': u'matt.dannenberg@10gen.com'}

Message: SERVER-10540 better error message now
Branch: master
https://github.com/mongodb/mongo/commit/a6f6542f067500a1bea72ef5da723367418a6fe6

Generated at Thu Feb 08 03:23:26 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.