hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "mahesh kumar behera (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HIVE-19708) Repl copy retrying with cm path even if the failure is due to network issue
Date Tue, 05 Jun 2018 10:40:00 GMT

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

mahesh kumar behera updated HIVE-19708:
---------------------------------------
    Attachment: HIVE-19708.06-branch-3.patch

> Repl copy retrying with cm path even if the failure is due to network issue
> ---------------------------------------------------------------------------
>
>                 Key: HIVE-19708
>                 URL: https://issues.apache.org/jira/browse/HIVE-19708
>             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: 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
>
>
> * 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
(v7.6.3#76005)

Mime
View raw message