[SERVER-6167] very verbose messaging with large numbers of collections Created: 21/Jun/12 Updated: 11/Jul/16 Resolved: 27/Nov/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Logging, Sharding |
| Affects Version/s: | 2.0.6, 2.2.0-rc0 |
| Fix Version/s: | 2.0.7, 2.2.3, 2.3.2 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Greg Studer | Assignee: | Greg Studer |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||
| Issue Links: |
|
||||
| Operating System: | ALL | ||||
| Participants: | |||||
| Description |
|
When there are many sharded collections, the standard logging can be extremely verbose in the balancer, wbl, and sharded write logic. We should make sure we aren't reporting unimportant information on individual collections at the default logLevel. |
| Comments |
| Comment by auto [ 08/Jan/13 ] |
|
Author: {u'date': u'2013-01-08T06:45:29Z', u'name': u'Dan Pasette', u'email': u'dan@10gen.com'}Message: |
| Comment by auto [ 08/Jan/13 ] |
|
Author: {u'date': u'2012-11-26T22:51:06Z', u'name': u'Greg Studer', u'email': u'greg@10gen.com'}Message: Conflicts: src/mongo/client/distlock.cpp |
| Comment by auto [ 26/Nov/12 ] |
|
Author: {u'date': u'2012-11-26T22:51:06Z', u'email': u'greg@10gen.com', u'name': u'Greg Studer'}Message: |
| Comment by Ian Whalen (Inactive) [ 31/Jul/12 ] |
|
David this did make it into the 2.0.7-rc0 release, so you should see a change using that or rc1. It's still marked as open because we've only made the change on the 2.0 branch and not master yet. |
| Comment by David Mytton [ 30/Jul/12 ] |
|
Was this in the 2.0.7.rc1 release? It's still shown as unresolved. |
| Comment by auto [ 02/Jul/12 ] |
|
Author: {u'date': u'2012-07-02T11:51:30-07:00', u'name': u'Greg Studer', u'email': u'greg@10gen.com'}Message: |