hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "terry zhang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-6446) Replication source will throw EOF exception when hlog size is 0
Date Wed, 25 Jul 2012 03:03:34 GMT

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

terry zhang commented on HBASE-6446:

hi Daniel ,what about check the hlog queue length?  

catch (IOException ioe) {
      if(this.queue.size() != 0){
        LOG.warn(peerClusterZnode + " Got: ", ioe);
      // TODO Need a better way to determinate if a file is really gone but
      // TODO without scanning all logs dir
      if (sleepMultiplier == this.maxRetriesMultiplier) {
        LOG.warn("Waited too long for this file, considering dumping");
        return !processEndOfFile();

this can prevent warning exception print again and again when master rs startup and no data
was put in.
> Replication source will throw EOF exception when hlog size is 0
> ---------------------------------------------------------------
>                 Key: HBASE-6446
>                 URL: https://issues.apache.org/jira/browse/HBASE-6446
>             Project: HBase
>          Issue Type: Bug
>          Components: replication
>    Affects Versions: 0.94.0
>            Reporter: terry zhang
>         Attachments: hbase-6446.patch
> when master cluster startup new hlog which size is 0 will be created. if we start replication,
replication source will print many EOF exception when openreader. I think we need to ignore
this case and do not print so many exception warning log .

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


View raw message