accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Tubbs (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (ACCUMULO-2867) Consolidate Thrift connection helper classes
Date Sat, 07 Jun 2014 17:25:02 GMT

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

Christopher Tubbs updated ACCUMULO-2867:
----------------------------------------

    Issue Type: Sub-task  (was: Improvement)
        Parent: ACCUMULO-756

> Consolidate Thrift connection helper classes
> --------------------------------------------
>
>                 Key: ACCUMULO-2867
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-2867
>             Project: Accumulo
>          Issue Type: Sub-task
>          Components: client, master, replication, tserver
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>            Priority: Minor
>
> Came up during the review of ACCUMULO-378:
> ReplicationClient, MasterClient, and ThriftUtil are all classes with lots of static methods
used to make executing RPC against a remote service much easier with nice constructs (like
getting a typed return object).
> The downside is that they have lots of implicit gotchas contained (implicit retries,
network failure handling, etc), which make them easier to use by the invoking code, but very
complex beasts.
> It would be good to consolidate what we have into a common base, and then provide strong
semantics on each operation that encapsulates how we want each to operate (master ops should
retry quickly, replication ops should retry slowly and give up eventually, etc), and also
allow for testing of these intended implementations.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message