delta/mongo.git/src/mongo/s, branch r4.0.17 github.com: mongodb/mongo.git SERVER-44598 Shards do not treat the IGNORED version as "intended sharded" 2020-03-02T11:10:34+00:00 Kaloian Manassiev kaloian.manassiev@mongodb.com 2020-03-02T10:29:15+00:00 60b4902efe05c84d938f6ac600f406d53de0eb6f (cherry picked from commit 7604dad6da718751ad1f04bae1c839e87a1f8651) (cherry picked from commit 5868a00ce71d85b6063489909b5ae79bc7369338) 
(cherry picked from commit 7604dad6da718751ad1f04bae1c839e87a1f8651)
(cherry picked from commit 5868a00ce71d85b6063489909b5ae79bc7369338)
SERVER-45599 Backport of SERVER-39495: Move ShardingState::needCollectionMetadata under OperationShardingState 2020-02-26T19:46:00+00:00 Kaloian Manassiev kaloian.manassiev@mongodb.com 2020-02-26T17:31:41+00:00 fcd2dd41189fffc6e67a8645b99974178f87ca04 ShardingState logically contains answers to questions about whether the current instance is node in a sharded cluster, whereas OperationShardingState is responsible for the 'shardedness' of the commands. This is a partial cherry-pick from b049257fbd1d215388cffaf7544f6741dbce5b45, adapted for the 4.0 branch. Also backports the addition of more testing for multi:true/justOne:false updates and ChangeStreams, which was taken from commit 50f6bd4d6a9428a6f1df22db792d7b55d773762c. 
ShardingState logically contains answers to questions about whether the
current instance is node in a sharded cluster, whereas
OperationShardingState is responsible for the 'shardedness' of the
commands.

This is a partial cherry-pick from b049257fbd1d215388cffaf7544f6741dbce5b45, adapted for the 4.0 branch.

Also backports the addition of more testing for multi:true/justOne:false updates and ChangeStreams, which was taken from commit 50f6bd4d6a9428a6f1df22db792d7b55d773762c.
SERVER-45599 Backport of SERVER-32198: Split CollectionShardingState::getMetadata into three methods 2020-02-26T12:15:07+00:00 Kaloian Manassiev kaloian.manassiev@mongodb.com 2020-02-26T10:20:35+00:00 b41cd4b2c416e965fc3541c97cd0b51563d90c40 o getCurrentMetadataIfKnown - which returns the current filtering metadata if any is available o getMetadataForOperation - which returns the metadata which is required by the current opertion, based on the OperationShardingState o getCurrentMetadata - which returns the currently available filtering metadata (or UNSHARDED if not known) This is in preparation for making getMetadataForOperation/getCurrentMetadata throw StaleShardVersion exception if the metadata has not been loaded yet. This is a partial cherry-pick from dcf7e0dd89d34f58b592f1adb3d41e5edd6e2012, adapted for the 4.0 branch. 
o getCurrentMetadataIfKnown - which returns the current filtering metadata if any is available
o getMetadataForOperation - which returns the metadata which is required by the current opertion, based on the OperationShardingState
o getCurrentMetadata - which returns the currently available filtering metadata (or UNSHARDED if not known)

This is in preparation for making getMetadataForOperation/getCurrentMetadata throw StaleShardVersion exception if the metadata has not been loaded yet.

