[SERVER-29638] Improve the error message when unable to reach any nodes in a replica set Created: 14/Jun/17 Updated: 30/Oct/23 Resolved: 20/Jun/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Logging |
| Affects Version/s: | None |
| Fix Version/s: | 3.5.10 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Justin Cohler | Assignee: | Tyler Kaye |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | neweng, platforms-interns-2017 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Platforms 2017-07-10 |
| Participants: |
| Description |
|
The following error: "No primary detected for set Cluster0-shard-0 2017-06-14T00:00:00.000-0800 I NETWORK [ReplicaSetMonitor-TaskExecutor-0] 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] |
| Comments |
| Comment by Githook User [ 20/Jun/17 ] |
|
Author: {u'username': u'tkaye407', u'name': u'Tyler Kaye', u'email': u'tyler.kaye@mongodb.com'}Message: |
| Comment by Tyler Kaye [ 19/Jun/17 ] |
|
This is the new error message: [js_test:add_invalid_shard] 2017-06-19T14:17:02.162-0400 c20011| 2017-06-19T14:17:02.161-0400 W NETWORK [conn18] Unable to reach primary for set prefix_add_invalid_shard |
| Comment by Osmar Olivo [ 16/Jun/17 ] |
|
I propose the below for wording: "Unable to reach primary for set Cluster0-shard-0 2017-06-14T00:00:00.000-0800 I NETWORK [ReplicaSetMonitor-TaskExecutor-0] |