You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/08/26 15:52:02 UTC

[jira] [Commented] (FLINK-7528) Create Dispatcher REST endpoint

    [ https://issues.apache.org/jira/browse/FLINK-7528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16142852#comment-16142852 ] 

ASF GitHub Bot commented on FLINK-7528:
---------------------------------------

GitHub user tillrohrmann opened a pull request:

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

    [FLINK-7528] Create DispatcherRestEndpoint and integrate with Dispatcher

    ## What is the purpose of the change
    
    This commit creates the DispatcherRestEndpoint and integrates it with the
    Dispatcher. The DispatcherRestEndpoint is created in the SessionClusterEntrypoint
    and its address is passed to the Dispatcher such that it can answer the
    requestRestAddress RPC.
    
    ## Brief change log
    
    - Create the `DispatcherRestEndpoint`
    - Start `DispatcherRestEndpoint` in `SessionClusterEntrypoint`
    - Pass in REST address to Dispatcher and JobManager
    - Resolve redirection address by directly ask leader component
    
    ## Verifying this change
    
    Verified manually that the `DispatcherRestEndpoint` is started and reachable (even though it does not serve anything yet).
    
    ## Does this pull request potentially affect one of the following parts:
    
      - Dependencies (does it add or upgrade a dependency): (no)
      - The public API, i.e., is any changed class annotated with `@Public(Evolving)`: (no)
      - The serializers: (no)
      - The runtime per-record code paths (performance sensitive): (no)
      - Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (no)
    
    ## Documentation
    
      - Does this pull request introduce a new feature? (no)
      - If yes, how is the feature documented? (not applicable)
    


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

    $ git pull https://github.com/tillrohrmann/flink dispatcherRestEndpoint

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

    https://github.com/apache/flink/pull/4598.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 #4598
    
----
commit 7835d0a89c8ecdd5b9661ee8c57a9d63a3ed3742
Author: Till Rohrmann <tr...@apache.org>
Date:   2017-08-14T13:47:04Z

    [FLINK-7522] Add termination future to ClusterEntrypoint
    
    The termination future is completed when the ClusterEntrypoint shuts down. This
    allows for easier testing.

commit 2cdf97f824bc62a82e65f4c160b9ad64de446de4
Author: Till Rohrmann <tr...@apache.org>
Date:   2017-08-16T12:36:13Z

    [FLINK-7457] Make Dispatcher highly available
    
    This commit introduces a dispatcher leader election and retrieval service to the
    HighAvailabilityServices. Moreover it adds code such that the Dispatcher now takes
    part in the leader election process using the afore-mentioned services.
    
    Let Dispatcher participate in leader election
    
    Add test for Dispatcher leader election

commit 04caf85d33ddfc3a4a9b788745b8282c3437d8e2
Author: Till Rohrmann <tr...@apache.org>
Date:   2017-08-10T08:56:12Z

    [FLINK-7409] [web] Make WebRuntimeMonitor reactive
    
    This commit changes the behaviour of the WebRuntimeMonitor to not longer block serving
    threads by waiting on the result of futures. Instead the RequestHandler now returns a
    CompletableFuture<FullHttpResponse> which is written out to the Netty channel upon
    completion. This will improve the performance of our WebRuntimeMonitor.

commit 4fa6dedd95555a2d1a91339ff5effda3bc2bd1d5
Author: Till Rohrmann <tr...@apache.org>
Date:   2017-08-15T10:00:58Z

    [FLINK-7458] Generalize GatewayRetriever for WebRuntimeMonitor
    
    Introduce a generalized GatewayRetriever replacing the JobManagerRetriever. The
    GatewayRetriever fulfills the same purpose as the JobManagerRetriever with the
    ability to retrieve the gateway for an arbitrary endpoint type.

commit 0f9b2ce77e20f25fc95ddeba98f863b86450a72c
Author: Till Rohrmann <tr...@apache.org>
Date:   2017-08-15T11:55:47Z

    [FLINK-7459] Generalize Flink's redirection logic
    
    Introduce RedirectHandler which can be extended to add redirection functionality to all
    SimpleInboundChannelHandlers. This allows to share the same functionality across the
    StaticFileServerHandler and the RuntimeMonitorHandlerBase which could now be removed.
    In the future, the AbstractRestHandler will also extend the RedirectHandler.

commit 88aed4f7a198b3994271088b8e19558d399ddd9d
Author: Till Rohrmann <tr...@apache.org>
Date:   2017-08-17T13:04:19Z

    [FLINK-7527] [rest] Let AbstractRestHandler extend RedirectHandler
    
    By letting the AbstractRestHandler extend the RedirectHandler, we add redirection
    capabilities to the AbstractRestHandler.

commit 9b7de1dc21b771fc10ee1661f34c142e990b424f
Author: Till Rohrmann <tr...@apache.org>
Date:   2017-08-17T13:25:33Z

    [FLINK-7528] Create DispatcherRestEndpoint and integrate with Dispatcher
    
    This commit creates the DispatcherRestEndpoint and integrates it with the
    Dispatcher. The DispatcherRestEndpoint is created in the SessionClusterEntrypoint
    and its address is passed to the Dispatcher such that it can answer the
    requestRestAddress RPC.

----


> Create Dispatcher REST endpoint
> -------------------------------
>
>                 Key: FLINK-7528
>                 URL: https://issues.apache.org/jira/browse/FLINK-7528
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Distributed Coordination, REST
>    Affects Versions: 1.4.0
>            Reporter: Till Rohrmann
>            Assignee: Till Rohrmann
>            Priority: Minor
>              Labels: flip-6
>
> Create and integrate the {{DispatcherRestEndpoint}} with the {{Dispatcher}}.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)