hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jing Zhao (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-12421) Add jitter to RetryInvocationHandler
Date Mon, 04 Apr 2016 20:21:25 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-12421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15224972#comment-15224972

Jing Zhao commented on HADOOP-12421:

Thanks for working on this, [~eclark]. One quick question is currently the client's retry
policy, {{FailoverOnNetworkExceptionRetry}}, already includes randomness in {{calculateExponentialTime}}.
Do you know why this cannot avoid the spike and why an extra jitter can help here?

> Add jitter to RetryInvocationHandler
> ------------------------------------
>                 Key: HADOOP-12421
>                 URL: https://issues.apache.org/jira/browse/HADOOP-12421
>             Project: Hadoop Common
>          Issue Type: Bug
>    Affects Versions: 2.8.0
>            Reporter: Elliott Clark
>            Assignee: Elliott Clark
>         Attachments: HADOOP-12421-v1.patch, HADOOP-12421-v2.patch, HADOOP-12421-v3.patch,
HADOOP-12421-v4.patch, HADOOP-12421-v5.patch
> Calls to NN can become synchronized across a cluster during NN failover. This leads to
a spike in requests until things recover. Making an already tricky time worse.

This message was sent by Atlassian JIRA

View raw message