Funny you should say that, because in a recent discussion with Stephan and
Jamie, we talked about reworking the web UI to talk to numerous job managers.
I’ve been looking into is as part of the Mesos work (FLINK-1984). I’ll start a
new thread about it soon.
> On May 11, 2016, at 10:38 PM, Al
That would be definitely awesome (and useful also for us)! +1
On Thu, May 12, 2016 at 7:38 AM, Aljoscha Krettek
wrote:
> I favor the one-cluster-per job approach. If this becomes the dominant
> approach to doing things we could also think about introducing a separate
> component that would allo
I favor the one-cluster-per job approach. If this becomes the dominant
approach to doing things we could also think about introducing a separate
component that would allow monitoring the jobs in these per-job clusters as
is now possible when running multiple jobs in a single cluster.
On Thu, 12 Ma
One option is to use a separate cluster (JobManager + TaskManagers) for each
job. This is fairly straightforward with the YARN support - "flink run” can
launch a cluster for a job and tear it down afterwards.
Of course this means you must deploy YARN. That doesn’t necessarily imply
HDFS tho
