You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "ramkrishna.s.vasudevan (JIRA)" <ji...@apache.org> on 2014/12/30 05:36:13 UTC

[jira] [Resolved] (HBASE-5323) Need to handle assertion error while splitting log through ServerShutDownHandler by shutting down the master

     [ https://issues.apache.org/jira/browse/HBASE-5323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

ramkrishna.s.vasudevan resolved HBASE-5323.
-------------------------------------------
    Resolution: Won't Fix

0.90.x version is no more active. Resolving as 'Won't fix'.

> Need to handle assertion error while splitting log through ServerShutDownHandler by shutting down the master
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-5323
>                 URL: https://issues.apache.org/jira/browse/HBASE-5323
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 0.90.5
>            Reporter: ramkrishna.s.vasudevan
>            Assignee: ramkrishna.s.vasudevan
>         Attachments: HBASE-5323.patch, HBASE-5323.patch
>
>
> We know that while parsing the HLog we expect the proper length from HDFS.
> In WALReaderFSDataInputStream
> {code}
>               assert(realLength >= this.length);
> {code}
> We are trying to come out if the above condition is not satisfied.  But if SSH.splitLog() gets this problem then it lands in the run method of EventHandler.  This kills the SSH thread and so further assignment does not happen.  If ROOT and META are to be assigned they cannot be.
> I think in this condition we abort the master by catching such exceptions.
> Please do suggest.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)