hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Payne (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-9905) WebHdfsFileSystem#runWithRetry should display original stack trace on error
Date Thu, 09 Jun 2016 21:02:21 GMT

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

Eric Payne updated HDFS-9905:
-----------------------------
    Attachment: HDFS-9905-branch-2.7.002.patch

HDFS-7163, which introduced this problem, was originally merged back to 2.7, but this JIRA
(HDFS-9905), was not. The misleading stack trace is causing difficulty in debugging problems
for us, so I cherry-picked this back to 2.7: 

> WebHdfsFileSystem#runWithRetry should display original stack trace on error
> ---------------------------------------------------------------------------
>
>                 Key: HDFS-9905
>                 URL: https://issues.apache.org/jira/browse/HDFS-9905
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: test
>    Affects Versions: 2.7.3
>            Reporter: Kihwal Lee
>            Assignee: Wei-Chiu Chuang
>             Fix For: 2.8.0
>
>         Attachments: HDFS-9905-branch-2.7.002.patch, HDFS-9905.001.patch, HDFS-9905.002.patch
>
>
> When checking for a timeout in {{TestWebHdfsTimeouts}}, it does get {{SocketTimeoutException}},
but the message sometimes does not contain "connect timed out". Since the original exception
is not logged, we do not know details.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
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