accumulo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From joshelser <...@git.apache.org>
Subject [GitHub] accumulo pull request: ACCUMULO-4065 Create a separate connection ...
Date Mon, 30 Nov 2015 20:18:51 GMT
GitHub user joshelser opened a pull request:

    https://github.com/apache/accumulo/pull/54

    ACCUMULO-4065 Create a separate connection cache for oneway Thrift ca…

    …lls.
    
    Oneway Thrift calls return to the caller before the response from a server
    is received. Even though all oneway calls are void methods, there is still
    an implicit response sent by the server so that the client knows when
    the RPC has completed. Because of this potential delay, a connection that
    is re-used by a non-oneway call could see the response from the oneway
    call, not its own (void or typed response message). We must separate
    connections to ensure that this is avoided.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/joshelser/accumulo ACCUMULO-4065-oneway-isolation

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/accumulo/pull/54.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #54
    
----
commit 55e05fc11c04cae42dbba9b3ec1d6138b9bfd85b
Author: Josh Elser <elserj@apache.org>
Date:   2015-11-27T23:27:24Z

    ACCUMULO-4065 Create a separate connection cache for oneway Thrift calls.
    
    Oneway Thrift calls return to the caller before the response from a server
    is received. Even though all oneway calls are void methods, there is still
    an implicit response sent by the server so that the client knows when
    the RPC has completed. Because of this potential delay, a connection that
    is re-used by a non-oneway call could see the response from the oneway
    call, not its own (void or typed response message). We must separate
    connections to ensure that this is avoided.

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

Mime
View raw message