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/16 13:56:00 UTC

[jira] [Commented] (FLINK-7457) Make dispatcher highly available

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

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

GitHub user tillrohrmann opened a pull request:

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

    [FLINK-7457] Make Dispatcher highly available

    ## What is the purpose of the change
    
    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
    
    ## Brief change log
    
    - Introduce `LeaderElectionService` and `LeaderElectionRetrievalService` for the `Dispatcher` to the `HighAvailabililtyServices`
    - Let the `Dispatcher participate in the leader election process
    - Guard `Dispatcher#submitJob` with leader session id
    
    ## Verifying this change
    
    This change added tests and can be verified as follows:
    
    - Added `DispatcherTest#testLeaderElection` which simulates a leader election process
    
    ## 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 addDispatcherHA

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

    https://github.com/apache/flink/pull/4548.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 #4548
    
----
commit 9be93a9814ac0727015710f6764ce5e6a4166ea7
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

----


> Make dispatcher highly available
> --------------------------------
>
>                 Key: FLINK-7457
>                 URL: https://issues.apache.org/jira/browse/FLINK-7457
>             Project: Flink
>          Issue Type: Improvement
>          Components: Distributed Coordination
>    Affects Versions: 1.4.0
>            Reporter: Till Rohrmann
>            Assignee: Till Rohrmann
>              Labels: flip-6
>
> The dispatcher component should be made highly available similar to the {{ResourceManager}} and the {{JobMasters}}.



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