hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jean-Daniel Cryans (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:34:34 GMT

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

Jean-Daniel Cryans commented on HBASE-6446:

bq. this can prevent warning exception print again and again when master rs startup and no
data was put in.

Like I wrote I'm all for not printing the exception, but I'd still like to keep a message.
More precisely, a message at DEBUG level.

bq. you need to handle it yourself. Replication should NOT swallow the EOF exception.

The current logic is in processEndOfFile(), what it looks like is if there's no other log
in the queue, it will keep retrying to read... unless it's a recovered queue in which case
since it's the end of the last file so it will close that replication stream (since it's considered
all replicated). Finally, if you have an EOF and there's another file in the queue, it means
that the current file cannot be read further and so we move on to the next one.

What is your suggestion?
> 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