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-19708) Repl copy retrying with cm path even if the failure is due to network issue
Date Tue, 16 Jun 2020 16:56:01 GMT


ASF GitHub Bot logged work on HIVE-19708:

                Author: ASF GitHub Bot
            Created on: 16/Jun/20 16:55
            Start Date: 16/Jun/20 16:55
    Worklog Time Spent: 10m 
      Work Description: github-actions[bot] commented on pull request #359:

   This pull request has been automatically marked as stale because it has not had recent
activity. It will be closed if no further activity occurs.
   Feel free to reach out on the list if the patch is in need of reviews.

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: 446706)
    Remaining Estimate: 0h
            Time Spent: 10m

> Repl copy retrying with cm path even if the failure is due to network issue
> ---------------------------------------------------------------------------
>                 Key: HIVE-19708
>                 URL:
>             Project: Hive
>          Issue Type: Task
>          Components: Hive, HiveServer2, repl
>    Affects Versions: 3.1.0
>            Reporter: mahesh kumar behera
>            Assignee: mahesh kumar behera
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 3.1.0, 4.0.0
>         Attachments: HIVE-19708.01.patch, HIVE-19708.02.patch, HIVE-19708.04.patch, HIVE-19708.05.patch,
HIVE-19708.06-branch-3.patch, HIVE-19708.06.patch, HIVE-19708.07-branch-3.patch
>          Time Spent: 10m
>  Remaining Estimate: 0h
> * During repl load
>  ** for filesystem based copying of file if the copy fails due to a connection error
to source Name Node, we should recreate the filesystem object.
>  ** the retry logic for local file copy should be triggered using the original source
file path ( and not the CM root path ) since failure can be due to network issues between
DFSClient and NN.
>  * When listing files in tables / partition to include them in _files, we should add
retry logic when failure occurs. FileSystem object here also should be recreated since the
existing one might be in inconsistent state.

This message was sent by Atlassian Jira

View raw message