[SERVER-41875] Should ban "emptyCapped" commands on jstestfuzz_concurrent_replication_continuous__stepdown suite for WiredTiger Storage. Created: 21/Jun/19  Updated: 29/Oct/23  Resolved: 03/Sep/19

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 4.3.1, 4.2.16

Type: Task Priority: Major - P3
Reporter: Suganthi Mani Assignee: Suganthi Mani
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Related
related to SERVER-34853 rollback (or replay during recovery) ... Closed
Backwards Compatibility: Fully Compatible
Backport Requested:
v4.2
Sprint: Repl 2019-07-01, Repl 2019-08-12, Repl 2019-08-26, Repl 2019-09-09
Participants:
Linked BF Score: 17

 Description   

"emptyCapped" is a test-only command which is not supported if rollback is via RTT. Since, it is a test only command, it's okay to be less targeted. So, we can ban "emptyCapped" command entirely for wiredTigerStorageEngine regardless of rollback type.

Note: We should also file a TIG ticket to make changes in jstestfuzz repo.



 Comments   
Comment by Githook User [ 06/Jul/21 ]

Author:

{'name': 'Suganthi Mani', 'email': 'suganthi.mani@mongodb.com', 'username': 'smani87'}

Message: SERVER-41875 Should ban 'emptycapped' commands on jstestfuzz_concurrent_replication_continuous_stepdown suite for WiredTiger Storage.

(cherry picked from commit 32d77aa09d188b1ff289305d9645b59881a57729)
Branch: v4.2
https://github.com/mongodb/mongo/commit/52414df4548983bd5cd0e100921e6228c5a6ae16

Comment by Pavithra Vetriselvan [ 07/Jun/21 ]

Yep, that all sounds right to me! Thank you for confirming, I can request the backports and assign them to Replication.

Comment by Suganthi Mani [ 07/Jun/21 ]

pavithra.vetriselvan, We should ban the "emptyCapped" command for storage engines that support RTT. When I banned the command for WiredTiger, I was expecting the ban to apply for both durable and in-memory variant of WiredTiger. Also, my understanding is that currently we only have wiredTiger that supports RTT.

Looking at BF-21292, it seems we just need to backport this ticket and TIG-1938 to 4.2, am I correct?

Comment by Pavithra Vetriselvan [ 28/May/21 ]

suganthi.mani Is there a reason we banned "emptyCapped" only for WT? I'm seeing a jstestfuzz 4.2 BF, BF-21292, on the inMemory variant that fails because "emptyCapped" is unsupported in RTT. I would expect that we need to ban this command for inMemory variants as well.

Comment by Githook User [ 03/Sep/19 ]

Author:

{'name': 'Suganthi Mani', 'username': 'smani87', 'email': 'suganthi.mani@mongodb.com'}

Message: SERVER-41875 Should ban 'emptycapped' commands on jstestfuzz_concurrent_replication_continuous_stepdown suite for WiredTiger Storage.
Branch: master
https://github.com/mongodb/mongo/commit/32d77aa09d188b1ff289305d9645b59881a57729

Generated at Thu Feb 08 04:58:55 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.