hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eli Collins (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HDFS-198) org.apache.hadoop.dfs.LeaseExpiredException during dfs write
Date Mon, 27 Sep 2010 21:44:34 GMT

    [ https://issues.apache.org/jira/browse/HDFS-198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12915497#action_12915497

Eli Collins commented on HDFS-198:

Yes, what I meant earlier was that you can still see this issue because loaded TT's that don't
respond for over 10 minutes are thought to be dead and therefore their leases expire. Perhaps
work similar to HDFS-599 needs to be done on the TT/JT?

> org.apache.hadoop.dfs.LeaseExpiredException during dfs write
> ------------------------------------------------------------
>                 Key: HDFS-198
>                 URL: https://issues.apache.org/jira/browse/HDFS-198
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: hdfs client, name-node
>            Reporter: Runping Qi
> Many long running cpu intensive map tasks failed due to org.apache.hadoop.dfs.LeaseExpiredException.
> See [a comment below|https://issues.apache.org/jira/browse/HDFS-198?focusedCommentId=12910298&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_12910298]
for the exceptions from the log:

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message