[SERVER-47791] Additional logging for failed collection clone during resync. Created: 27/Apr/20  Updated: 27/Oct/23  Resolved: 05/May/20

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: 4.0.14
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: James Phelan (Inactive) Assignee: Judah Schvimer
Resolution: Works as Designed Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Participants:
Case:

 Description   

During an initial sync we can fail to clone a collection from the sync source. The messages logged are as follows.

YYYY-MM-DDTHH:MM:SSZ I REPL [repl writer worker 1] Finished cloning data: InitialSyncFailure: Failed to clone 1 collection(s) in 'DBNAME' from HOST:PORT. Beginning oplog replay.

To improve diagnostics it would be a good idea to log the collection name that failed.



 Comments   
Comment by James Phelan (Inactive) [ 05/May/20 ]

Hi judah.schvimer,

Thank you for getting back. You are correct, information on the failed collection is recorded in previous log messages. Redacted version below.

Closing this ticket as "Works as designed" because the requested information is already logged.

YYYY-MM-DDTHH:MM:SS.000Z W REPL     [replication-49] collection clone for 'DB.COLLECTION' failed due to InvalidBSON: Error cloning collection 'DB.COLLECTION' :: caused by :: not null terminated string in element with field name 'FIELD' in object with unknown _id
...
...
YYYY-MM-DDTHH:MM:SS.000Z W REPL     [repl writer worker 2] database 'DB' (4 of 4) clone failed due to InitialSyncFailure: Failed to clone 1 collection(s) in 'DB' from HOST:PORT

Comment by Judah Schvimer [ 04/May/20 ]

Hi james.phelan,

Thank you for the report. My understanding is that in the above example, the name of the failed collection would be in a log message shortly before the one referenced here. Is that not the case, or is that not sufficient?

Thank you,
Judah

Generated at Thu Feb 08 05:15:14 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.