[SERVER-15591] enforce secondaryThrottle during moveChunk commit Created: 09/Oct/14  Updated: 27/Oct/15  Resolved: 15/Oct/14

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

Type: Bug Priority: Major - P3
Reporter: Greg Studer Assignee: Randolph Tan
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-16548 Allow enforcement of additional custo... Closed
is related to DOCS-4318 Document secondaryThrottle improvements Closed
is related to SERVER-14041 enhance secondaryThrottle parameter Closed
is related to SERVER-16357 Chunk migration pre-commit write conc... Closed
Tested
Operating System: ALL
Participants:

 Description   

The secondaryThrottle parameter is used during the bulk insert/remove operations of migrations, but is not used during commit - this is somewhat inconsistent if the secondaryThrottle write concern is stronger than the (necessary) majority-of-nodes-caught-up write concern used by the migration commit.

By enforcing both majority-of-nodes and the specified secondaryThrottle, we should be as safe as before but also allow users to provide stronger migration commit guarantees.



 Comments   
Comment by Githook User [ 15/Oct/14 ]

Author:

{u'username': u'renctan', u'name': u'Randolph Tan', u'email': u'randolph@10gen.com'}

Message: SERVER-15591 enforce secondaryThrottle during moveChunk commit
Branch: master
https://github.com/mongodb/mongo/commit/658f0bce4379fc0334a53c4381d57b8b7c7d53b7

Comment by Randolph Tan [ 15/Oct/14 ]

To docs team:

This is addendum to SERVER-14041 - on the commit phase of the destination shard, the server will now enforce both the "majority" and user specified write concern.

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