Return-Path: X-Original-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 5B9D718BD9 for ; Thu, 4 Jun 2015 20:42:41 +0000 (UTC) Received: (qmail 37963 invoked by uid 500); 4 Jun 2015 20:42:41 -0000 Delivered-To: apmail-hadoop-common-issues-archive@hadoop.apache.org Received: (qmail 37915 invoked by uid 500); 4 Jun 2015 20:42:41 -0000 Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-issues@hadoop.apache.org Delivered-To: mailing list common-issues@hadoop.apache.org Received: (qmail 37903 invoked by uid 99); 4 Jun 2015 20:42:41 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 04 Jun 2015 20:42:41 +0000 Date: Thu, 4 Jun 2015 20:42:41 +0000 (UTC) From: "Hadoop QA (JIRA)" To: common-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HADOOP-12054) RPC client should not retry for InvalidToken exceptions MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HADOOP-12054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14573541#comment-14573541 ] Hadoop QA commented on HADOOP-12054: ------------------------------------ \\ \\ | (/) *{color:green}+1 overall{color}* | \\ \\ || Vote || Subsystem || Runtime || Comment || | {color:blue}0{color} | pre-patch | 16m 20s | Pre-patch trunk compilation is healthy. | | {color:green}+1{color} | @author | 0m 0s | The patch does not contain any @author tags. | | {color:green}+1{color} | tests included | 0m 0s | The patch appears to include 1 new or modified test files. | | {color:green}+1{color} | javac | 7m 28s | There were no new javac warning messages. | | {color:green}+1{color} | javadoc | 9m 36s | There were no new javadoc warning messages. | | {color:green}+1{color} | release audit | 0m 23s | The applied patch does not increase the total number of release audit warnings. | | {color:green}+1{color} | checkstyle | 1m 4s | There were no new checkstyle issues. | | {color:green}+1{color} | whitespace | 0m 1s | The patch has no lines that end in whitespace. | | {color:green}+1{color} | install | 1m 33s | mvn install still works. | | {color:green}+1{color} | eclipse:eclipse | 0m 31s | The patch built with eclipse:eclipse. | | {color:green}+1{color} | findbugs | 1m 50s | The patch does not introduce any new Findbugs (version 3.0.0) warnings. | | {color:green}+1{color} | common tests | 23m 19s | Tests passed in hadoop-common. | | | | 62m 8s | | \\ \\ || Subsystem || Report/Notes || | Patch URL | http://issues.apache.org/jira/secure/attachment/12737667/HADOOP-12054.02.patch | | Optional Tests | javadoc javac unit findbugs checkstyle | | git revision | trunk / 9f6d678 | | hadoop-common test log | https://builds.apache.org/job/PreCommit-HADOOP-Build/6924/artifact/patchprocess/testrun_hadoop-common.txt | | Test Results | https://builds.apache.org/job/PreCommit-HADOOP-Build/6924/testReport/ | | Java | 1.7.0_55 | | uname | Linux asf906.gq1.ygridcore.net 3.13.0-36-lowlatency #63-Ubuntu SMP PREEMPT Wed Sep 3 21:56:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux | | Console output | https://builds.apache.org/job/PreCommit-HADOOP-Build/6924/console | This message was automatically generated. > RPC client should not retry for InvalidToken exceptions > ------------------------------------------------------- > > Key: HADOOP-12054 > URL: https://issues.apache.org/jira/browse/HADOOP-12054 > Project: Hadoop Common > Issue Type: Bug > Components: ipc > Affects Versions: 2.4.0 > Reporter: Daryn Sharp > Assignee: Varun Saxena > Priority: Critical > Attachments: HADOOP-12054.01.patch, HADOOP-12054.02.patch > > > An InvalidToken exception is thrown for expired or cancelled tokens. An InvalidToken not wrapped in a RetriableException must be considered fatal by the retry proxies or clients will spam the service with failed connections. Depending on the context, a service may be degraded when spammed with thousands of connection failures. -- This message was sent by Atlassian JIRA (v6.3.4#6332)