annot dial mongo to initiate replicaset: no reachable servers
Bug #1605776 reported by
Curtis Hovey
This bug report is a duplicate of:
Bug #1605767: Mongo: SetUpTest/TearDownTest no reachable servers.
Edit
Remove
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Triaged
|
Medium
|
Unassigned | ||
| juju-core |
Won't Fix
|
Undecided
|
Unassigned | ||
| 1.25 |
Won't Fix
|
Undecided
|
Unassigned | ||
Bug Description
As seen in
http://
An intermittent issue, Cannot dial mongo to initiate replicaset: no reachable servers
The recent occurrences are definitely related to a host under stress. Several fixes have been made over time to Juju 1.x for mongo 2.4. We can see from recent tests that is can happen to juju2 with mongo 3.2.
As stress appears to be a factor, maybe Juju could explain the situation and suggest a solution instead of showing the user an errors and taking the blame for the failure. Maybe juju is at fault because it didn't recognise the host was under stress and needed to retry. This is happening more frequently over the last few months of testing
| affects: | juju-core → juju |
| Changed in juju-core: | |
| status: | New → Won't Fix |
Revision history for this message
| Anastasia (anastasia-macmood) wrote | #1 |
To post a comment you must log in.
I am pretty sure that it is another case of bug # 1605767. Marking this report as duplicate.