[SERVER-64204] `d_moveChunk` test case must not be skipped in sharded environments Created: 04/Mar/22  Updated: 27/Oct/23  Resolved: 05/Sep/22

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

Type: Task Priority: Major - P3
Reporter: Pierlauro Sciarelli Assignee: Pierlauro Sciarelli
Resolution: Works as Designed Votes: 0
Labels: sharding-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-69460 Complete TODO listed in SERVER-64204 Closed
Sprint: Sharding EMEA 2022-08-08, Sharding EMEA 2022-08-22, Sharding EMEA 2022-09-05
Participants:

 Description   

The d_moveChunk test case is flagged as skipSharded even though the moveChunk command actually only makes sense on sharded clusters.



 Comments   
Comment by Githook User [ 18/Oct/22 ]

Author:

{'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}

Message: SERVER-69460 Complete TODO listed in SERVER-64204
Branch: master
https://github.com/mongodb/mongo/commit/f2a32606a3740070f7deed5feda3604b5a766bee

Comment by Pierlauro Sciarelli [ 05/Sep/22 ]

Thanks for the heads up Marcos! Considering that, we can safely close this ticket.

Comment by Marcos José Grillo Ramirez [ 22/Aug/22 ]

There is already a test for the sharded cluster, which is s_moveChunk, d_moveChunk is simply an auth test, and that's why it has 'expectFail: true'. Is there something specifically that you had in mind with this ticket or could we close it pierlauro.sciarelli@mongodb.com?

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