[
https://issues.apache.org/jira/browse/FLINK-1984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14721880#comment-14721880
]
ASF GitHub Bot commented on FLINK-1984:
---------------------------------------
Github user ankurcha commented on the pull request:
https://github.com/apache/flink/pull/948#issuecomment-136236719
@rmetzger I have finally got some time to work on this again. Let me
address your question one by one:
> Why did you decide to start the JobManager alongside the Scheduler?
This is basically a "easy" first step way of getting things running the way
it was done in a whole bunch of projects. The easiest way to run a "single"
master + multiple worker application is to make the scheduler run the master
process and have another meta-framework such as marathon submit the whole
framework as a task to the mesos server. In the lack of marathon or aurora etc,
mesos-submit ( an app that ships with mesos) can be used to submit the
scheduler as a task. This means the job manager + scheduler would be running in
the mesos cluster submitted as an app (just like in YARN).
My eventual goal is to make the scheduler support a completely standalone
mode of operation but that requires coordination in order to assure that only
one scheduler instance exists at a time - this may have some hooks that can be
a part of the HA job manager initiative.
> Tests
I am working on some docker and vagrant based scripts that can make the
"setup" part of the tests more palatable.
> 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)
