[SERVER-11688] Improve diagnostic messages for metadata reloading in shards Created: 13/Nov/13  Updated: 11/Jul/16  Resolved: 03/Mar/14

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 2.5.3
Fix Version/s: 2.6.0-rc1

Type: Task Priority: Major - P3
Reporter: Randolph Tan Assignee: Siyuan Zhou
Resolution: Done Votes: 0
Labels: pull-request
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-11124 mongos setShardVersion failed message... Closed
Participants:

 Description   

Idea is that on (mongod) config metadata reload, there is a lot of information presented to the user - the previous version/epoch, the loaded version/epoch, the version that may have changed while we load. There's also collection vs. shard version to report.

We currently dump much of this info to the logs, but in common cases, we could simplify. For example:

"collection was previously unsharded, new metadata loaded with shard version XXX|YYY (collection version XXX|YYY|epoch)"
"collection was previously at shard version XXX|YYY, now at shard version WWW|QQQ (new collection version RRR|SSS|epoch)"

Or maybe two messages - one for shard version, one saying "collection version was loaded at version XXX|YYY|epoch".



 Comments   
Comment by Githook User [ 28/Feb/14 ]

Author:

{u'username': u'visualzhou', u'name': u'Siyuan Zhou', u'email': u'siyuan.zhou@mongodb.com'}

Message: SERVER-11688 Improve diagnostic messages for metadata reloading in shards

Signed-off-by: Matt Kangas <matt.kangas@mongodb.com>
Branch: master
https://github.com/mongodb/mongo/commit/d43eb9202ff065364e0eac9a6b601186afd37fa5

Comment by Daniel Pasette (Inactive) [ 17/Dec/13 ]

can you provide a better description here?

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