JobTracker should collect statistics of failed map output fetches, and take
decisions to reexecute map tasks and/or restart the (possibly faulty) Jetty
server on the TaskTracker
---
[
https://issues.apache.org/jira/browse/HADOOP-1130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12483944
]
Tom White commented on HADOOP-1130:
---
Does the need updating in light of Owen's comments (and now HADOOP-1131 is
r
Konstantin Shvachko (JIRA) wrote:
Anonymous code is like public property: nobody cares, nobody takes
responsibility. Been there.
I'm not sure how file ownership solves this issue since the file may
have been revised with contributions from many others and the original
author may no longer b
[
https://issues.apache.org/jira/browse/HADOOP-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom White updated HADOOP-1131:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
I've just committed this. Thanks Ph
[
https://issues.apache.org/jira/browse/HADOOP-672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom White updated HADOOP-672:
-
Status: Open (was: Patch Available)
FsShell is no longer DFS-specific, so usage should show the invocati
[
https://issues.apache.org/jira/browse/HADOOP-1122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom White updated HADOOP-1122:
--
Resolution: Fixed
Fix Version/s: 0.13.0
Status: Resolved (was: Patch Available)
I'v
[
https://issues.apache.org/jira/browse/HADOOP-1068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom White updated HADOOP-1068:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
I've just committed this. Thanks Dh
