[DOCS-11870] Clarify that the balancer no longer takes the balancer lock Created: 12/Jul/18  Updated: 30/Oct/23  Resolved: 06/Nov/18

Status: Closed
Project: Documentation
Component/s: manual
Affects Version/s: 3.6 Core Server, 4.0 Core Server
Fix Version/s: Server_Docs_20231030

Type: Improvement Priority: Major - P3
Reporter: Linda Qin Assignee: Kay Kim (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:
Days since reply: 5 years, 14 weeks, 1 day ago
Epic Link: DOCSP-1769
Story Points: 0.25

 Description   

----------------------------

Original Description

This is for the document Cluster Balancer.

Per SERVER-27550, since MongoDB 3.6, the balancer no longer takes the balancer lock. It would be nice to add this change in the document for MongoDB 3.6 and above. e.g.

Changed in version 3.6: The balancer no longer takes the balancer lock.

----------------------------

Description

Scope of changes (files that need work and how much)

Impact to other docs outside of this product

MVP (work and date?)

Resources (e.g. Scope Docs, Invision)



 Comments   
Comment by Githook User [ 06/Nov/18 ]

Author:

{'name': 'kay', 'email': 'kay.kim@10gen.com', 'username': 'kay-kim'}

Message: DOCS-11870: 3.6 no more balancer locks
Branch: v3.6
https://github.com/mongodb/docs/commit/deb2caa696761e46db0e8cc31bbc5ce80544883c

Comment by Githook User [ 06/Nov/18 ]

Author:

{'name': 'kay', 'email': 'kay.kim@10gen.com', 'username': 'kay-kim'}

Message: DOCS-11870: 3.6 no more balancer locks
Branch: v4.0
https://github.com/mongodb/docs/commit/c12b6e92cc7517feae7c1c54f0e7fc8e694bcab0

Comment by Githook User [ 06/Nov/18 ]

Author:

{'name': 'kay', 'email': 'kay.kim@10gen.com', 'username': 'kay-kim'}

Message: DOCS-11870: 3.6 no more balancer locks
Branch: master
https://github.com/mongodb/docs/commit/a9a31a1ff28ba561dcbb35bb05d31fa4a028fd13

Comment by 章 黒鉄 [ 12/Jul/18 ]

I like to suggest that if the {{{_id: "balancer", ... }}} document is present in config.locks collection after upgrading from 3.4, it is just an artifact and it can be safely deleted.

Cheers,

Akira

Generated at Thu Feb 08 08:03:50 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.