Constructing a JobConf without a class leads to a very misleading error message.
Key: HADOOP-1971
URL: https://issues.apache.org/jira/browse/HADOOP-1971
Project: Hadoop
[
https://issues.apache.org/jira/browse/HADOOP-1822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christophe Taton updated HADOOP-1822:
-
Attachment: 1822_2007-09-29_6.patch
The configuration now follows the suggested scheme:
[
https://issues.apache.org/jira/browse/HADOOP-1822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christophe Taton updated HADOOP-1822:
-
Attachment: (was: 1822-2007-09-11a.patch)
> Allow SOCKS proxy configuration to remot
[
https://issues.apache.org/jira/browse/HADOOP-1942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531257
]
rangadi edited comment on HADOOP-1942 at 9/29/07 10:04 AM:
Dhuba, this works around
[
https://issues.apache.org/jira/browse/HADOOP-1942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531257
]
Raghu Angadi commented on HADOOP-1942:
--
Dhuba, this works around the locking issue with a 1millisec sleep, whi
[
https://issues.apache.org/jira/browse/HADOOP-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531174
]
sriramsrao edited comment on HADOOP-1963 at 9/29/07 9:16 AM:
-
Doug---Thanks for pointing
[
https://issues.apache.org/jira/browse/HADOOP-1946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531248
]
Hadoop QA commented on HADOOP-1946:
---
+1 overall. Here are the results of testing the latest attachment
http://is
[
https://issues.apache.org/jira/browse/HADOOP-1946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hairong Kuang updated HADOOP-1946:
--
Status: Patch Available (was: Open)
> du should be not called on every heartbeat
> --
[
https://issues.apache.org/jira/browse/HADOOP-1789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531238
]
Hudson commented on HADOOP-1789:
Integrated in Hadoop-Nightly #254 (See
[http://lucene.zones.apache.org:8080/hudson
See http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Nightly/254/changes
f) Pardon me, Torsten, are you saying a logging facade is
inappropriate
(because it is not a library or framework)? Perhaps you are
saying the
opposite?
No - you got me right :)
IMHO logging facades are better suited for frameworks ...less useful
for applications. So I am +1 for using
[
https://issues.apache.org/jira/browse/HADOOP-1942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
dhruba borthakur updated HADOOP-1942:
-
Attachment: transactionLogSync2.patch
Thanks Raghu. I changed the locking slightly to ac
[
https://issues.apache.org/jira/browse/HADOOP-1935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531223
]
Hadoop QA commented on HADOOP-1935:
---
+1 overall. Here are the results of testing the latest attachment
http://is
[
https://issues.apache.org/jira/browse/HADOOP-1970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Koji Noguchi updated HADOOP-1970:
-
Description:
Saw one reduce task stuck on copy.
jstack on the reduce task(task_200709272248_0001
tasktracker hang in reduce. Deadlock between main and comm thread
-
Key: HADOOP-1970
URL: https://issues.apache.org/jira/browse/HADOOP-1970
Project: Hadoop
Issue Type: Bug
15 matches
Mail list logo