[SERVER-4171] WritebackListener should force detection of newly sharded collection Created: 28/Oct/11  Updated: 11/Jul/16  Resolved: 09/Nov/11

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 2.0.1
Fix Version/s: 1.8.5, 2.0.2, 2.1.0

Type: Bug Priority: Major - P3
Reporter: Greg Studer Assignee: Greg Studer
Resolution: Done Votes: 0
Labels: rn
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File writeback_shard_version.js    
Issue Links:
Depends
is depended on by SERVER-4167 Sharding info not communicated to all... Closed
Related
Backwards Compatibility: Fully Compatible
Operating System: ALL
Participants:

 Description   

... in the case where it does not appear sharded initially from other operations, throws assertion 10181

Probably the fix is to explicitly check the results of getChunkManagerIfExists() before checking, though a cleaner fix is probably also worth doing.



 Comments   
Comment by auto [ 08/Dec/11 ]

Author:

{u'login': u'gregstuder', u'name': u'Greg Studer', u'email': u'greg@10gen.com'}

Message: SERVER-4171 test for new wbl behavior in 1.8.5
Branch: v1.8
https://github.com/mongodb/mongo/commit/57fa5f296e00af8833bf19c31e3209e8c65bb47b

Comment by auto [ 08/Dec/11 ]

Author:

{u'login': u'gregstuder', u'name': u'Greg Studer', u'email': u'greg@10gen.com'}

Message: SERVER-4171 check in wbl for newly sharded state, reload
Branch: v1.8
https://github.com/mongodb/mongo/commit/a8deef409a7319faafa4d746881bcaac31ee061c

Comment by Greg Studer [ 07/Nov/11 ]

1.8 backport will be messier - waiting on discussion of other backports there.

Comment by auto [ 07/Nov/11 ]

Author:

{u'login': u'gregstuder', u'name': u'gregs', u'email': u'greg@10gen.com'}

Message: SERVER-4171 modified test for wbl and new sharding, avoids S*RVER-4222
Branch: v2.0
https://github.com/mongodb/mongo/commit/e76f5276870cf3d9be5cbfc8aeb55d2c209d9ae1

Comment by auto [ 07/Nov/11 ]

Author:

{u'login': u'gregstuder', u'name': u'gregs', u'email': u'greg@10gen.com'}

Message: reload shard version if needed for new collections in wbl SERVER-4171
Branch: v2.0
https://github.com/mongodb/mongo/commit/04ba3d198ab5eed8cd604d6fe18b753ae050108a

Comment by Greg Studer [ 07/Nov/11 ]

Fixes the issue, but the error is still very ugly. In general, need to refactor chunk manager code to eliminate the masserts and stack traces when not necessary.

Comment by auto [ 07/Nov/11 ]

Author:

{u'login': u'gregstuder', u'name': u'gregs', u'email': u'greg@10gen.com'}

Message: SERVER-4171 test for wbl and new sharding
Branch: master
https://github.com/mongodb/mongo/commit/2c91cca517f9ffad4753d2e4b6eb863b035f9058

Comment by auto [ 02/Nov/11 ]

Author:

{u'login': u'gregstuder', u'name': u'gregs', u'email': u'greg@10gen.com'}

Message: reload shard version if needed for new collections in wbl SERVER-4171
Branch: master
https://github.com/mongodb/mongo/commit/d121b7ba4e40ff6b8aee657ed36094f1a9eb3dce

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