Michael Miller created ACCUMULO-4699:
----------------------------------------
Summary: Map in SequentialWorkAssigner uses two different keys
Key: ACCUMULO-4699
URL: https://issues.apache.org/jira/browse/ACCUMULO-4699
Project: Accumulo
Issue Type: Bug
Components: replication
Affects Versions: 1.8.1, 1.7.3
Reporter: Michael Miller
Assignee: Josh Elser
Fix For: 1.7.4, 1.8.2, 2.0.0
SequentialWorkAssigner has a map used for tracking replication work called
queuedWorkByPeerName which it quite clearly uses peerName as the key. There is
a line of code in the initializeQueuedWork() method which does a put on the
queuedWorkByPeerName map but uses tableId as the key.
This is a simple code fix but I created a ticket here as it could have further
implications on the replication process.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
