You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@accumulo.apache.org by "Christopher Tubbs (JIRA)" <ji...@apache.org> on 2017/02/22 20:33:44 UTC

[jira] [Resolved] (ACCUMULO-4456) Fix exclusion on answering RPCs when lock is not acquired

     [ https://issues.apache.org/jira/browse/ACCUMULO-4456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Christopher Tubbs resolved ACCUMULO-4456.
-----------------------------------------
    Resolution: Fixed

I think your phrasing is preventing me from clearly ascertaining your opinion. However, I *think* you're saying that my fix is correct, so I will re-close, this issue, since I've merged that. Thanks!

> Fix exclusion on answering RPCs when lock is not acquired
> ---------------------------------------------------------
>
>                 Key: ACCUMULO-4456
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-4456
>             Project: Accumulo
>          Issue Type: Sub-task
>          Components: client, master
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>             Fix For: 2.0.0
>
>          Time Spent: 2h 50m
>  Remaining Estimate: 0h
>
> [~kturner] asked me a good question about what the client does when it tries to talk to a master which has recently lost its active status, how does the client handle the thrown exception?
> Should run a quick local test.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)