[SERVER-26172] Better logging in MetadataManager::refreshActiveMetadata Created: 19/Sep/16  Updated: 06/Dec/22  Resolved: 19/Sep/16

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 3.3.12
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Randolph Tan Assignee: [DO NOT USE] Backlog - Sharding Team
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-26107 refreshMetadata should not be called ... Closed
Assigned Teams:
Sharding
Participants:

 Description   

The log entry here:

log() << "Marking collection as not sharded.";

and here:

log() << "Marking collection as sharded with " << remoteMetadata->toStringBasic();

doesn't contain the name of the collection, which makes diagnosis a little bit difficult



 Comments   
Comment by Kaloian Manassiev [ 19/Sep/16 ]

The symptoms in this ticket duplicate the work done for SERVER-26107 already.

Generated at Thu Feb 08 04:11:20 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.