You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@flink.apache.org by Elias Levy <fe...@gmail.com> on 2017/09/24 00:48:40 UTC
History Server
I am curious, why is the History Server a separate process and Web UI
instead of being part of the Web Dashboard within the Job Manager?
Re: History Server
Posted by Chesnay Schepler <ch...@apache.org>.
The HS isn't aware of running jobs at all, so yes users would have to
switch once the job is done.
On 17.01.2018 00:45, Eron Wright wrote:
> As a follow-up question, how well does the history server work for
> observing a running job? I'm trying to understand whether, in the
> cluster-per-job model, a user would be expected to hop from the Web UI
> to the History Server once the job completed.
>
> Thanks
>
> On Wed, Oct 4, 2017 at 3:49 AM, Stephan Ewen <sewen@apache.org
> <ma...@apache.org>> wrote:
>
> To add to this:
>
> The History Server is mainly useful in cases where one runs a
> Flink-cluster-per-job. One the job finished, the processes
> disappear. The History Server should be longer lived to make past
> executions' stats available.
>
> On Mon, Sep 25, 2017 at 3:44 PM, Nico Kruber
> <nico@data-artisans.com <ma...@data-artisans.com>> wrote:
>
> Hi Elias,
> in theory, it could be integrated into a single web interface,
> but this was
> not done so far.
> I guess the main reason for keeping it separate was probably
> to have a better
> separation of concerns as the history server is actually
> independent of the
> current JobManager execution and merely displays previous job
> results which
> may also come from different or previously existing JobManager
> instances which
> stored history data in its storage directory.
>
> Chesnay (cc'd) may elaborate a bit more in case you'd like to
> change that and
> integrate the history server (interface) into the JobManager.
>
>
> Nico
>
> On Sunday, 24 September 2017 02:48:40 CEST Elias Levy wrote:
> > I am curious, why is the History Server a separate process
> and Web UI
> > instead of being part of the Web Dashboard within the Job
> Manager?
>
>
>
>
Re: History Server
Posted by Eron Wright <er...@gmail.com>.
As a follow-up question, how well does the history server work for
observing a running job? I'm trying to understand whether, in the
cluster-per-job model, a user would be expected to hop from the Web UI to
the History Server once the job completed.
Thanks
On Wed, Oct 4, 2017 at 3:49 AM, Stephan Ewen <se...@apache.org> wrote:
> To add to this:
>
> The History Server is mainly useful in cases where one runs a
> Flink-cluster-per-job. One the job finished, the processes disappear. The
> History Server should be longer lived to make past executions' stats
> available.
>
> On Mon, Sep 25, 2017 at 3:44 PM, Nico Kruber <ni...@data-artisans.com>
> wrote:
>
>> Hi Elias,
>> in theory, it could be integrated into a single web interface, but this
>> was
>> not done so far.
>> I guess the main reason for keeping it separate was probably to have a
>> better
>> separation of concerns as the history server is actually independent of
>> the
>> current JobManager execution and merely displays previous job results
>> which
>> may also come from different or previously existing JobManager instances
>> which
>> stored history data in its storage directory.
>>
>> Chesnay (cc'd) may elaborate a bit more in case you'd like to change that
>> and
>> integrate the history server (interface) into the JobManager.
>>
>>
>> Nico
>>
>> On Sunday, 24 September 2017 02:48:40 CEST Elias Levy wrote:
>> > I am curious, why is the History Server a separate process and Web UI
>> > instead of being part of the Web Dashboard within the Job Manager?
>>
>>
>>
>
Re: History Server
Posted by Stephan Ewen <se...@apache.org>.
To add to this:
The History Server is mainly useful in cases where one runs a
Flink-cluster-per-job. One the job finished, the processes disappear. The
History Server should be longer lived to make past executions' stats
available.
On Mon, Sep 25, 2017 at 3:44 PM, Nico Kruber <ni...@data-artisans.com> wrote:
> Hi Elias,
> in theory, it could be integrated into a single web interface, but this was
> not done so far.
> I guess the main reason for keeping it separate was probably to have a
> better
> separation of concerns as the history server is actually independent of the
> current JobManager execution and merely displays previous job results which
> may also come from different or previously existing JobManager instances
> which
> stored history data in its storage directory.
>
> Chesnay (cc'd) may elaborate a bit more in case you'd like to change that
> and
> integrate the history server (interface) into the JobManager.
>
>
> Nico
>
> On Sunday, 24 September 2017 02:48:40 CEST Elias Levy wrote:
> > I am curious, why is the History Server a separate process and Web UI
> > instead of being part of the Web Dashboard within the Job Manager?
>
>
>
Re: History Server
Posted by Nico Kruber <ni...@data-artisans.com>.
Hi Elias,
in theory, it could be integrated into a single web interface, but this was
not done so far.
I guess the main reason for keeping it separate was probably to have a better
separation of concerns as the history server is actually independent of the
current JobManager execution and merely displays previous job results which
may also come from different or previously existing JobManager instances which
stored history data in its storage directory.
Chesnay (cc'd) may elaborate a bit more in case you'd like to change that and
integrate the history server (interface) into the JobManager.
Nico
On Sunday, 24 September 2017 02:48:40 CEST Elias Levy wrote:
> I am curious, why is the History Server a separate process and Web UI
> instead of being part of the Web Dashboard within the Job Manager?