[jira] [Commented] (FLINK-1984) Integrate Flink with Apache Mesos

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

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

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

Github user ankurcha commented on the pull request:

    https://github.com/apache/flink/pull/948#issuecomment-138417721
  
    @rmetzger This PR should be good to test. I have embedded a simple http server that can serve the `log4j.configuration=...` file or the a default file to the task managers. I recommend using `mvn -P include-mesos clean package` in flink dist followed by something similar to:
    
    ```bash
    java -Dlog4j.configuration=/Users/achauhan/Projects/flink/flink-dist/target/flink-0.10-SNAPSHOT-bin/flink-0.10-SNAPSHOT/conf/log4j.properties -cp flink-dist-0.10-SNAPSHOT.jar org.apache.flink.mesos.scheduler.FlinkScheduler --confDir /Users/achauhan/Projects/flink/flink-dist/target/flink-0.10-SNAPSHOT-bin/flink-0.10-SNAPSHOT/conf
    ```
    
    to start the job manager. The `--confDir` path must contain correct configuration etc. Please let me know if you face any problems. I have tried it using [playa-mesos](https://github.com/mesosphere/playa-mesos).


> Integrate Flink with Apache Mesos
> ---------------------------------
>
>                 Key: FLINK-1984
>                 URL: https://issues.apache.org/jira/browse/FLINK-1984
>             Project: Flink
>          Issue Type: New Feature
>          Components: New Components
>            Reporter: Robert Metzger
>            Priority: Minor
>         Attachments: 251.patch
>
>
> There are some users asking for an integration of Flink into Mesos.
> There also is a pending pull request for adding Mesos support for Flink: https://github.com/apache/flink/pull/251
> But the PR is insufficiently tested. I'll add the code of the pull request to this JIRA in case somebody wants to pick it up in the future.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)