[SERVER-26777] Improve logging around chunk metadata refresh Created: 25/Oct/16 Updated: 07/Dec/16 Resolved: 27/Oct/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 3.2.10, 3.4.0-rc1 |
| Fix Version/s: | 3.4.0-rc2 |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Kaloian Manassiev | Assignee: | Kaloian Manassiev |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Backport Completed: | |||||||||
| Sprint: | Sharding 2016-10-31 | ||||||||
| Participants: | |||||||||
| Case: | (copied to CRM) | ||||||||
| Description |
|
The logging around chunk metadata refresh is confusing and is only done after the load has completed. This means that long refresh operations (which happen under a mutex) will block other calls, but will not output anything until the call completes. In addition they are inconsistent between mongos and the shards. |
| Comments |
| Comment by Githook User [ 31/Oct/16 ] |
|
Author: {u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}Message: (backport of commit e8cbb32624663fdf59f6df752594e5295c55247c) |
| Comment by Githook User [ 27/Oct/16 ] |
|
Author: {u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}Message: Unifies the logging messages between mongos and mongod and adds timing |
| Comment by Kaloian Manassiev [ 27/Oct/16 ] |
|
Author: {u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}Message: |