Xiangyu Yao
2975b0dc56
SERVER-31553 Update multiversion tests on 3.6
2017-11-28 15:29:06 -05:00
Xiangyu Yao
9ab80a3861
SERVER-29453 Disallow removing featureCompatibilityVersion document and renaming collection
2017-11-22 11:37:25 -05:00
Xiangyu Yao
07c34da05d
SERVER-31740 Make setFeatureCompatibilityVersion idempotent
2017-11-10 10:49:12 -05:00
Tess Avitabile
ba9fe259f5
SERVER-31633 If the featureCompatibilityVersion is 3.6, upgrading, or downgrading, respond to isMaster with minWireVersion=maxWireVersion
2017-10-27 16:24:18 -04:00
Daniel Gottlieb
09388643a6
SERVER-31611: Perform a clean shutdown and downgrade on an interpreted FCV 3.2.
...
There are a few cases where a 3.6 binary will refuse to start up because it
concludes the datafiles belong to a 3.2 mongod. In those cases, the server
must perform a clean shutdown that ensures datafiles are downgraded to a
format that older binaries can understand.
2017-10-27 09:13:06 -04:00
Tess Avitabile
23e886eebf
SERVER-31630 getParameter for featureCompatibilityVersion must expose targetVersion
2017-10-25 12:18:07 -04:00
Tess Avitabile
5d4b316b24
SERVER-31634 FeatureCompatibilityVersion::setIfCleanStartup() should store FCV=3.4 for shardsvrs
2017-10-24 10:03:33 -04:00
Maria van Keulen
e739ab399c
SERVER-29452 Correctly obtain the UUID of a collection in setfcv test
2017-10-20 16:05:24 -04:00
Tess Avitabile
ddacafb225
SERVER-31531 featureCompatibilityVersion writes must check for writeErrors
2017-10-18 16:38:34 -04:00
Nathan Myers
aeabbf96ff
SERVER-31191 Plumb Collection UUIDs through catalog cache
2017-10-17 14:07:38 -04:00
Spencer T Brody
8b9703b98b
SERVER-31277 Cancel all user operations on heartbeat stepdown path
2017-10-16 18:05:08 -04:00
Maria van Keulen
c9ca12d30b
SERVER-29452 Handle missing featureCompatibilityVersion document
2017-10-16 17:41:56 -04:00
Esha Maharishi
6787c13d49
SERVER-30793 merge setFeatureCompatibilityVersion and _configsvrSetFeatureCompatibilityVersion
2017-10-09 10:24:55 -04:00
Esha Maharishi
62fe0f89e9
SERVER-30511 call checkUUIDsConsistentAcrossCluster() before shutting down a ShardingTest
2017-09-25 11:27:23 -04:00
Esha Maharishi
6dd8ca2e84
SERVER-29759 on _configsvrSetFeatureCompatibilityVersion=3.6, generate and persist UUIDs for existing sharded collections
2017-06-26 17:33:28 -04:00
Tess Avitabile
19fb2eca83
SERVER-29798 Ensure 3.4 secondary replicates featureCompatibilityVersion document in set_feature_compatibility_version.js
2017-06-22 17:13:51 -04:00
Tess Avitabile
67500efdc1
SERVER-29350 Bump featureCompatibilityVersion to 3.6
2017-06-09 15:05:04 -04:00
Robert Guo
b2bca3948f
SERVER-27107 remove or modify tests unrelated to the 3.4->3.6 upgrade path
2016-12-14 11:26:18 -05:00
Randolph Tan
26cb6b14f4
SERVER-26610 add maxTimeMS to setFeatureCompatibilityVersion call in set_feature_compatibility_version.js
2016-10-17 13:31:43 -04:00
Maria van Keulen
fadd01e32d
SERVER-26265 Add tests for 3.2 mongos joining 3.4 clusters
2016-10-10 11:36:10 -04:00
Judah Schvimer
da47772085
SERVER-26322 Use reconfig helper in multiversion tests
2016-09-26 14:38:36 -04:00
Max Hirschhorn
96a21e63bf
SERVER-25725 Kill 3.2 secondaries when featureCompatibilityVersion=3.4.
...
Creates a v=2 index on the "admin.system.version" collection when the
featureCompatibilityVersion is set to 3.4. The index version of this
index is returned as a decimal value in the "listIndexes" command
response in order to prevent 3.2 secondaries from performing initial
sync from a 3.4 mongod with featureCompatibilityVersion=3.4.
2016-09-20 19:07:55 -04:00
David Storch
63582d3c29
SERVER-26087 make config server only set its own featureCompatibilityVersion if all shards report success
2016-09-14 14:16:43 -04:00
Tess Avitabile
ac055bb958
SERVER-25739 set_feature_compatibility_version.js should not use 3.4 mongos to add 3.2 shard
2016-08-24 15:55:43 -04:00
Tess Avitabile
dc4a079760
SERVER-25155 Create setFeatureCompatibilityVersion command
2016-08-19 17:57:33 -04:00
