Steve Loughran commented on HADOOP-13604:

Renamed to make clear it's about auth: the problem is two fold: determining 
that there's an unrecoverable and then rejecting it. The retry handler is meant 
to retry on some things, ConnectionRefused, etc, but k-auth problems are 
unlikely to go away. That said, some network problems (especially DNS) tend not 
to resolve on their own.

w.r.t Auth problems, the fact that UGI tends to generate IOEs rather than 
anything you can filter on is going to have to be fixed first

> Abort retry loop when RPC has an unrecoverable Auth error
> ---------------------------------------------------------
>                 Key: HADOOP-13604
>                 URL: https://issues.apache.org/jira/browse/HADOOP-13604
>             Project: Hadoop Common
>          Issue Type: Improvement
>            Reporter: Henry Robinson
>            Assignee: Xiao Chen
> I've seen an issue where, after an RPC client hit an error obtaining a TGT 
> from Kerberos, the RPC client continues to retry even though there's no 
> chance of success (the no login window is set to 600s).
> In this particular deployment, the client retries 15 times at 15s intervals, 
> leading to a delay of more than three minutes before the failure is bubbled 
> up to the client when the RPC ultimately fails.
> Unrecoverable errors (like failures to login to Kerberos) should lead to fast 
> aborts of the retry loop.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org

Reply via email to