[SERVER-21204] Majority read fails after captrunc test command Created: 29/Oct/15  Updated: 03/Nov/15  Resolved: 03/Nov/15

Status: Closed
Project: Core Server
Component/s: Querying, Replication, Storage
Affects Version/s: 3.2.0-rc0
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Michael Grundy Assignee: Mathias Stearn
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Operating System: ALL
Steps To Reproduce:

python buildscripts/resmoke.py   --executor read_concern_majority_passthrough jstests/core/capped6.js

Sprint: QuInt C (11/23/15)
Participants:

 Description   

The check that documents are in order (checkOrder) fails and it seems that it might be getting data from an older snapshot.



 Comments   
Comment by Mathias Stearn [ 03/Nov/15 ]

Initially, I thought the issue was that the captruc command wasn't being intercepted by the test harness. Once I solved that, I realized it doesn't even make sense to test this feature in this way. captruc is a test-only command that isn't replicated. Therefore it doesn't make sense to mix it with read or write concern. It allows us to directly poke at functionality used by replication to do its job and isn't something that is intended to be used on its own.

I propose closing as works as designed.

Comment by J Rassi [ 03/Nov/15 ]

redbeard0531, would you mind investigating?

Generated at Thu Feb 08 03:56:38 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.