[
https://issues.apache.org/jira/browse/HBASE-15811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-15811:
--------------------------
Fix Version/s: (was: 1.2.1)
0.98.19
1.1.6
1.2.2
Release Note: We were not waiting on all executors in a batch to
complete which meant a read-your-own-writes could sometimes fail -- especially
if client is loaded; i.e. putting to multiple machines in a cluster. The test
for no-more-executors was damaged by the 0.99/0.98.4 fix "HBASE-11403 Fix race
conditions around Object#notify"
Affects Version/s: 1.0.0
0.98.19
Status: Patch Available (was: Open)
> Batch Get after batch Put does not fetch all Cells
> --------------------------------------------------
>
> Key: HBASE-15811
> URL: https://issues.apache.org/jira/browse/HBASE-15811
> Project: HBase
> Issue Type: Bug
> Components: Client
> Affects Versions: 0.98.19, 1.2.1, 1.0.0, 1.3.0
> Reporter: stack
> Assignee: stack
> Priority: Blocker
> Fix For: 1.3.0, 1.2.2, 1.1.6, 0.98.19
>
> Attachments: 15811.branch-1.patch, Test.java, Test2.java
>
>
> A big batch put followed by a batch get does not always return all Cells put.
> See attached test program by Robert Farr that reproduces the issue. It seems
> to be an issue to do with a cluster of more than one machine. Running against
> a single machine does not have the problem (though the single machine may
> have many regions). Robert was unable to make his program fail with a single
> machine only.
> I reproduced what Robert was seeing running his program. I was also unable to
> make a single machine fail. In a batch of 1000 puts, I see one to three Gets
> fail. I noticed too that if I wait a second after a fail and then re-get, the
> Get succeeds.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
