[
https://issues.apache.org/jira/browse/ACCUMULO-4456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15878533#comment-15878533
]
Josh Elser commented on ACCUMULO-4456:
--------------------------------------
bq. After removing the code which was no longer needed, I saw that the
ReplicationCoordinator.Processor<ReplicationCoordinator.Iface>
replicationCoordinatorProcessor wasn't wrapping the haReplicationProxy, and
that the latter was left unused.
Sounds like an unintentional omission. There's no reason that the replication
thrift server should be any different than the others.
> 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)
