GitHub user StephanEwen opened a pull request:

    https://github.com/apache/flink/pull/2360

    [FLINK-4384] [rpc] Add "scheduleRunAsync()" to the RpcEndpoint

    NOTE: This builds on top of #2357 - only the second commit belongs actually 
to this pull request is relevant.
    
    Add a `scheduleRunAsync()` method to the `RpcEndpoint`. It behaves like 
`runAsync()` but delays the call by a given number of milliseconds. The delay 
does not happen by a thread sleep, but by scheduling the message that triggers 
the Runnable it into the future of the message dispatcher.
    
    This also adds tests for the `runAsync()`, `scheduleRunAsync()`, and 
`callAsync()` that validate that all these calls actually run in the same 
thread (the RPC endpoint's main thread).

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

    $ git pull https://github.com/StephanEwen/incubator-flink schedule_future

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

    https://github.com/apache/flink/pull/2360.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 #2360
    
----
commit 13f6f392943e32b14bf0d08c7ded2d88496911ab
Author: Till Rohrmann <trohrm...@apache.org>
Date:   2016-08-10T16:42:26Z

    [FLINK-4362] [rpc] Auto generate rpc gateways via Java proxies
    
    This PR introduces a generic AkkaRpcActor which receives rpc calls as a
    RpcInvocation message. The RpcInvocation message is generated by the
    AkkaInvocationHandler which gets them from automatically generated Java 
Proxies.
    
    Add documentation for proxy based akka rpc service

commit 7b9eb2f3de23a7bee28346664ff39e0c28235a6e
Author: Stephan Ewen <se...@apache.org>
Date:   2016-08-11T17:10:48Z

    [FLINK-4384] [rpc] Add "scheduleRunAsync()" to the RpcEndpoint

----


---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to