History Server API’s.¶
-
class
yarn_api_client.history_server.
HistoryServer
(address=None, port=19888, timeout=30)¶ The history server REST API’s allow the user to get status on finished applications. Currently it only supports MapReduce and provides information on finished jobs.
-
application_information
()¶ The history server information resource provides overall information about the history server.
-
job
(job_id)¶ A Job resource contains information about a particular job identified by jobid.
-
job_attempts
(job_id)¶ With the job attempts API, you can obtain a collection of resources that represent a job attempt.
-
job_conf
(job_id)¶ A job configuration resource contains information about the job configuration for this job.
-
job_counters
(job_id)¶ With the job counters API, you can object a collection of resources that represent al the counters for that job.
-
job_task
(job_id, task_id)¶ A Task resource contains information about a particular task within a job.
-
job_tasks
(job_id, type=None)¶ With the tasks API, you can obtain a collection of resources that represent a task within a job.
-
jobs
(state=None, user=None, queue=None, limit=None, started_time_begin=None, started_time_end=None, finished_time_begin=None, finished_time_end=None)¶ The jobs resource provides a list of the MapReduce jobs that have finished. It does not currently return a full list of parameters.
-
task_attempt
(job_id, task_id, attempt_id)¶ A Task Attempt resource contains information about a particular task attempt within a job.
-
task_attempt_counters
(job_id, task_id, attempt_id)¶ With the task attempt counters API, you can object a collection of resources that represent al the counters for that task attempt.
-
task_attempts
(job_id, task_id)¶ With the task attempts API, you can obtain a collection of resources that represent a task attempt within a job.
-
task_counters
(job_id, task_id)¶ With the task counters API, you can object a collection of resources that represent all the counters for that task.
-