[HIVE-10959] webhcat launcher job should reconnect to the running child job on task retry

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.15.0
• Fix Version/s: 1.2.1
• Component/s: WebHCat
• Assignee: Ivan Mitic
• Reporter: Ivan Mitic
• Created: 08/Jun/15 05:41
• Updated: 11/Jun/15 16:05
• Resolved: 11/Jun/15 07:15

Description

Currently, Templeton launcher kills all child jobs (jobs tagged with the parent job's id) upon task retry.

Upon templeton launcher task retry, templeton should reconnect to the running job and continue tracking its progress that way.

This logic cannot be used for all job kinds (e.g. for jobs that are driven by the client side like regular hive). However, for MapReduceV2, and possibly Tez and HiveOnTez, this should be the default.

Issue Links

• is related to: HIVE-7190 WebHCat launcher task failure can cause two concurent user jobs to run