hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (Jira)" <>
Subject [jira] [Work logged] (HIVE-24068) Add re-execution plugin for handling DAG submission and unmanaged AM failures
Date Tue, 25 Aug 2020 17:06:00 GMT


ASF GitHub Bot logged work on HIVE-24068:

                Author: ASF GitHub Bot
            Created on: 25/Aug/20 17:05
            Start Date: 25/Aug/20 17:05
    Worklog Time Spent: 10m 
      Work Description: prasanthj commented on pull request #1428:

   @kgyrtkirk thanks for the review! Addressed the review comment. Also handled the maxExecutions
within the plugin which was missing before. Once minor change added is to update AM loss plugin
to handle unmanaged AM failure as well.

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:

Issue Time Tracking

    Worklog Id:     (was: 474399)
    Time Spent: 0.5h  (was: 20m)

> Add re-execution plugin for handling DAG submission and unmanaged AM failures
> -----------------------------------------------------------------------------
>                 Key: HIVE-24068
>                 URL:
>             Project: Hive
>          Issue Type: Bug
>    Affects Versions: 4.0.0
>            Reporter: Prasanth Jayachandran
>            Assignee: Prasanth Jayachandran
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 0.5h
>  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
> There is already AM loss retry execution plugin but it only handles managed AMs. It can
be extended to handle unmanaged AMs as well.

This message was sent by Atlassian Jira

View raw message