hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (JIRA)" <>
Subject [jira] [Commented] (HIVE-19708) Repl copy retrying with cm path even if the failure is due to network issue
Date Fri, 01 Jun 2018 05:25:00 GMT


Hive QA commented on HIVE-19708:

Here are the results of testing the latest attachment:

{color:red}ERROR:{color} -1 due to build exiting with an error

Test results:
Console output:
Test logs:

Executing org.apache.hive.ptest.execution.TestCheckPhase
Tests exited with: Exception: Patch URL
was found in seen patch url's cache and a test was probably run already on it. Aborting...

This message is automatically generated.

ATTACHMENT ID: 12925845 - PreCommit-HIVE-Build

> 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
>         Attachments: HIVE-19708.01.patch, HIVE-19708.02.patch, HIVE-19708.04.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

View raw message