[ACCUMULO-4699] Map in SequentialWorkAssigner uses two different keys

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.7.3, 1.8.1
• Fix Version/s: 1.7.4, 1.9.0
• Component/s: replication
• Assignee: Michael Miller
• Reporter: Michael Miller
• Created: 01/Sep/17 16:45
• Updated: 23/Apr/19 16:12
• Resolved: 06/Sep/17 15:20

Description

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.

Issue Links

• is depended upon by: ACCUMULO-4662 Fix ambiguous table references
• links to: GitHub Pull Request #295