hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Himanshu Vashishtha (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-8229) Replication code logs like crazy if a target table cannot be found.
Date Mon, 01 Apr 2013 17:27:15 GMT

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

Himanshu Vashishtha commented on HBASE-8229:

Yea, I wonder if we show a replication tab on master UI or somewhere which shows some kind
of replication state. Basic errors like table not existing on slave, missing family, or may
be exception thrown by the slave at peer level are shown. That should give some basic idea
to the user. What others think about this?
> Replication code logs like crazy if a target table cannot be found.
> -------------------------------------------------------------------
>                 Key: HBASE-8229
>                 URL: https://issues.apache.org/jira/browse/HBASE-8229
>             Project: HBase
>          Issue Type: Bug
>          Components: Replication
>            Reporter: Lars Hofhansl
>             Fix For: 0.95.0, 0.98.0, 0.94.7
> One of our RS/DN machines ran out of diskspace on the partition to which we write the
log files.
> It turns out we still had a table in our source cluster with REPLICATION_SCOPE=>1
that did not have a matching table in the remote cluster.
> In then logged a long stack trace every 50ms or so, over a few days that filled up our
log partition.
> Since ReplicationSource cannot make any progress in this case anyway, it should probably
sleep a bit before retrying (or at least limit the rate at which it spews out these exceptions
to the log).

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message