Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 66D23200CC1 for ; Mon, 10 Jul 2017 23:11:43 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 65411164447; Mon, 10 Jul 2017 21:11:43 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id ABB5F164443 for ; Mon, 10 Jul 2017 23:11:42 +0200 (CEST) Received: (qmail 62542 invoked by uid 500); 10 Jul 2017 21:11:39 -0000 Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list common-issues@hadoop.apache.org Received: (qmail 62531 invoked by uid 99); 10 Jul 2017 21:11:39 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 10 Jul 2017 21:11:39 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id DF28819448E for ; Mon, 10 Jul 2017 21:11:38 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id wImY6lqEeEl0 for ; Mon, 10 Jul 2017 21:11:38 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 5BDF0626EF for ; Mon, 10 Jul 2017 20:56:06 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id AF21EE0059 for ; Mon, 10 Jul 2017 20:56:04 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 306ED246A0 for ; Mon, 10 Jul 2017 20:56:02 +0000 (UTC) Date: Mon, 10 Jul 2017 20:56:02 +0000 (UTC) From: "Jitendra Nath Pandey (JIRA)" To: common-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (HADOOP-14443) Azure: Support retry and client side failover for authorization, SASKey and delegation token generation MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 10 Jul 2017 21:11:43 -0000 [ https://issues.apache.org/jira/browse/HADOOP-14443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jitendra Nath Pandey updated HADOOP-14443: ------------------------------------------ Status: Open (was: Patch Available) > Azure: Support retry and client side failover for authorization, SASKey and delegation token generation > ------------------------------------------------------------------------------------------------------- > > Key: HADOOP-14443 > URL: https://issues.apache.org/jira/browse/HADOOP-14443 > Project: Hadoop Common > Issue Type: Improvement > Components: fs/azure > Affects Versions: 2.9.0 > Reporter: Santhosh G Nayak > Assignee: Santhosh G Nayak > Fix For: 3.0.0-beta1 > > Attachments: HADOOP-14443.1.patch, HADOOP-14443.2.patch, HADOOP-14443.3.patch, HADOOP-14443.4.patch, HADOOP-14443.5.patch, HADOOP-14443.6.patch, HADOOP-14443.7.patch, HADOOP-14443-branch2-1.patch, HADOOP-14443-branch-2.2.patch, HADOOP-14443-branch2-2.patch > > > Currently, {{WasRemoteCallHelper}} can be configured to talk to only one URL for authorization, SASKey generation and delegation token generation. If for some reason the service is down, all the requests will fail. > So proposal is to, > - Add support to configure multiple URLs, so that if communication to one URL fails, client can retry on another instance of the service running on different node for authorization, SASKey generation and delegation token generation. > - Rename the configurations {{fs.azure.authorization.remote.service.url}} to {{fs.azure.authorization.remote.service.urls}} and {{fs.azure.cred.service.url}} to {{fs.azure.cred.service.urls}} to support the comma separated list of URLs. > - Introduce a new configuration {{fs.azure.delegation.token.service.urls}} to configure the comma separated list of service URLs to get the delegation token. -- This message was sent by Atlassian JIRA (v6.4.14#64029) --------------------------------------------------------------------- To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: common-issues-help@hadoop.apache.org