[SERVER-26683] Log the error which causes a node to be marked as failed in the replica set monitor Created: 18/Oct/16  Updated: 01/Nov/16  Resolved: 24/Oct/16

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 3.2.10, 3.4.0-rc0
Fix Version/s: 3.4.0-rc2

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

Backwards Compatibility: Fully Compatible
Backport Completed:
Sprint: Sharding 2016-10-31
Participants:

 Description   

There are various code paths in sharding currently which mark replica set nodes as failed in the replica set monitor, but we never log it. We should include logging for better diagnostics.



 Comments   
Comment by Githook User [ 01/Nov/16 ]

Author:

{u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}

Message: SERVER-26683 Log reason for marking repl hosts as failed in the RSM

(backport of commit c0fe7490ed8482c5244a36196253883d3c50e7c7)
Branch: v3.2
https://github.com/mongodb/mongo/commit/819946a376ba70cb6451a61695dcce42084f3863

Comment by Githook User [ 24/Oct/16 ]

Author:

{u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}

Message: SERVER-26683 Log reason for marking repl hosts as failed in the RSM
Branch: master
https://github.com/mongodb/mongo/commit/c0fe7490ed8482c5244a36196253883d3c50e7c7

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