[ https://issues.apache.org/jira/browse/HBASE-16768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15552890#comment-15552890 ]
ChiaPing Tsai commented on HBASE-16768: --------------------------------------- I follow the logic of HStore#add(cell) which uses the read lock also. According to the comments in HStore, the MemStore is assumed to be thread safe. So it use the read lock. > Inconsistent results from the Append/Increment > ---------------------------------------------- > > Key: HBASE-16768 > URL: https://issues.apache.org/jira/browse/HBASE-16768 > Project: HBase > Issue Type: Bug > Reporter: ChiaPing Tsai > Assignee: ChiaPing Tsai > Priority: Minor > Fix For: 2.0.0 > > Attachments: HBASE-16768.v0.patch, HBASE-16768.v1.patch, > HBASE-16768.v2.patch > > > If the Append/Increment skips the WAL, the sequential id will not be updated. > It introduces that the AbstractMemStore#upsert may remove the cell even > though the cell is visible to the oldest scanner. -- This message was sent by Atlassian JIRA (v6.3.4#6332)