[SERVER-17468] actionlog should not log every single balancer round Created: 04/Mar/15 Updated: 05/Mar/18 Resolved: 29/Feb/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 3.0.0 |
| Fix Version/s: | 3.2.5, 3.3.3 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Asya Kamsky | Assignee: | Dianna Hohensee (Inactive) |
| Resolution: | Done | Votes: | 1 |
| Labels: | bkp, code-and-test | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Backport Completed: | |||||||||
| Backport Requested: |
v3.0
|
||||||||
| Sprint: | Sharding 10 (02/19/16), Sharding 11 (03/11/16) | ||||||||
| Participants: | |||||||||
| Description |
|
The sharding config collection actionlog added for If you have several dozen mongos processes, it's conceivable that each of these balancing rounds will be happening every second or two and since actionlog is 2MB capped collection, after about 3-4 hours we will have overwritten all previous actions. Is there value of recording "balancer thread woke up, got the lock, found nothing to do and did nothing"? If there was nothing to do during balancing round, did it really happen? Even if it did, is there any value to recording that over and over again? |
| Comments |
| Comment by Githook User [ 30/Mar/16 ] |
|
Author: {u'username': u'DiannaHohensee', u'name': u'Dianna Hohensee', u'email': u'dianna.hohensee@10gen.com'}Message: (cherry picked from commit b2338b956c6808efc633428116e8534e495ee12c) Conflicts: |
| Comment by Githook User [ 29/Feb/16 ] |
|
Author: {u'username': u'DiannaHohensee', u'name': u'Dianna Hohensee', u'email': u'dianna.hohensee@10gen.com'}Message: |
| Comment by Hoyt Ren [ 06/Jan/16 ] |
|
I feel need this feature too, other logs don't see problems, but mongos. I feel here should be a config option like "systemLog.component.banlancer.verbosity". |