[ https://issues.apache.org/jira/browse/HBASE-22917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17114590#comment-17114590 ]
Anoop Sam John commented on HBASE-22917: ---------------------------------------- bq.And maybe it is safe to just increase the file id without deleting the broken proc wal file(this is a typical solution in WAL based system), but anyway, usually deleting a wal file is not a good idea.. [~pankaj2461] Following this suggestion also ur issue can be solved right? Want to give a patch? > 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: 2.2.6 > > > 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)