You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Lars Hofhansl (JIRA)" <ji...@apache.org> on 2013/03/30 07:25:15 UTC

[jira] [Created] (HBASE-8229) Replication code logs like crazy if a target table cannot be found.

Lars Hofhansl created HBASE-8229:
------------------------------------

             Summary: 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
            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