In addition to that, you need to change property *yarn*.*nodemanager*. resource.*memory*-mb in yarn-site.xmk to make NM recognize memory usage. On May 22, 2014 7:50 PM, "ch huang" <[EMAIL PROTECTED]> wrote:
Not "in addition to that". You should only use the memory-mb configuration. Giving 15GB to NodeManger itself will eat into the total memory available for containers.
On May 22, 2014, at 8:25 PM, Tsuyoshi OZAWA <[EMAIL PROTECTED]> wrote:
CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You.
Thanks, Tsuyoshi On May 22, 2014 9:26 PM, "Vinod Kumar Vavilapalli" <[EMAIL PROTECTED]> wrote:
NEW: Monitor These Apps!
Apache Lucene, Apache Solr and all other Apache Software Foundation projects and their respective logos are trademarks of the Apache Software Foundation.
Elasticsearch, Kibana, Logstash, and Beats are trademarks of Elasticsearch BV, registered in the U.S. and in other countries. This site and Sematext Group is in no way affiliated with Elasticsearch BV.
Service operated by Sematext