[SERVER-21174] applyChunkOpsDeprecated should retry on notMaster or network errors Created: 27/Oct/15  Updated: 17/Nov/15  Resolved: 12/Nov/15

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 3.2.0-rc3

Type: Bug Priority: Major - P3
Reporter: Kaloian Manassiev Assignee: Misha Tyulenev
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding B (10/30/15), Sharding C (11/20/15)
Participants:

 Description   

This was found through code inspection. The moveChunk command under CSRS will terminate the donor shard instance if the applyOps command returns a notMaster status. In particular, this line and the handling here.

While we are at it, we should also get rid of the try/catch block around applyChunkOpsDeprecated because this method should never throw in 3.2.

The splitChunk command will also benefit from the same retry logic.



 Comments   
Comment by Githook User [ 12/Nov/15 ]

Author:

{u'username': u'mikety', u'name': u'Misha Tyulenev', u'email': u'misha@mongodb.com'}

Message: SERVER-21174 applyChunkOpsDeprecated should retry on notMaster or network errors
Branch: master
https://github.com/mongodb/mongo/commit/4bc9ddd700aafd4306de0479ffccf4dac3d08266

Generated at Thu Feb 08 03:56:32 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.