[
https://issues.apache.org/jira/browse/HBASE-6446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13422446#comment-13422446
]
Jean-Daniel Cryans commented on HBASE-6446:
-------------------------------------------
bq. I think we should not keep retrying. We can retry for some configurable
times, then log an error and skip this file. A bad file should not break the
system
In which case? Let's say the RS got a 0 length file, then creates a new HLog.
Here the replication code will do the right thing and move on.
bq. OKļ¼Daniel. Let's change it from warning level to debug level to prevent
warning in online cluster.
I was also thinking that we should not print the stack trace.
> 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-v2.patch, 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