This is a partial cherry-pick from dcf7e0dd89d34f58b592f1adb3d41e5edd6e2012, adapted for the 4.0 branch.
SERVER-45599 Backport of SERVER-32198: Make MetadataManager support an 'UNKNOWN' filtering metadata state 2020-02-26T08:00:01+00:00 Kaloian Manassiev kaloian.manassiev@mongodb.com 2020-02-25T21:04:41+00:00 96ced970aef7c5dbf81b660009bb80f33d8026e8 This is partial cherry-pick of the changes done under 20117b8ee9678794be675eb4d728bfcc8f9d75f4 to make the 4.0 logic match that of 4.2. 
This is partial cherry-pick of the changes done under 20117b8ee9678794be675eb4d728bfcc8f9d75f4 to make the 4.0 logic match that of 4.2.
Revert "SERVER-45599 Backport of SERVER-32198: Make MetadataManager support an 'UNKNOWN' filtering metadata state" 2020-01-29T16:37:03+00:00 Kaloian Manassiev kaloian.manassiev@mongodb.com 2020-01-29T15:47:18+00:00 132aa852b1ae87f48165dbdf50943f32d2376c73 This reverts commit e4e052a10484cf2cc44c62c377db4ece8162820a. 
This reverts commit e4e052a10484cf2cc44c62c377db4ece8162820a.
Revert "SERVER-45599 Backport of SERVER-32198: Split CollectionShardingState::getMetadata into three methods" 2020-01-29T16:37:03+00:00 Kaloian Manassiev kaloian.manassiev@mongodb.com 2020-01-29T15:47:13+00:00 c25809db3532d2af31321648790e775bd420e600 This reverts commit a414e4ceafb45dc6ebf4daeb9198f0a7f3fb189c. 
This reverts commit a414e4ceafb45dc6ebf4daeb9198f0a7f3fb189c.
Revert "SERVER-45599 Backport of SERVER-39495: Move ShardingState::needCollectionMetadata under OperationShardingState" 2020-01-29T16:37:03+00:00 Kaloian Manassiev kaloian.manassiev@mongodb.com 2020-01-29T15:47:02+00:00 385511e9d05b254beb6767ed92a3cd95e83ea166 This reverts commit 1a01c53df8f7c1e016c0ccbc38b77f6b3508bf65. 
This reverts commit 1a01c53df8f7c1e016c0ccbc38b77f6b3508bf65.
Revert "SERVER-44598 Shards do not treat the IGNORED version as "intended sharded"" 2020-01-29T16:37:02+00:00 Kaloian Manassiev kaloian.manassiev@mongodb.com 2020-01-29T15:45:58+00:00 329618bf849fb8fdeca96703ca691874f8817947 This reverts commit f2eee7f4879a0dda72b281c8d1d25f2afc4c5eb7. 
This reverts commit f2eee7f4879a0dda72b281c8d1d25f2afc4c5eb7.
SERVER-44598 Shards do not treat the IGNORED version as "intended sharded" 2020-01-27T13:08:44+00:00 Marcos José Grillo Ramírez marcos.grillo@10gen.com 2020-01-27T13:08:44+00:00 f2eee7f4879a0dda72b281c8d1d25f2afc4c5eb7 (cherry picked from commit 7604dad6da718751ad1f04bae1c839e87a1f8651) (cherry picked from commit 5868a00ce71d85b6063489909b5ae79bc7369338) 
(cherry picked from commit 7604dad6da718751ad1f04bae1c839e87a1f8651)
(cherry picked from commit 5868a00ce71d85b6063489909b5ae79bc7369338)
SERVER-45599 Backport of SERVER-39495: Move ShardingState::needCollectionMetadata under OperationShardingState 2020-01-26T11:13:38+00:00 Kaloian Manassiev kaloian.manassiev@mongodb.com 2018-08-21T14:50:04+00:00 1a01c53df8f7c1e016c0ccbc38b77f6b3508bf65 ShardingState logically contains answers to questions about whether the current instance is node in a sharded cluster, whereas OperationShardingState is responsible for the 'shardedness' of the commands. This is a partial cherry-pick from b049257fbd1d215388cffaf7544f6741dbce5b45, adapted for the 4.0 branch. Also backports the addition of more testing for multi:true/justOne:false updates and ChangeStreams, which was taken from commit 50f6bd4d6a9428a6f1df22db792d7b55d773762c. 
ShardingState logically contains answers to questions about whether the
current instance is node in a sharded cluster, whereas
OperationShardingState is responsible for the 'shardedness' of the
commands.

This is a partial cherry-pick from b049257fbd1d215388cffaf7544f6741dbce5b45, adapted for the 4.0 branch.

Also backports the addition of more testing for multi:true/justOne:false updates and ChangeStreams, which was taken from commit 50f6bd4d6a9428a6f1df22db792d7b55d773762c.