[SERVER-29638] Improve the error message when unable to reach any nodes in a replica set - MongoDB Jira

XML

Word

Printable

Details

Type: Improvement
Status: Closed
Priority: Major - P3
Resolution: Fixed
Affects Version/s: None
Fix Version/s: 3.5.10
Component/s: Logging
Labels:
- neweng
- platforms-interns-2017

Backwards Compatibility:
Fully Compatible
Sprint:
Platforms 2017-07-10

Description

The following error:

"No primary detected for set Cluster0-shard-0 2017-06-14T00:00:00.000-0800 I NETWORK [ReplicaSetMonitor-TaskExecutor-0]
All nodes for set Cluster0-shard-0 are down."

should say instead print something more like the following:

"Unable to reach primary for set Cluster0-shard-0 2017-06-14T00:00:00.000-0800 I NETWORK [ReplicaSetMonitor-TaskExecutor-0]
All nodes for set Cluster0-shard-0 are unreachable".

Attachments

Activity

People

Assignee:: Tyler Kaye

Reporter:: Justin Cohler

Participants:: Githook User, Justin Cohler, Osmar Olivo, Tyler Kaye

Votes:: 0 Vote for this issue

Watchers:: 4 Start watching this issue

Dates

Created:: Jun 14 2017 09:15:39 PM UTC

Updated:: Oct 12 2017 08:59:00 PM UTC

Resolved:: Jun 20 2017 09:20:29 PM UTC