[
https://issues.apache.org/jira/browse/HIVE-19708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16492284#comment-16492284
]
ASF GitHub Bot commented on HIVE-19708:
---------------------------------------
GitHub user maheshk114 opened a pull request:
https://github.com/apache/hive/pull/359
HIVE-19708 : Repl copy retrying with cm path even if the failure is d…
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/maheshk114/hive BUG-102280
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/hive/pull/359.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #359
----
commit fc7377c8f265402f2bdc19ef79f0cf94b4fa5c44
Author: Mahesh Kumar Behera <mbehera@...>
Date: 2018-05-25T03:43:52Z
HIVE-19708 : Repl copy retrying with cm path even if the failure is due to
network issue
----
> 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: 3.1.0
>
> Attachments: HIVE-19708.01.patch, HIVE-19708.02.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)
