[SERVER-46402] Better logging for movePrimary/moveChunk when error occurs Created: 25/Feb/20  Updated: 29/Oct/23  Resolved: 24/Apr/20

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

Type: Improvement Priority: Major - P3
Reporter: Randolph Tan Assignee: Pierlauro Sciarelli
Resolution: Fixed Votes: 0
Labels: neweng, sharding-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2020-05-04
Participants:

 Description   

We currently use the uassertStatusOKWithWarning to log errors that occurred when running moveChunk/movePrimary:

https://github.com/mongodb/mongo/blob/r4.3.2/src/mongo/db/s/move_chunk_command.cpp#L229
https://github.com/mongodb/mongo/blob/r4.3.2/src/mongo/db/s/move_primary_command.cpp#L162

However, these only catches cases when the error is propagated via a returned status. There are a few cases where we use uasserts inside these calls and they won't show up in the log default setting unless it is verbose enough to show assertion messages.



 Comments   
Comment by Githook User [ 24/Apr/20 ]

Author:

{'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}

Message: SERVER-46402 Better logging for movePrimary/moveChunk when error occurs
Branch: master
https://github.com/mongodb/mongo/commit/381dbd91f3c5c0e7b23513c6b93fc4842ad96b26

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