[
https://issues.apache.org/jira/browse/HBASE-6446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13421967#comment-13421967
]
Jimmy Xiang commented on HBASE-6446:
------------------------------------
About 0 length HLog file, I filed HBASE-6443 last week. When a new HLog file is
created, its size is 0. My understanding is that it is not replicated since it
is still in use. Only those closed HLog file will be replicated. Correct me if
I am wrong. So in this case, you may have a corrupted HLog file. Just like in
HBASE-6443, you need to handle it yourself. Replication should NOT swallow the
EOF exception.
> 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
