hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lukas Majercak (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-14134) Idempotent operations throwing RemoteException should not be retried by the client
Date Fri, 07 Dec 2018 20:03:00 GMT

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

Lukas Majercak updated HDFS-14134:
----------------------------------
    Description: 
Currently, some operations that throw IOException on the NameNode are evaluated by RetryPolicy
as FAILOVER_AND_RETRY, but they should just fail fast.

For example, when calling getXAttr("user.some_attr", file") where the file does not have the
attribute, NN throws an IOException with message "could not find attr". The current client
retry policy determines the action for that to be FAILOVER_AND_RETRY. The client then fails
over and retries until it reaches the maximum number of retries. Supposedly, the client should
be able to tell that this exception is normal and fail fast. 

Moreover, even if the action was FAIL, the RetryInvocationHandler looks at all the retry actions
from all requests, and FAILOVER_AND_RETRY takes precedence over FAIL action.

  was:
Currently, some operations that throw IOException on the NameNode are evaluated by RetryPolicy
as FAILOVER_AND_RETRY, but they should just fail fast.

For example, when calling getXAttr("user.some_attr", file") where file does not have the attribute,
NN throws an IOException with message "could not find attr". The current client retry policy
determines the action for that to be FAILOVER_AND_RETRY. The client then fails over and retries
until it reaches the maximum number of retries. Supposedly, the client should be able to tell
that this exception is normal and fail fast. 

Moreover, even if the action was FAIL, the RetryInvocationHandler looks at all the retry actions
from all requests, and FAILOVER_AND_RETRY takes precedence over FAIL action.


> Idempotent operations throwing RemoteException should not be retried by the client
> ----------------------------------------------------------------------------------
>
>                 Key: HDFS-14134
>                 URL: https://issues.apache.org/jira/browse/HDFS-14134
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: hdfs, hdfs-client, ipc
>            Reporter: Lukas Majercak
>            Assignee: Lukas Majercak
>            Priority: Critical
>         Attachments: HDFS-14134.001.patch
>
>
> Currently, some operations that throw IOException on the NameNode are evaluated by RetryPolicy
as FAILOVER_AND_RETRY, but they should just fail fast.
> For example, when calling getXAttr("user.some_attr", file") where the file does not have
the attribute, NN throws an IOException with message "could not find attr". The current client
retry policy determines the action for that to be FAILOVER_AND_RETRY. The client then fails
over and retries until it reaches the maximum number of retries. Supposedly, the client should
be able to tell that this exception is normal and fail fast. 
> Moreover, even if the action was FAIL, the RetryInvocationHandler looks at all the retry
actions from all requests, and FAILOVER_AND_RETRY takes precedence over FAIL action.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org


Mime
View raw message