Re: unsubscribe

2023-01-30 Thread Destin Ashwin
unsubscribe

On Mon, 30 Jan, 2023, 4:58 pm Lake Chang,  wrote:

> unsubscribe
>


Re: Hadoop 2.6 Timeline/history server: Killed/Complete Containers

2016-12-02 Thread Destin Ashwin
unsubscribe.

On Fri, Dec 2, 2016 at 8:17 PM, AJAY GUPTA <ajaygit...@gmail.com> wrote:

> I have Hadoop 2.6 setup on my laptop and my workplace too has a Hadoop 2.6
> cluster. I have started the timeline server on both locations. I am seeing
> different behaviour on both these setups.
>
> *Application:* I am writing a rest API to fetch all killed containers for
> an application
>
> *On company cluster:* Assume I have started an application, assume one of
> the containers gets killed for this application. I am trying to fetch
> information for this killed container using historyClient (while the
> application is running). However this information is not available with
> historyServer. This information is available with history server only after
> application gets killed. The entire application's information is sent to
> history server only after the application is getting killed.
>
> *On local laptop setup:* The killed container information is available at
> history server even when the application is running.
>
> Am I missing some configuration setting on the company cluster which is
> causing this different behaviour?
>



-- 
Thanks,
Destin Ashwin
Cell: +91 914.573.4711
Email: destinash...@gmail.com


Re: yarnClient.getContainerReport exception for KILLED containers

2016-12-01 Thread Destin Ashwin
unsubscribe me please.

On 30-Nov-2016 8:23 pm, "AJAY GUPTA"  wrote:

> Hi
>
> I am running Hadoop 2.6.0 on a cluster setup. I have setup the timeline
> server on this cluster.
> My code wants to fetch details of KILLED containers for an application. I
> have used the yarnClient.getContainerReport() call to get
> details of containers. This call throws an exception for KILLED containers,
> despite timeline server being up.
> Is there some configuration I am missing here which is resulting in this
> issue or is this expected in hadoop 2.6.0?
>
> I have a local setup with Hadoop 2.7.2. It is able to give details of
> KILLED containers without any exception.
>
> Thanks,
> Ajay
>