Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Thu, 4 Apr 2013 21:18:23 +0000 (UTC)
From: "Hudson (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12639914.1364624673973.110420.1365110303791@arcas>
In-Reply-To: <JIRA.12639914.1364624673973@arcas>
References: <JIRA.12639914.1364624673973@arcas>
Subject: [jira] [Commented] (HBASE-8229) Replication code logs like crazy if
 a target table cannot be found.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Hudson commented on HBASE-8229:
-------------------------------

Integrated in HBase-0.94-security #130 (See [https://builds.apache.org/job/HBase-0.94-security/130/])
    HBASE-8229 Replication code logs like crazy if a target table cannot be found. (Revision 1464275)

     Result = FAILURE
larsh : 
Files : 
* /hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/replication/regionserver/ReplicationSource.java

                
> 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.1, 0.98.0, 0.94.7
>
>         Attachments: 8229-0.94.txt
>
>
> 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