Bug 617209 - Store: Recovery failure (JERR_MAP_NOTFOUND:)
Summary: Store: Recovery failure (JERR_MAP_NOTFOUND:)
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: qpid-cpp   
(Show other bugs)
Version: Development
Hardware: All Linux
Target Milestone: 1.4
: ---
Assignee: Kim van der Riet
QA Contact: MRG Quality Engineering
Depends On:
TreeView+ depends on / blocked
Reported: 2010-07-22 13:43 UTC by Kim van der Riet
Modified: 2011-07-15 18:10 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2011-07-15 18:10:03 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Kim van der Riet 2010-07-22 13:43:30 UTC
This bug is a regression from checkin r.4033. A logic error in that checkin introduced a bug in which a JERR_MAP_NOTFOUND error may be thrown during journal recovery if the journal being recovered contains an old dequeue record which survives an overwrite while the original enqueue record which it dequeues does not.

This condition is detected by test _st_basic.file_cycle_interleaved, which is part of the long test suite (ie run using make check-long).

Comment 1 Kim van der Riet 2010-07-22 17:12:16 UTC
Also affects similar transactional cases.

Fixed in r.4144.

All tests including the long tests now pass.

The test in comment 1 is incorrect; test _st_basic.recover_file_cycle_block and _st_basic.recover_file_cycle_interleaved will detect this issue.

Comment 2 Kim van der Riet 2010-07-22 17:38:38 UTC
I was mistaken about this bug being in the MRG 1.3 branch. In fact, checkin r.4033 did not make it onto the MRG 1.3 branch in the first place, so this will affect only the trunk (and hence the next major build).

Comment 3 Kim van der Riet 2011-07-15 18:10:03 UTC
This bug was fixed in r.4144, and is hence a part of the 0.10 release, and thus consequently also MRG 2.0.


Note You need to log in before you can comment on or make changes to this bug.