You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Rohith Sharma K S (JIRA)" <ji...@apache.org> on 2018/07/10 11:05:00 UTC
[jira] [Created] (YARN-8512) ATSv2 entities are not published to
HBase
Rohith Sharma K S created YARN-8512:
---------------------------------------
Summary: ATSv2 entities are not published to HBase
Key: YARN-8512
URL: https://issues.apache.org/jira/browse/YARN-8512
Project: Hadoop YARN
Issue Type: Bug
Reporter: Yesha Vora
Assignee: Rohith Sharma K S
It is observed that if 1st attempt master container is died and 2nd attempt master container is launched in a NM where old containers are running but not master container.
||Attempt||NM1||NM2||Action||
|attempt-1|master container i.e container-1-1|container-1-2|master container died|
|attempt-2|NA|container-1-2 and master container container-2-1|NA|
In the above scenario, NM doesn't identifies flowContext and will get log below
{noformat}
2018-07-10 00:44:38,285 WARN storage.HBaseTimelineWriterImpl (HBaseTimelineWriterImpl.java:write(170)) - Found null for one of: flowName=null appId=application_1531175172425_0001 userId=hbase clusterId=yarn-cluster . Not proceeding with writing to hbase
2018-07-10 00:44:38,560 WARN storage.HBaseTimelineWriterImpl (HBaseTimelineWriterImpl.java:write(170)) - Found null for one of: flowName=null appId=application_1531175172425_0001 userId=hbase clusterId=yarn-cluster . Not proceeding with writing to hbase
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org