TestAtomicOperation.testMultiRowMutationMultiThreads fails occasionally -----------------------------------------------------------------------
Key: HBASE-5569 URL: https://issues.apache.org/jira/browse/HBASE-5569 Project: HBase Issue Type: Bug Reporter: Lars Hofhansl Priority: Minor What I pieces together so far is that it is the *scanning* side that has problems sometimes. Every time I see a assertion failure in the log I see this before: {quote} 2012-03-12 21:48:49,523 DEBUG [Thread-211] regionserver.StoreScanner(499): Storescanner.peek() is changed where before = rowB/colfamily11:qual1/75366/Put/vlen=6,and after = rowB/colfamily11:qual1/75203/DeleteColumn/vlen=0 {quote} The order of if the Put and Delete is sometimes reversed. The test threads should always see exactly one KV, if the "before" was the Put the thread see 0 KVs, if the "before" was the Delete the threads see 2 KVs. This debug message comes from StoreScanner to checkReseek. It seems we still some consistency issue with scanning sometimes :( -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira