Affects Version/s: 0.23.0
Fix Version/s: 0.23.2
The job history UI and MRClientProtocol calls routed via JobHistory are very slow for large jobs. Some of this time is spent parsing the history file. A good chunk is spent pre-creating lots of objects which may never be used. Those can be create when required - bringing down the load times of job history pages and getJobReport etc calls to approximately the history file parse time.
|Status||Patch Available [ 10002 ]||Resolved [ 5 ]|
|Hadoop Flags||Reviewed [ 10343 ]|
|Release Note||Modified JobHistory records in YARN to lazily load job and task reports so as to improve UI response times.|
|Fix Version/s||0.23.2 [ 12319851 ]|
|Resolution||Fixed [ 1 ]|