[SERVER-26144] Add additional logging around balancer operations Created: 16/Sep/16  Updated: 19/Nov/16  Resolved: 20/Sep/16

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

Type: Bug Priority: Major - P3
Reporter: Dianna Hohensee (Inactive) Assignee: Dianna Hohensee (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-26177 DuplicateKey Error in Balancer during... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2016-10-10
Participants:

 Description   

Log when the state changes to kStopping, i.e. when the migration manager is interrupted.

ScopedMigrationRequest::writeMigration should find the matching migration document so we can log the differences on DuplicateKey errors.



 Comments   
Comment by Githook User [ 20/Sep/16 ]

Author:

{u'username': u'DiannaHohensee', u'name': u'Dianna Hohensee', u'email': u'dianna.hohensee@10gen.com'}

Message: SERVER-26144 add additional logging to ScopedMigrationRequest to aid debugging the balancer
Branch: master
https://github.com/mongodb/mongo/commit/493aede8171057c8a0d14d567fae6236c1a0b995

Comment by Dianna Hohensee (Inactive) [ 20/Sep/16 ]

This has turned into a bug fix, because getting better logging fixes a race in ScopedMigrationRequest::writeMigration wherein it can fail when it hits a DuplicateKey error, but then fails to verify it's the same migration because the find query fails because the document was removed since the DuplicateKey error.

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