[SERVER-36227] Improve logging when awaitReplication hangs Created: 20/Jul/18  Updated: 29/Oct/23  Resolved: 20/Aug/18

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

Type: Improvement Priority: Major - P3
Reporter: Samyukta Lanka Assignee: Samyukta Lanka
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Backwards Compatibility: Fully Compatible
Sprint: Repl 2018-08-13, Repl 2018-08-27
Participants:
Linked BF Score: 15

 Description   

1. Add recovery component logging to more test suites so that we can see updates to the stable timestamp
2. Add information about all the opTimes that we keep track of to replicationProgress to display more information in the case of a timeout in awaitReplication
3. Add a timeout in waitForLinearizableReadConcern when we're testing so that we can make sure that replicationProgress is printed out to help in debugging.



 Comments   
Comment by Githook User [ 20/Aug/18 ]

Author:

{'name': 'Judah Schvimer', 'email': 'judah@mongodb.com', 'username': 'judahschvimer'}

Message: SERVER-36227 always log replication progress on write concern failure
Branch: master
https://github.com/mongodb/mongo/commit/eb4df9f2f06a0c5dc6c07231f3de7d2cbb674ee9

Comment by Judah Schvimer [ 17/Aug/18 ]

One thought we'd talked about that is not reflected here is that any time that _awaitReplication_inlock fails (either through returning a bad status or by throwing) we should log the "Replication for failed WC" message, not just when it times out.

Another thing that would be helpful is to log the earliest drop pending optime since we also wait on that to commit before returning from SERVER-34372.

Comment by Githook User [ 10/Aug/18 ]

Author:

{'name': 'Samy Lanka', 'email': 'samy.lanka@gmail.com', 'username': 'lankas'}

Message: SERVER-36227 Add informatin about additional optimes that we keep track of to replicationProgress
Branch: master
https://github.com/mongodb/mongo/commit/ea11d6e7f8b6cc62e937094521f25faada5f109f

Comment by Githook User [ 30/Jul/18 ]

Author:

{'name': 'Samy Lanka', 'email': 'samy.lanka@gmail.com', 'username': 'lankas'}

Message: Revert "SERVER-36227 Add recovery component logging to concurrency suites that use replication"

This reverts commit 018905518ca552775255f36a52e9fd187f9d61f8.
Branch: master
https://github.com/mongodb/mongo/commit/7110f484d4f6fa7c0fd348c5ced9c31c16b3c060

Comment by Githook User [ 30/Jul/18 ]

Author:

{'name': 'Samy Lanka', 'email': 'samy.lanka@gmail.com', 'username': 'lankas'}

Message: SERVER-36227 Add recovery to default log component verbosity setting for evergreen
Branch: master
https://github.com/mongodb/mongo/commit/43bde3838e8b29476c40c0a2894873f41feca0d5

Comment by Githook User [ 27/Jul/18 ]

Author:

{'username': 'lankas', 'name': 'Samy Lanka', 'email': 'samy.lanka@gmail.com'}

Message: SERVER-36227 Add recovery component logging to concurrency suites that use replication
Branch: master
https://github.com/mongodb/mongo/commit/018905518ca552775255f36a52e9fd187f9d61f8

Comment by Tess Avitabile (Inactive) [ 26/Jul/18 ]

Please work on this on Fridays (this means you might do less BF diagnosis, which is fine).

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