[
https://issues.apache.org/jira/browse/HBASE-14234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Yuan Jiang updated HBASE-14234:
---------------------------------------
Component/s: proc-v2
> Procefure-V2: Exception encountered in WALProcedureStore#rollWriter() should
> be properly handled
> ------------------------------------------------------------------------------------------------
>
> Key: HBASE-14234
> URL: https://issues.apache.org/jira/browse/HBASE-14234
> Project: HBase
> Issue Type: Bug
> Components: proc-v2
> Reporter: Ted Yu
> Assignee: Ted Yu
> Priority: Minor
> Fix For: 2.0.0, 1.2.0, 1.1.2, 1.3.0
>
> Attachments: 14234-v1.txt
>
>
> Observed the following in recent Jenkins build
> (https://builds.apache.org/job/HBase-TRUNK/6732/console):
> {code}
> testWALfencingWithoutWALRolling(org.apache.hadoop.hbase.master.procedure.TestMasterFailoverWithProcedures)
> Time elapsed: 9.938 sec <<< ERROR!
> org.apache.hadoop.ipc.RemoteException: failed to create file
> /user/jenkins/test-data/0d9e3047-6bb1-4219-9ed2-5b9884176321/MasterProcWALs/state-00000000000000000002.log
> for DFSClient_NONMAPREDUCE_-966558185_1 for client 127.0.0.1 because current
> leaseholder is trying to recreate file.
> at
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.recoverLeaseInternal(FSNamesystem.java:2589)
> at
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.startFileInternal(FSNamesystem.java:2386)
> {code}
> When file creation fails (e.g. due to RemoteException), we should handle the
> exception by returning false.
> Similar handling can be applied to failure in writing header.
> Thanks to [~mbertozzi] for offline discussion.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
