[
https://issues.apache.org/jira/browse/HBASE-17206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15958071#comment-15958071
]
Hudson commented on HBASE-17206:
--------------------------------
SUCCESS: Integrated in Jenkins build HBase-1.3-JDK7 #139 (See
[https://builds.apache.org/job/HBase-1.3-JDK7/139/])
HBASE-17227 Backported HBASE-17206 to branch-1.3 (antonov: rev
eec476677444922591903d0c255912e7c2f8d2f1)
* (edit)
hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/wal/FSHLog.java
> FSHLog may roll a new writer successfully with unflushed entries
> ----------------------------------------------------------------
>
> Key: HBASE-17206
> URL: https://issues.apache.org/jira/browse/HBASE-17206
> Project: HBase
> Issue Type: Bug
> Components: wal
> Affects Versions: 2.0.0, 1.4.0, 1.1.7, 1.2.4
> Reporter: Duo Zhang
> Assignee: Duo Zhang
> Priority: Critical
> Fix For: 2.0.0, 1.4.0, 1.2.5, 1.1.8
>
> Attachments: HBASE-17206.patch
>
>
> Found it when debugging the flakey TestFailedAppendAndSync.
> The problem is in waitSafePoint.
> {code}
> while (true) {
> if (this.safePointAttainedLatch.await(1, TimeUnit.MILLISECONDS)) {
> break;
> }
> if (syncFuture.isThrowable()) {
> throw new
> FailedSyncBeforeLogCloseException(syncFuture.getThrowable());
> }
> }
> return syncFuture;
> {code}
> If we attach the safe point quick enough then we will bypass the
> syncFuture.isThrowable check and will not throw
> FailedSyncBeforeLogCloseException.
> This may cause incosistency between memstore and wal.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
