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

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.98.0, 0.94.7, 0.95.1
• Component/s: Replication
• Assignee: Lars Hofhansl
• Reporter: Lars Hofhansl
• Created: 30/Mar/13 06:24
• Updated: 27/Apr/13 15:55
• Resolved: 04/Apr/13 03:51

Description

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).