Skip to main content

No project description provided

Project description

README

## Bookmarks

YARN logs

In YARN terminology, executors and application masters run inside “containers”.

If log aggregation is turned on (with the yarn.log-aggregation-enable config), container logs are copied to HDFS and deleted on the local machine.

These logs can be viewed from anywhere on the cluster with the yarn logs command.

yarn logs -applicationId <app ID>

note:

The only thing you need to follow to get correctly working history server for Spark is to close your Spark context in your application. Otherwise, application history server does not see you as COMPLETE and does not show anything (despite history UI is accessible but not so visible).

On HDFS they are located can be found by looking at your YARN configs yarn.nodemanager.remote-app-log-dir and yarn.nodemanager.remote-app-log-dir-suffix

Helpfull question on [cloudera support question]https://community.cloudera.com/t5/Support-Questions/Yarn-log-history/m-p/164682/highlight/true#M127049

Yarn typically stores history of all the application in

  • Mapreduce History server (only for Mapreduce jobs)
  • Application Timeline Server ( all type of yarn applications).
<property>
  <name>yarn.timeline-service.enabled</name>
  <value>true</value>
</property>
<property>
<name>yarn.timeline-service.webapp.address</name>
<value>host1:8188</value>
</property>

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

khadoop-0.1.0.tar.gz (2.5 kB view hashes)

Uploaded Source

Built Distribution

khadoop-0.1.0-py3-none-any.whl (2.7 kB view hashes)

Uploaded Python 3

Supported by

AWS AWS Cloud computing and Security Sponsor Datadog Datadog Monitoring Fastly Fastly CDN Google Google Download Analytics Microsoft Microsoft PSF Sponsor Pingdom Pingdom Monitoring Sentry Sentry Error logging StatusPage StatusPage Status page