[
https://issues.apache.org/jira/browse/HBASE-5009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13174077#comment-13174077
]
ramkrishna.s.vasudevan commented on HBASE-5009:
-----------------------------------------------
@Ted
Not sure how long it may take.. but it should not be too long.. But this will
ensure that the background threads are completed. If not we may get more such
errors
{code}
org.apache.hadoop.ipc.RemoteException:
org.apache.hadoop.hdfs.server.namenode.LeaseExpiredException: No lease on
/hbase/Htable_UFDR_015/914f3eff1aa7649b7a99b8ce86f3f39c/splits/42423e22baa0c02897a27f92a265f2ad/value/1480356236187113033.914f3eff1aa7649b7a99b8ce86f3f39c
File does not exist. [Lease. Holder:
DFSClient_hb_rs_193-195-18-165,20020,1324435953313_1324435953584_377812698_27,
pendingcreates: 1]
at
org.apache.hadoop.hdfs.server.namenode.FSNamesystem.checkLease(FSNamesystem.java:1786)
at
org.apache.hadoop.hdfs.server.namenode.FSNamesystem.checkLease(FSNamesystem.java:1777)
at
org.apache.hadoop.hdfs.server.namenode.FSNamesystem.completeFileInternal(FSNamesystem.java:1834)
at
org.apache.hadoop.hdfs.server.namenode.FSNamesystem.completeFile(FSNamesystem.java:1820)
at
org.apache.hadoop.hdfs.server.namenode.NameNode.complete(NameNode.java:738)
at sun.reflect.GeneratedMethodAccessor21.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:547)
at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:1116)
at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:1112)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:396)
at org.apache.hadoop.ipc.Server$Handler.run(Server.java:1110)
at org.apache.hadoop.ipc.Client.call(Client.java:954)
at org.apache.hadoop.ipc.RPC$Invoker.invoke(RPC.java:245)
at $Proxy6.complete(Unknown Source)
at sun.reflect.GeneratedMethodAccessor17.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
com.huawei.isap.ump.ha.client.RPCRetryAndSwitchInvoker.invokeMethod(RPCRetryAndSwitchInvoker.java:183)
at
com.huawei.isap.ump.ha.client.RPCRetryAndSwitchInvoker.invokeMethod(RPCRetryAndSwitchInvoker.java:171)
at
com.huawei.isap.ump.ha.client.RPCRetryAndSwitchInvoker.invoke(RPCRetryAndSwitchInvoker.java:76)
at $Proxy6.complete(Unknown Source)
at
org.apache.hadoop.hdfs.DFSClient$DFSOutputStream.closeInternal(DFSClient.java:4307)
at
org.apache.hadoop.hdfs.DFSClient$DFSOutputStream.close(DFSClient.java:4211)
at
org.apache.hadoop.fs.FSDataOutputStream$PositionCache.close(FSDataOutputStream.java:63)
at
org.apache.hadoop.fs.FSDataOutputStream.close(FSDataOutputStream.java:88)
at org.apache.hadoop.hbase.io.Reference.write(Reference.java:133)
at
org.apache.hadoop.hbase.regionserver.StoreFile.split(StoreFile.java:651)
at
org.apache.hadoop.hbase.regionserver.SplitTransaction.splitStoreFile(SplitTransaction.java:498)
{code}
> Failure of creating split dir if it already exists prevents splits from
> happening further
> -----------------------------------------------------------------------------------------
>
> Key: HBASE-5009
> URL: https://issues.apache.org/jira/browse/HBASE-5009
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.90.6
> Reporter: ramkrishna.s.vasudevan
> Assignee: ramkrishna.s.vasudevan
> Attachments: HBASE-5009.patch, HBASE-5009_Branch90.patch
>
>
> The scenario is
> -> The split of a region takes a long time
> -> The deletion of the splitDir fails due to HDFS problems.
> -> Subsequent splits also fail after that.
> {code}
> private static void createSplitDir(final FileSystem fs, final Path splitdir)
> throws IOException {
> if (fs.exists(splitdir)) throw new IOException("Splitdir already exits? "
> + splitdir);
> if (!fs.mkdirs(splitdir)) throw new IOException("Failed create of " +
> splitdir);
> }
> {code}
> Correct me if am wrong? If it is an issue can we change the behaviour of
> throwing exception?
> Pls suggest.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
