Fetch container list for failed application attempt

[priyanka gugale <pr...@gmail.com>]

Hi,

I am launching a yarn application. If I kill app master, it tries to
restart application with new attempt id. Now I use yarn command,

yarn container -list <Application Attempt ID>

When I provide the Application Attempt ID of failed attempt, it lists the
container from next attempt which is in "RUNNING" state right now.

Shouldn't this return either list of killed containers from attempt 1 or
empty list? Is this a issue or it's expected behavior?

-Priyanka

Re: Fetch container list for failed application attempt

[priyanka gugale <pr...@apache.org>]

Hi,

Any inputs on this? I have observed this behavior on hadoop v 2.5 and 2.6.
Really appreciate any help on this.

-Priyanka

On Wed, Dec 14, 2016 at 5:02 PM, priyanka gugale <pr...@gmail.com>
wrote:

> Hi,
>
> I am launching a yarn application. If I kill app master, it tries to
> restart application with new attempt id. Now I use yarn command,
>
> yarn container -list <Application Attempt ID>
>
> When I provide the Application Attempt ID of failed attempt, it lists the
> container from next attempt which is in "RUNNING" state right now.
>
> Shouldn't this return either list of killed containers from attempt 1 or
> empty list? Is this a issue or it's expected behavior?
>
> -Priyanka
>

Re: Fetch container list for failed application attempt

[Sunil Govind <su...@gmail.com>]

Hello

IIUC, failed attempt is not removed from attempts list. While querying for
containers of failed attempt, internally resource manager gives u container
from running attempt. Its some what fine as we are transferring few
containers from old attempt if available.

If this behavior is not correct as per your usecase, I suggest you could
raise a JIRA ticket explaining the problem and folks will help in
discussing the same.

Thanks
Sunil

On Wed, Dec 14, 2016 at 5:02 PM priyanka gugale <pr...@gmail.com>
wrote:

> Hi,
>
> I am launching a yarn application. If I kill app master, it tries to
> restart application with new attempt id. Now I use yarn command,
>
> yarn container -list <Application Attempt ID>
>
> When I provide the Application Attempt ID of failed attempt, it lists the
> container from next attempt which is in "RUNNING" state right now.
>
> Shouldn't this return either list of killed containers from attempt 1 or
> empty list? Is this a issue or it's expected behavior?
>
> -Priyanka
>