accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-4699) Map in SequentialWorkAssigner uses two different keys
Date Fri, 01 Sep 2017 17:30:01 GMT

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

Josh Elser commented on ACCUMULO-4699:
--------------------------------------

I wouldn't know how, [~milleruntime], as I don't believe the Master is restarted in that test.

> 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
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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)

Mime
View raw message