flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From GJL <...@git.apache.org>
Subject [GitHub] flink pull request #6239: [FLINK-9004][tests] Implement Jepsen tests to test...
Date Mon, 02 Jul 2018 12:19:48 GMT
GitHub user GJL opened a pull request:

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

    [FLINK-9004][tests] Implement Jepsen tests to test job availability.

    ## What is the purpose of the change
    
    *Use the Jepsen framework (https://github.com/jepsen-io/jepsen) to implement
    tests that verify Flink's HA capabilities under real-world faults, such as
    sudden TaskManager/JobManager termination, HDFS NameNode unavailability, network
    partitions, etc. The Flink cluster under test is automatically deployed on YARN
    (session & job mode) and Mesos.
    
    Provide Dockerfiles for local test development.*
    
    
    ## Brief change log
    
      - *Implement Jepsen tests.*
    
    
    ## Verifying this change
    
    This change added tests and can be verified as follows:
    
      - *The changes themselves are tests.*
      - *Run Jepsen tests in docker containers.*
      - *Run unit tests with `lein test`*
    
    ## Does this pull request potentially affect one of the following parts:
    
      - Dependencies (does it add or upgrade a dependency): (yes / **no** (at least not to
Flink))
      - The public API, i.e., is any changed class annotated with `@Public(Evolving)`: (yes
/ **no**)
      - The serializers: (yes / **no** / don't know)
      - The runtime per-record code paths (performance sensitive): (yes / **no** / don't know)
      - Anything that affects deployment or recovery: JobManager (and its components), Checkpointing,
Yarn/Mesos, ZooKeeper: (yes / **no** (but it will as soon as test failures appear) / don't
know)
      - The S3 file system connector: (yes / **no** / don't know)
    
    ## Documentation
    
      - Does this pull request introduce a new feature? (yes / **no**)
      - If yes, how is the feature documented? (**not applicable** / docs / JavaDocs / not
documented)
    
    cc: @tillrohrmann @cewood


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

    $ git pull https://github.com/GJL/flink FLINK-9004

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

    https://github.com/apache/flink/pull/6239.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 #6239
    
----
commit 063e4621a5982b55ee7f7b0935290bbc717a5a45
Author: gyao <gary@...>
Date:   2018-03-05T21:23:33Z

    [FLINK-9004][tests] Implement Jepsen tests to test job availability.
    
    Use the Jepsen framework (https://github.com/jepsen-io/jepsen) to implement
    tests that verify Flink's HA capabilities under real-world faults, such as
    sudden TaskManager/JobManager termination, HDFS NameNode unavailability, network
    partitions, etc. The Flink cluster under test is automatically deployed on YARN
    (session & job mode) and Mesos.
    
    Provide Dockerfiles for local test development.

----


---

Mime
View raw message