[jira] [Commented] (HBASE-25583) Handle the NoNode exception in remove log replication and avoid crash

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

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

Wellington Chevreuil commented on HBASE-25583:
----------------------------------------------

I see a PR to branch-1 named linked to another Jira HBASE-25582. I believe it has been mistakenly named to that jira, as description matches to this one. Please update the PR title. And please edit the "Affects Version/s" field here to reflect all versions where you had identified this problem.

> Handle the NoNode exception in remove log replication and avoid crash
> ---------------------------------------------------------------------
>
>                 Key: HBASE-25583
>                 URL: https://issues.apache.org/jira/browse/HBASE-25583
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Sandeep Pal
>            Assignee: Sandeep Pal
>            Priority: Major
>
> Should not crash the region server it there is a NoNode exception while removing the log
> We should look into the excpetion and if it is NoNode we shouldn't crash. There might be a possiblity the node was deleted as part of peer tear down. 
> `  @Override
>   public void removeLog(String queueId, String filename) {
>     try {
>       String znode = ZKUtil.joinZNode(this.myQueuesZnode, queueId);
>       znode = ZKUtil.joinZNode(znode, filename);
>       ZKUtil.deleteNode(this.zookeeper, znode);
>     } catch (KeeperException e) {
>       this.abortable.abort("Failed to remove wal from queue (queueId=" + queueId + ", filename="
>           + filename + ")", e);
>     }
>   }



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