Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Wed, 25 Jul 2012 03:58:36 +0000 (UTC)
From: "terry zhang (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <1413141303.99741.1343188716400.JavaMail.jiratomcat@issues-vm>
In-Reply-To: <699562386.95104.1343125354906.JavaMail.jiratomcat@issues-vm>
Subject: [jira] [Updated] (HBASE-6446) Replication source will throw EOF
 exception when hlog size is 0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/HBASE-6446?page=3Dcom.atlassia=
n.jira.plugin.system.issuetabpanels:all-tabpanel ]

terry zhang updated HBASE-6446:
-------------------------------

    Attachment: hbase-6446-v2.patch

OK=EF=BC=8CDaniel. Let's change it from warning level to debug level to pre=
vent warning in online cluster.
               =20
> 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 e=
xception warning log .

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrato=
rs: https://issues.apache.org/jira/secure/ContactAdministrators!default.jsp=
a
For more information on JIRA, see: http://www.atlassian.com/software/jira