[SERVER-19319] CatalogManagerReplicaSet needs to send setShardVersion to primary shard after sharding a collection Created: 07/Jul/15  Updated: 19/Sep/15  Resolved: 29/Jul/15

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

Type: Bug Priority: Major - P3
Reporter: Spencer Brody (Inactive) Assignee: Kaloian Manassiev
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-18594 RS Catalog Manager implementation of ... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding 6 07/17/15, Sharding 7 08/10/15
Participants:

 Comments   
Comment by Githook User [ 31/Jul/15 ]

Author:

{u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}

Message: SERVER-19319 Send setShardVersion command after sharding a collection

The shard collection operation needs to inform the former primary shard
for the database containing this collection that the collection is being
sharded. That way, unsharded operations will be rejected when they come
from mongos instances, which are not yet aware the collection became
sharded.

Also reverts commit 280b8e6c835bab826899a7696a1f5852e1221d53
("SERVER-19319 Temporarily update some tests to run a query after sharding
a collection to force the version to be set")
Branch: master
https://github.com/mongodb/mongo/commit/9ca37ee188c73256610b105b1b5097a605e54697

Comment by Githook User [ 31/Jul/15 ]

Author:

{u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}

Message: SERVER-19319 Send setShardVersion command after sharding a collection

The shard collection operation needs to inform the former primary shard
for the database containing this collection that the collection is being
sharded. That way, unsharded operations will be rejected when they come
from mongos instances, which are not yet aware the collection became
sharded.

Also reverts commit 280b8e6c835bab826899a7696a1f5852e1221d53
("SERVER-19319 Temporarily update some tests to run a query after sharding
a collection to force the version to be set")
Branch: master
https://github.com/mongodb/mongo/commit/9ca37ee188c73256610b105b1b5097a605e54697

Comment by Githook User [ 31/Jul/15 ]

Author:

{u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}

Message: SERVER-19319 SetShardVersionRequest

This change introduces a SetShardVersionRequest class, which will be used
to parse and construct the BSON for setShardVersion commands.
Branch: master
https://github.com/mongodb/mongo/commit/d5a9eea40f6c25167c5ec33c2dc3dadde5862aff

Comment by Githook User [ 29/Jul/15 ]

Author:

{u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}

Message: SERVER-19319 Fix a lint breakage
Branch: master
https://github.com/mongodb/mongo/commit/54287f9a7a35e335b91689f5f5e7d5efcdb7dd15

Comment by Githook User [ 29/Jul/15 ]

Author:

{u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}

Message: Revert "SERVER-19319 Send setShardVersion command after sharding a collection"

This reverts commit b0067ef44c6461beed332c8bbfc40ceb55d05d40.
Branch: master
https://github.com/mongodb/mongo/commit/a06c27a9887c9dd8fc43d9e7d8727a1840292911

Comment by Githook User [ 29/Jul/15 ]

Author:

{u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}

Message: SERVER-19319 Send setShardVersion command after sharding a collection

The shard collection operation needs to inform the former primary shard
for the database containing this collection that the collection is being
sharded. That way, unsharded operations will be rejected when they come
from mongos instances, which are not yet aware the collection became
sharded.

Also reverts commit 280b8e6c835bab826899a7696a1f5852e1221d53
("SERVER-19319 Temporarily update some tests to run a query after sharding
a collection to force the version to be set")
Branch: master
https://github.com/mongodb/mongo/commit/b0067ef44c6461beed332c8bbfc40ceb55d05d40

Comment by Githook User [ 29/Jul/15 ]

Author:

{u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}

Message: SERVER-19319 Send setShardVersion command after sharding a collection

The shard collection operation needs to inform the former primary shard
for the database containing this collection that the collection is being
sharded. That way, unsharded operations will be rejected when they come
from mongos instances, which are not yet aware the collection became
sharded.

Also reverts commit 280b8e6c835bab826899a7696a1f5852e1221d53
("SERVER-19319 Temporarily update some tests to run a query after sharding
a collection to force the version to be set")
Branch: master
https://github.com/mongodb/mongo/commit/b0067ef44c6461beed332c8bbfc40ceb55d05d40

Comment by Githook User [ 28/Jul/15 ]

Author:

{u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@mongodb.com'}

Message: SERVER-19319 Temporarily update some tests to run a query after sharding a collection to force the version to be set
Branch: master
https://github.com/mongodb/mongo/commit/280b8e6c835bab826899a7696a1f5852e1221d53

Comment by Spencer Brody (Inactive) [ 22/Jul/15 ]

Note: When resolving this make sure to undo the test changes added in https://github.com/mongodb/mongo/commit/280b8e6c835bab826899a7696a1f5852e1221d53

Comment by Githook User [ 22/Jul/15 ]

Author:

{u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@mongodb.com'}

Message: SERVER-19319 Temporarily update some tests to run a query after sharding a collection to force the version to be set
Branch: master
https://github.com/mongodb/mongo/commit/280b8e6c835bab826899a7696a1f5852e1221d53

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