I'm not aware of any plans to change this. It would be possible though, to
add a mode where a standalone cluster only accepts a single job.
On Fri, 1 Jul 2016 at 04:50 Jark Wu wrote:
> As standalone mode has the disadvantage that the TaskManager JVM can’t
> isolate different jobs. Does we have a
As standalone mode has the disadvantage that the TaskManager JVM can’t isolate
different jobs. Does we have any plan to improve this ?
- Jark Wu
> 在 2016年6月30日，下午4:19，Kevin Jacobs 写道：
>
> In my opinion the streaming process can be perfectly simulated on a single
> node. You can setup a mess
What I means is standalone mode is not suitable for production enironment. It
is just for testing or prototype.
regardsLongda
--From:Kevin
Jacobs Send Time:2016年6月30日(星期四) 16:20To:dev
; 封仲淹(纪君祥) Subject:Re:
[Discuss] Why differen
In my opinion the streaming process can be perfectly simulated on a
single node. You can setup a message distribution system like Kafka on a
single node, you can run Spark on a single node and the only thing you
need to change when running it on a cluster is that you need to change
the environm
Hi,
no, it is not just for prototyping. Since it is actually the oldest mode of
execution it is also the most stable. You should have no problem using it.
Cheers,
Aljoscha
On Thu, 30 Jun 2016 at 09:54 Longda Feng
wrote:
>
>
> This means Standalone mode is just for prototype.
> But I think we ne
This means Standalone mode is just for prototype.
But I think we need a lightweight solution for streaming process, standalone is
the best solution. Some times, we need setup a flink cluster on a small
cluster. setup a yarn cluster isn't convenient.
(1) in small company, the number of machine
Hi,
yes, you are definitely right that allowing to run multiple user code tasks
in the same TaskManager JVM is not good for stability. This mode is still
there from the very early days of Flink where Yarn was not yet available.
In a production environment I would now recommend to always run one
Fli
