https://community.cloudera.com/t5/Support-Questions/CDH5-4-1-Problem-about-Yarn-NodeManager-chart-metric/m-p/65108#M37553 <P>I found the answer,the problem is a bug.</P><P>apache jira issue:</P><P><A href="https://issues.apache.org/jira/browse/YARN-4408" target="_blank">https://issues.apache.org/jira/browse/YARN-4408</A></P><P>CDH repaire version:</P><P><A href="https://www.cloudera.com/documentation/enterprise/release-notes/topics/cdh_rn_fixed_in_55.html" target="_blank">https://www.cloudera.com/documentation/enterprise/release-notes/topics/cdh_rn_fixed_in_55.html</A></P><P>&nbsp;</P><P>&nbsp;</P><P><SPAN>Yarn for the container management, through the life-cycle approach, we can know the current operating status of each container, after cloudera manager statistical analysis, but also become a chart metric numerical resources. Therefore, we think this is because there is a problem with container life cycle processing.</SPAN></P> Mon, 05 Mar 2018 08:28:53 GMT ISLAND 2018-03-05T08:28:53Z https://community.cloudera.com/t5/Support-Questions/CDH5-4-1-Problem-about-Yarn-NodeManager-chart-metric/m-p/65016#M37552 <P><SPAN>There is a cluster of 15 nodes, several of which Node's chart , the y-axis has a negative case, </SPAN></P><P><SPAN>How dose this happen？&nbsp;&nbsp;is there a solution?</SPAN></P><P><SPAN><span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="allocate container.PNG" style="width: 600px;"><img src="https://community.cloudera.com/t5/image/serverpage/image-id/3907i9650C98215F4CDAA/image-size/large?v=v2&amp;px=999" role="button" title="allocate container.PNG" alt="allocate container.PNG" /></span><span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="allocated Memory.PNG" style="width: 600px;"><img src="https://community.cloudera.com/t5/image/serverpage/image-id/3906iF0C3A3A1A74BA579/image-size/large?v=v2&amp;px=999" role="button" title="allocated Memory.PNG" alt="allocated Memory.PNG" /></span><span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="realtime_container_running.PNG" style="width: 600px;"><img src="https://community.cloudera.com/t5/image/serverpage/image-id/3908iC26EAC402F9451BE/image-size/large?v=v2&amp;px=999" role="button" title="realtime_container_running.PNG" alt="realtime_container_running.PNG" /></span></SPAN></P><P>&nbsp;</P> Thu, 01 Mar 2018 05:22:06 GMT https://community.cloudera.com/t5/Support-Questions/CDH5-4-1-Problem-about-Yarn-NodeManager-chart-metric/m-p/65016#M37552 ISLAND 2018-03-01T05:22:06Z https://community.cloudera.com/t5/Support-Questions/CDH5-4-1-Problem-about-Yarn-NodeManager-chart-metric/m-p/65108#M37553 <P>I found the answer,the problem is a bug.</P><P>apache jira issue:</P><P><A href="https://issues.apache.org/jira/browse/YARN-4408" target="_blank">https://issues.apache.org/jira/browse/YARN-4408</A></P><P>CDH repaire version:</P><P><A href="https://www.cloudera.com/documentation/enterprise/release-notes/topics/cdh_rn_fixed_in_55.html" target="_blank">https://www.cloudera.com/documentation/enterprise/release-notes/topics/cdh_rn_fixed_in_55.html</A></P><P>&nbsp;</P><P>&nbsp;</P><P><SPAN>Yarn for the container management, through the life-cycle approach, we can know the current operating status of each container, after cloudera manager statistical analysis, but also become a chart metric numerical resources. Therefore, we think this is because there is a problem with container life cycle processing.</SPAN></P> Mon, 05 Mar 2018 08:28:53 GMT https://community.cloudera.com/t5/Support-Questions/CDH5-4-1-Problem-about-Yarn-NodeManager-chart-metric/m-p/65108#M37553 ISLAND 2018-03-05T08:28:53Z