Rollback: MagmaKVStore vbstate vbid:304 not found. Status:NotFound: MagmaKVStore::readLocalDoc(vbid:vb:304 key:_vbstate not found.

Description

As per discussion with , after WAL corruption is detected Magma-Open should fail and should have propagated the error instead after detection magma has proceeded normally. This could lead to data loss.

Components

Affects versions

Fix versions

Environment

http://server.jenkins.couchbase.com/job/toy-unix/6411/artifact/couchbase-server-enterprise-6.5.0-42-centos7.x86_64.rpm

Link to Log File, atop/blg, CBCollectInfo, Core dump

https://cb-jira.s3.us-east-2.amazonaws.com/logs/rollback/collectinfo-2020-02-04T044836-ns_1%40172.23.105.220.zip https://cb-jira.s3.us-east-2.amazonaws.com/logs/rollback/collectinfo-2020-02-04T044836-ns_1%40172.23.105.221.zip

Release Notes Description

None

Activity

Show:

Ritesh Agarwal February 26, 2021 at 5:46 AM

Not seeing this issue on the 7.0.0-4502. Verified-Closing the defect.

CB robot April 17, 2020 at 7:16 PM

Build couchbase-server-6.6.0-1000 contains magma commit 1588fb3 with commit message:
magma: Fix recovery not checking batch iterator status correctly

Apaar Gupta February 14, 2020 at 3:18 PM

This bug was open cos magma was not failing the Magma::Open despite iterator reporting corruption. This was resulting in data going missing after the open since wal iterator had not completed replay. This has been fixed in the linked patch.

CB robot February 14, 2020 at 12:16 PM

Build couchbase-server-1006.5.1-1058 contains magma commit 1588fb3 with commit message:
magma: Fix recovery not checking batch iterator status correctly

CB robot February 14, 2020 at 10:20 AM

Build couchbase-server-7.0.0-1340 contains magma commit 1588fb3 with commit message:
magma: Fix recovery not checking batch iterator status correctly

Fixed
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Apaar Gupta

Reporter

Is this a Regression?

Unknown

Triage

Untriaged

Priority

Instabug

Open Instabug

PagerDuty

Sentry

Zendesk Support

Created February 4, 2020 at 6:32 AM
Updated June 17, 2021 at 10:56 PM
Resolved February 14, 2020 at 3:18 PM
Instabug
Loading...