[jira] [Commented] (HBASE-22917) Proc-WAL roll fails always saying someone else has already created log

["Hudson (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HBASE-22917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16964506#comment-16964506 ] 

Hudson commented on HBASE-22917:
--------------------------------

Results for branch branch-2.2
	[build #679 on builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/679/]: (x) *{color:red}-1 overall{color}*
----
details (if available):

(/) {color:green}+1 general checks{color}
-- For more information [see general report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/679//General_Nightly_Build_Report/]




(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2) report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/679//JDK8_Nightly_Build_Report_(Hadoop2)/]


(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3) report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/679//JDK8_Nightly_Build_Report_(Hadoop3)/]


(/) {color:green}+1 source release artifact{color}
-- See build output for details.


(/) {color:green}+1 client integration test{color}


> Proc-WAL roll fails always saying someone else has already created log
> ----------------------------------------------------------------------
>
>                 Key: HBASE-22917
>                 URL: https://issues.apache.org/jira/browse/HBASE-22917
>             Project: HBase
>          Issue Type: Bug
>          Components: proc-v2, wal
>            Reporter: Pankaj Kumar
>            Assignee: Pankaj Kumar
>            Priority: Critical
>             Fix For: 3.0.0, 2.3.0, 2.2.3
>
>
> Recently we met a weird scenario where Procedure WAL roll fails as it is already created by someone else.
> Later while going through the logs and code, observed that during Proc-WAL roll it failed to write the header. On failure file stream is just closed,
> {code}
>  try {
>  ProcedureWALFormat.writeHeader(newStream, header);
>  startPos = newStream.getPos();
>  } catch (IOException ioe) {
>  LOG.warn("Encountered exception writing header", ioe);
>  newStream.close();
>  return false;
>  }
> {code}
> Since we don't delete the corrupted file or increment the *flushLogId*, so on each retry it is trying to create the same *flushLogId* file. However Hmaster failover will resolve this issue, but we should handle it.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)