Details
-
Bug
-
Status: Resolved
-
Minor
-
Resolution: Incomplete
-
None
-
None
-
None
Description
Calling ctx.bypass(), where ctx is the ObserverContext object passed in to the region observer's prePut method, results in some inconsistent behavior.
If every other put in the batch is also bypassed, the region observer sees none of these in its postPut method. If there is at least one other put which is not bypassed, the region observer sees all of the puts in the batch including those which were bypassed.
The end result is that, after bypassing a put, that put may or may not end up in the region observer's postPut method. This behavior is dependent solely on which other puts the bypassed put is batched together with.
I tried to find existing tickets for this issue, but was unable to. Apologies if I missed something. The closest issues I could find were HBASE-4331 and HBASE-11503, but those didn't seem to quite hit it.
Additionally, I threw together a quick demonstration of this issue: https://github.com/hwh33/bypass-inconsistency-demo. You can run that demo in memory using the testing utility or against a running cluster. I actually haven't had time to test it against a cluster though, so you may encounter bugs if running in that mode (but hopefully not!).
Attachments
Issue Links
- relates to
-
HBASE-16933 Calls to ObserverContext#bypass in HRegion#processRowsWithLocks are inconsistent
- Open