You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hive.apache.org by "Prasanth Jayachandran (Jira)" <ji...@apache.org> on 2020/08/25 17:01:00 UTC

[jira] [Updated] (HIVE-24068) Add re-execution plugin for handling DAG submission and unmanaged AM failures

     [ https://issues.apache.org/jira/browse/HIVE-24068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Prasanth Jayachandran updated HIVE-24068:
-----------------------------------------
    Summary: Add re-execution plugin for handling DAG submission and unmanaged AM failures  (was: Add re-execution plugin for handling DAG submission failures)

> Add re-execution plugin for handling DAG submission and unmanaged AM 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
>              Labels: pull-request-available
>          Time Spent: 20m
>  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)