[
https://issues.apache.org/jira/browse/HIVE-24068?focusedWorklogId=474081&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-474081
]
ASF GitHub Bot logged work on HIVE-24068:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 24/Aug/20 23:23
Start Date: 24/Aug/20 23:23
Worklog Time Spent: 10m
Work Description: prasanthj opened a new pull request #1428:
URL: https://github.com/apache/hive/pull/1428
### What changes were proposed in this pull request?
DAG submission failure can also happen in environments where AM container
died causing DNS issues. DAG submissions are safe to retry as the DAG hasn't
started execution yet. There are retries at getSession and submitDAG level
individually but some submitDAG failure has to retry getSession as well as AM
could be unreachable, this can be handled in re-execution plugin. This PR adds
a new re-execution plugin for intermittent DAG submission failures.
### Why are the changes needed?
To make hive resilient to environments with network/DNS issues.
### Does this PR introduce _any_ user-facing change?
Yes. Adds the re-exec plugin as default option.
### How was this patch tested?
Manually. Tez code was changed to explicitly throw UnknownHostException to
simulate DNS/network issue and tested to make sure retry happens.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 474081)
Remaining Estimate: 0h
Time Spent: 10m
> Add re-execution plugin for handling DAG submission failures
> ------------------------------------------------------------
>
> Key: HIVE-24068
> URL: https://issues.apache.org/jira/browse/HIVE-24068
> Project: Hive
> Issue Type: Bug
> Affects Versions: 4.0.0
> Reporter: Prasanth Jayachandran
> Assignee: Prasanth Jayachandran
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> DAG submission failure can also happen in environments where AM container
> died causing DNS issues. DAG submissions are safe to retry as the DAG hasn't
> started execution yet. There are retries at getSession and submitDAG level
> individually but some submitDAG failure has to retry getSession as well as AM
> could be unreachable, this can be handled in re-execution plugin.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
