[HBASE-18152] [AMv2] Corrupt Procedure WAL file; procedure data stored out of order

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Cannot Reproduce
• Affects Version/s: 2.0.0
• Component/s: Region Assignment
• Assignee: Michael Stack
• Reporter: Michael Stack
• Created: 02/Jun/17 21:41
• Updated: 21/Jul/21 14:25
• Resolved: 25/Oct/18 17:15

Description

I've seen corruption from time-to-time testing. Its rare enough. Often we can get over it but sometimes we can't. It took me a while to capture an instance of corruption. Turns out we are write to the WAL out-of-order which undoes a basic tenet; that WAL content is ordered in line w/ execution.

Below I'll post a corrupt WAL.

Looking at the write-side, there is a lot going on. I'm not clear on how we could write out of order. Will try and get more insight. Meantime parking this issue here to fill data into.

Issue Links

• is related to: HBASE-21354 Procedure may be deleted improperly during master restarts resulting in 'Corrupt'
• relates to: HBASE-20939 There will be race when we call suspendIfNotReady and then throw ProcedureSuspendedException

Sub-Tasks

• Log when master proc wal rolls: Resolved