You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@knox.apache.org by "Phil Zampino (JIRA)" <ji...@apache.org> on 2018/09/19 14:58:00 UTC
[jira] [Updated] (KNOX-1440) WEBHDFS: retry should not be attempted
for datanode write failures
[ https://issues.apache.org/jira/browse/KNOX-1440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Phil Zampino updated KNOX-1440:
-------------------------------
Description:
For WEBHDFS invocations through Knox, if a *datanode* write fails with an IOException, the currently configured HA dispatch (DefaultHADispatch) attempts the write a second time.
HDFS dev says that it would be appropriate to more simply respond with the error, deferring the decision to retry to the client.
This may be resolved as a consequence of KNOX-1439 's resolution, but it may mean that a different dispatch be configured for the datanode interaction.
(FYI: the datanode dispatch is configured in the WEBHDFS service definition)
was:
For WEBHDFS invocations through Knox, if a *datanode* write fails with an IOException, the currently configured HA dispatch (DefaultHADispatch) attempts the write a second time.
HDFS dev says that it would be appropriate to more simply respond with the error, deferring the decision to retry to the client.
This may be resolved as a consequence of KNOX-1439 's resolution, but it may mean that a different dispatch be configured for the datanode interaction.
> WEBHDFS: retry should not be attempted for datanode write failures
> ------------------------------------------------------------------
>
> Key: KNOX-1440
> URL: https://issues.apache.org/jira/browse/KNOX-1440
> Project: Apache Knox
> Issue Type: Improvement
> Components: Server
> Affects Versions: 1.1.0
> Reporter: Phil Zampino
> Priority: Major
>
> For WEBHDFS invocations through Knox, if a *datanode* write fails with an IOException, the currently configured HA dispatch (DefaultHADispatch) attempts the write a second time.
> HDFS dev says that it would be appropriate to more simply respond with the error, deferring the decision to retry to the client.
> This may be resolved as a consequence of KNOX-1439 's resolution, but it may mean that a different dispatch be configured for the datanode interaction.
> (FYI: the datanode dispatch is configured in the WEBHDFS service definition)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)