[
https://issues.apache.org/jira/browse/ACCUMULO-4699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16150823#comment-16150823
]
Michael Miller commented on ACCUMULO-4699:
------------------------------------------
Josh Elser Could this be causing periodic time out of CyclicReplicationIT?
https://jenkins.revelc.net/job/Accumulo-2.0-ITs/lastBuild/org.apache.accumulo$accumulo-test/testReport/org.apache.accumulo.test.replication/CyclicReplicationIT/dataIsNotOverReplicated/
> 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.7.3, 1.8.1
> 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)
