[SERVER-2024] Update in configDB for a chunk's migration may suffer if connection is lost Created: 28/Oct/10  Updated: 12/Jul/16  Resolved: 19/Dec/10

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

Type: Bug Priority: Major - P3
Reporter: Alberto Lerner Assignee: Alberto Lerner
Resolution: Done Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: ALL
Participants:

 Description   

The chunk migration commit is done at s/d_migrate.cpp in several steps (5.x). In 5.c, we connect to the config DB and update version and location of a chunk. If that connection fails, we should unwind state accordingly.



 Comments   
Comment by auto [ 19/Dec/10 ]

Author:

{u'login': u'alerner', u'name': u'Alberto Lerner', u'email': u'alerner@10gen.com'}

Message: SERVER-2024 if a network error is raised during migrate commit, pause, and recheck
https://github.com/mongodb/mongo/commit/63c23a23597031d248389ca229f8d75ad62c4ef9

Comment by auto [ 11/Dec/10 ]

Author:

{u'login': u'alerner', u'name': u'Alberto Lerner', u'email': u'alerner@10gen.com'}

Message: SERVER-2024 disambiguate
https://github.com/mongodb/mongo/commit/4597deb9d436d31892633b1a3391bb41c3b5b675

Comment by auto [ 11/Dec/10 ]

Author:

{u'login': u'alerner', u'name': u'Alberto Lerner', u'email': u'alerner@10gen.com'}

Message: SERVER-2024 on migrate commit, either update both TO/FROM shards or none
https://github.com/mongodb/mongo/commit/d2e9c8586994fb33c07324177914b943e0d52d84

Comment by auto [ 13/Nov/10 ]

Author:

{'login': 'alerner', 'name': 'Alberto Lerner', 'email': 'alerner@10gen.com'}

Message: SERVER-2024 reminder comment; implementation depends on new state on ChunkMater that's coming up
/mongodb/mongo/commit/e58d6da4041c6950edf2fc63920b6877069578c2

Generated at Thu Feb 08 02:58:44 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.