You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by GitBox <gi...@apache.org> on 2018/08/05 13:02:57 UTC

[GitHub] GJL opened a new pull request #6496: [FLINK-10063][tests] Use runit to supervise mesos processes.

GJL opened a new pull request #6496: [FLINK-10063][tests] Use runit to supervise mesos processes.
URL: https://github.com/apache/flink/pull/6496
 
 
   ## What is the purpose of the change
   
   *Use a process supervisor to automatically restart Mesos processes. This is needed because Mesos uses a "fail-fast" approach to error handling, e.g., the Mesos master will exit when it discovers it has been partitioned away from the Zookeeper quorum. Currently the some of the tests cannot pass because the Mesos processes exiting.*
   
   cc: @igalshilman @cewood @tillrohrmann 
   
   ## Brief change log
   
     - *Use runit to supervise Mesos processes.*
     - *Make docker setup work.*
   
   
   ## Verifying this change
   
   This change added tests and can be verified as follows:
   
     - *Ran Mesos tests on docker.*
     
   ## Does this pull request potentially affect one of the following parts:
   
     - Dependencies (does it add or upgrade a dependency): (**yes** (in test code) / no)
     - 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** / 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)
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services