[SERVER-45655] refine_collection_shard_key_basic.js shouldn't check for changelog entries on sharding_csrs_continuous_config_stepdown suite Created: 20/Jan/20  Updated: 29/Oct/23  Resolved: 21/Jan/20

Status: Closed
Project: Core Server
Component/s: Sharding, Testing Infrastructure
Affects Version/s: None
Fix Version/s: 4.3.3

Type: Bug Priority: Major - P3
Reporter: Tommaso Tocci Assignee: Tommaso Tocci
Resolution: Fixed Votes: 0
Labels: sharding-csrs-stepdown-upkeep
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Problem/Incident
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding 2020-01-27
Participants:
Linked BF Score: 16

 Description   

refine_collection_shard_key_basic.js checks if entries associated with refineCollectionShardKey are correctly inserted into the changelog.
In the case that the primary stepdown do to a failure, it is not guaranteed that these entries are committed on the changelog.
In particular for every refineCollectionShardKey operation it could be possible to have:

  • one or more `refineCollectionShardKey.start` entry in the changelog SERVER-43201
  • one or zero `refineCollectionShardKey.end` entry in the changelog. SERVER-44099

Unfortunately the two implemented solution failed to address the problem.

The bug was introduced by:
https://github.com/mongodb/mongo/commit/76208a78621cfe67d417a5781f9202580f1b2608



 Comments   
Comment by Githook User [ 21/Jan/20 ]

Author:

{'username': 'toto-dev', 'name': 'Tommaso Tocci', 'email': 'tommaso.tocci@mongodb.com'}

Message: SERVER-45655 fix refine_collection_shard_key_basic.js under continuous_config_stepdown suite

refine_collection_shard_key_basic.js checks if entries associated with
refineCollectionShardKey are correctly inserted into the changelog.
In the case that the primary stepdown do to a failure,
it is not guaranteed that these entries are committed on the changelog.

This commit introduces the following changes:

  • refine_collection_shard_key_basic.js does not perform any check on
    the changelog entries so that it can be run in the continuous_config_stepdown suite.
  • introduces a new refine_collection_shard_key_changelog.js test with the only purpose of checking
    that changelog entries are inserted correctly for the refineCollectionShardKey operation.
    This test is blacklisted in the continuous_config_stepdown suite.

create mode 100644 jstests/sharding/refine_collection_shard_key_changelog.js
Branch: master
https://github.com/mongodb/mongo/commit/1539a4c9dd24a257cc073bbf291c2015c45f905c

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