[jira] [Updated] (YARN-8224) LogAggregation status TIME_OUT for absent container misleading

2018-04-27 Thread Prabhu Joseph (JIRA) 

 [ 
https://issues.apache.org/jira/browse/YARN-8224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Prabhu Joseph updated YARN-8224:

Description: 
When a container is not launched on NM and it is absent, RM still tries to get 
the Log Aggregation Status and reports the status as TIME_OUT in RM UI. 

{code}
2018-04-26 12:47:38,403 WARN  containermanager.ContainerManagerImpl 
(ContainerManagerImpl.java:handle(1070)) - Event EventType: KILL_CONTAINER sent 
to absent container container_e361_1524687599273_2110_01_000770

2018-04-26 12:49:31,743 WARN  containermanager.ContainerManagerImpl 
(ContainerManagerImpl.java:handle(1086)) - Event EventType: FINISH_APPLICATION 
sent to absent application application_1524687599273_2110

{code}




  was:
When a container is not launched on NM and it is absent, RM still tries to get 
the Log Aggregation Status and reports the status as TIME_OUT. 

{code}
2018-04-26 12:47:38,403 WARN  containermanager.ContainerManagerImpl 
(ContainerManagerImpl.java:handle(1070)) - Event EventType: KILL_CONTAINER sent 
to absent container container_e361_1524687599273_2110_01_000770

2018-04-26 12:49:31,743 WARN  containermanager.ContainerManagerImpl 
(ContainerManagerImpl.java:handle(1086)) - Event EventType: FINISH_APPLICATION 
sent to absent application application_1524687599273_2110

{code}





> LogAggregation status TIME_OUT for absent container misleading
> --
>
> Key: YARN-8224
> URL: https://issues.apache.org/jira/browse/YARN-8224
> Project: Hadoop YARN
>  Issue Type: Bug
>  Components: log-aggregation
>Affects Versions: 2.7.3
>Reporter: Prabhu Joseph
>Priority: Major
>
> When a container is not launched on NM and it is absent, RM still tries to 
> get the Log Aggregation Status and reports the status as TIME_OUT in RM UI. 
> {code}
> 2018-04-26 12:47:38,403 WARN  containermanager.ContainerManagerImpl 
> (ContainerManagerImpl.java:handle(1070)) - Event EventType: KILL_CONTAINER 
> sent to absent container container_e361_1524687599273_2110_01_000770
> 2018-04-26 12:49:31,743 WARN  containermanager.ContainerManagerImpl 
> (ContainerManagerImpl.java:handle(1086)) - Event EventType: 
> FINISH_APPLICATION sent to absent application application_1524687599273_2110
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org

[jira] [Updated] (YARN-8224) LogAggregation status TIME_OUT for absent container misleading

2018-04-27 Thread Prabhu Joseph (JIRA) 

 [ 
https://issues.apache.org/jira/browse/YARN-8224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Prabhu Joseph updated YARN-8224:

Description: 
When a container is not launched on NM and it is absent, RM still tries to get 
the Log Aggregation Status and reports the status as TIME_OUT. 

{code}
2018-04-26 12:47:38,403 WARN  containermanager.ContainerManagerImpl 
(ContainerManagerImpl.java:handle(1070)) - Event EventType: KILL_CONTAINER sent 
to absent container container_e361_1524687599273_2110_01_000770

2018-04-26 12:49:31,743 WARN  containermanager.ContainerManagerImpl 
(ContainerManagerImpl.java:handle(1086)) - Event EventType: FINISH_APPLICATION 
sent to absent application application_1524687599273_2110

{code}




  was:
When a container is not launched on NM and it is absent, RM still tries to get 
the Log Aggregation Status and reports the status as TIME_OUT. (attached 
screenshot)

{code}
2018-04-26 12:47:38,403 WARN  containermanager.ContainerManagerImpl 
(ContainerManagerImpl.java:handle(1070)) - Event EventType: KILL_CONTAINER sent 
to absent container container_e361_1524687599273_2110_01_000770

2018-04-26 12:49:31,743 WARN  containermanager.ContainerManagerImpl 
(ContainerManagerImpl.java:handle(1086)) - Event EventType: FINISH_APPLICATION 
sent to absent application application_1524687599273_2110

{code}





> LogAggregation status TIME_OUT for absent container misleading
> --
>
> Key: YARN-8224
> URL: https://issues.apache.org/jira/browse/YARN-8224
> Project: Hadoop YARN
>  Issue Type: Bug
>  Components: log-aggregation
>Affects Versions: 2.7.3
>Reporter: Prabhu Joseph
>Priority: Major
>
> When a container is not launched on NM and it is absent, RM still tries to 
> get the Log Aggregation Status and reports the status as TIME_OUT. 
> {code}
> 2018-04-26 12:47:38,403 WARN  containermanager.ContainerManagerImpl 
> (ContainerManagerImpl.java:handle(1070)) - Event EventType: KILL_CONTAINER 
> sent to absent container container_e361_1524687599273_2110_01_000770
> 2018-04-26 12:49:31,743 WARN  containermanager.ContainerManagerImpl 
> (ContainerManagerImpl.java:handle(1086)) - Event EventType: 
> FINISH_APPLICATION sent to absent application application_1524687599273_2110
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org