[SERVER-27923] Balancer get stuck for unresponsive server Created: 06/Feb/17 Updated: 27/Oct/23 Resolved: 07/Feb/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 3.0.14, 3.2.12 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Gilad W | Assignee: | Kelsey Schubert |
| Resolution: | Gone away | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Steps To Reproduce: | Created 2 mongos on different servers on a sharding cluster. |
| Participants: |
| Description |
|
I have application mongos on many servers. when the server of balancer gets shut down, the whole process gets stopped and no new balancer is getting selected. This problem can be solve by also allowing to choose the specific possible balancers hosts it would solve the problem. From today: |
| Comments |
| Comment by Kelsey Schubert [ 07/Feb/17 ] |
|
Thanks for the report. This issue has been resolved in MongoDB 3.4 as the balancer only runs on the primary config server. If this is an issue for you, I would recommend upgrading to MongoDB 3.4.2. Kind regards, |