Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Date: Thu, 15 Oct 2015 01:22:05 +0000 (UTC)
From: "Chen He (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: <JIRA.12902736.1444149246000.43786.1444872125075@Atlassian.JIRA>
In-Reply-To: <JIRA.12902736.1444149246000@Atlassian.JIRA>
References: <JIRA.12902736.1444149246000@Atlassian.JIRA>
 <JIRA.12902736.1444149246399@arcas>
Subject: [jira] [Updated] (HADOOP-12461) Swift driver should have the
 ability to renew token if it expired
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Chen He updated HADOOP-12461:
-----------------------------
    Summary: Swift driver should have the ability to renew token if it expired  (was: Swift driver should have the ability to renew token if server has timeout)

> Swift driver should have the ability to renew token if it expired
> -----------------------------------------------------------------
>
>                 Key: HADOOP-12461
>                 URL: https://issues.apache.org/jira/browse/HADOOP-12461
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: fs/swift
>    Affects Versions: 2.7.1
>            Reporter: Chen He
>
> Current swift driver will encounter authentication issue if swift server has token timeout. It will be good if driver can automatically renew once it expired. We met HTTP 401 error when transferring a 100gb file to swift object store. Since the large file is chunked into 27 files, the server will ask each chunk for token inspection. If server has timeout and 100GB file transferring time is longer than this timeout, token will expire and the file transferring will fail. 


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)