[
https://issues.apache.org/jira/browse/HADOOP-2757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12712650#action_12712650
]
dhruba borthakur commented on HADOOP-2757:
--
> 1. rpc timeout: the patch seems to
[
https://issues.apache.org/jira/browse/HADOOP-5896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jothi Padmanabhan updated HADOOP-5896:
--
Assignee: Sharad Agarwal
> Remove the dependency of GenericOptionsParser on Option.wit
[
https://issues.apache.org/jira/browse/HADOOP-5896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12712648#action_12712648
]
Jothi Padmanabhan commented on HADOOP-5896:
---
The following test is not running w
[
https://issues.apache.org/jira/browse/HADOOP-5252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sharad Agarwal updated HADOOP-5252:
---
Resolution: Fixed
Fix Version/s: 0.21.0
Hadoop Flags: [Reviewed]
Statu
[
https://issues.apache.org/jira/browse/HADOOP-5623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12712642#action_12712642
]
Jothi Padmanabhan commented on HADOOP-5623:
---
Changes look fine.
However, the tes
[
https://issues.apache.org/jira/browse/HADOOP-5438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
dhruba borthakur updated HADOOP-5438:
-
Resolution: Fixed
Fix Version/s: 0.21.0
Status: Resolved (was: Patch A
[
https://issues.apache.org/jira/browse/HADOOP-5890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12712637#action_12712637
]
dhruba borthakur commented on HADOOP-5890:
--
+1. Code looks good.
> Use exponent
[
https://issues.apache.org/jira/browse/HADOOP-5739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12712636#action_12712636
]
Hemanth Yamijala commented on HADOOP-5739:
--
Some comments:
- In JobTracker.proce
[
https://issues.apache.org/jira/browse/HADOOP-5900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
dhruba borthakur updated HADOOP-5900:
-
Resolution: Fixed
Fix Version/s: (was: 0.18.3)
(was: 0.
[
https://issues.apache.org/jira/browse/HADOOP-5895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ravi Gummadi updated HADOOP-5895:
-
Attachment: HADOOP-5895.v1.patch
Agreed Jothi.
Here is the patch with a flag doing the work of c
[
https://issues.apache.org/jira/browse/HADOOP-5883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hemanth Yamijala updated HADOOP-5883:
-
Attachment: HADOOP-5883.patch
The attached patch file incorporates the changes as mentio
[
https://issues.apache.org/jira/browse/HADOOP-5883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hemanth Yamijala updated HADOOP-5883:
-
Status: Patch Available (was: Open)
> TaskMemoryMonitorThread might shoot down tasks ev
[
https://issues.apache.org/jira/browse/HADOOP-5859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12712631#action_12712631
]
dhruba borthakur commented on HADOOP-5859:
--
> 2) dataQueue lock and ackQueue lock
[
https://issues.apache.org/jira/browse/HADOOP-5883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12712630#action_12712630
]
Hemanth Yamijala commented on HADOOP-5883:
--
As per some offline discussions with
[
https://issues.apache.org/jira/browse/HADOOP-5895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12712629#action_12712629
]
Jothi Padmanabhan commented on HADOOP-5895:
---
Using a flag to control the number
[
https://issues.apache.org/jira/browse/HADOOP-5710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12712628#action_12712628
]
Amareshwari Sriramadasu commented on HADOOP-5710:
-
Contrib test failures a
See http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-vesta.apache.org/394/
--
[...truncated 507968 lines...]
[exec] [junit] 09/05/25 02:57:38 INFO mapred.IndexCache: Map ID
attempt_200905250244_0001_m_02_2 not found in cache
[exec]
See
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-vesta.apache.org/393/changes
Changes:
[gkesavan] HADOOP-5847. Fixed failing Streaming unit tests
--
[...truncated 435061 lines...]
[exec] [junit] 09/05/24 22:29:58 WARN mapred.JobInProgre
[
https://issues.apache.org/jira/browse/HADOOP-5472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12712611#action_12712611
]
Hadoop QA commented on HADOOP-5472:
---
-1 overall. Here are the results of testing the la
[
https://issues.apache.org/jira/browse/HADOOP-5904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12712590#action_12712590
]
Kan Zhang commented on HADOOP-5904:
---
> this issue will be fixed in the trunk as part of
See http://hudson.zones.apache.org/hudson/job/Hadoop-trunk/845/
--
[...truncated 499674 lines...]
[junit] 09/05/24 18:02:50 INFO datanode.DataNode: PacketResponder 0 for
block blk_-3110252916069208619_1008 terminating
[junit] 09/05/24 18:02:50 INFO
[
https://issues.apache.org/jira/browse/HADOOP-5906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12712569#action_12712569
]
Steve Loughran commented on HADOOP-5906:
stack trace. Presumably we just need to s
Stream test TestStreamingExitStatus fails with Out of Memory
Key: HADOOP-5906
URL: https://issues.apache.org/jira/browse/HADOOP-5906
Project: Hadoop Core
Issue Type: Bug
[
https://issues.apache.org/jira/browse/HADOOP-5847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Giridharan Kesavan updated HADOOP-5847:
---
Resolution: Fixed
Fix Version/s: 0.21.0
Status: Resolved (was: Pat
[
https://issues.apache.org/jira/browse/HADOOP-5847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12712566#action_12712566
]
Steve Loughran commented on HADOOP-5847:
I'm willing to do the commit, but just ne
[
https://issues.apache.org/jira/browse/HADOOP-5847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12712563#action_12712563
]
Giridharan Kesavan commented on HADOOP-5847:
should we commit this?
> Stream
See http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-vesta.apache.org/392/
--
[...truncated 544191 lines...]
[exec] [junit] 09/05/24 13:27:40 INFO mapred.TaskTracker:
attempt_200905241327_0001_m_01_0 0.0% cleanup > map
[exec] [ju
[
https://issues.apache.org/jira/browse/HADOOP-5170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12712550#action_12712550
]
Hadoop QA commented on HADOOP-5170:
---
-1 overall. Here are the results of testing the la
[
https://issues.apache.org/jira/browse/HADOOP-5847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12712540#action_12712540
]
Steve Loughran commented on HADOOP-5847:
I'm running these tests at home (OSX) , a
[
https://issues.apache.org/jira/browse/HADOOP-5816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
He Yongqiang updated HADOOP-5816:
-
Status: Patch Available (was: Open)
> ArrayIndexOutOfBoundsException when using KeyFieldBasedCo
[
https://issues.apache.org/jira/browse/HADOOP-5816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
He Yongqiang updated HADOOP-5816:
-
Attachment: hadoop-5816-2009-05-24.patch
Talked with Min about this bug two weeks ago. This is a
[
https://issues.apache.org/jira/browse/HADOOP-5438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12712527#action_12712527
]
dhruba borthakur commented on HADOOP-5438:
--
+1 Code looks good. I will commit it
[
https://issues.apache.org/jira/browse/HADOOP-5887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12712526#action_12712526
]
Hadoop QA commented on HADOOP-5887:
---
-1 overall. Here are the results of testing the la
See http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-vesta.apache.org/391/
--
[...truncated 20 lines...]
[exec]
[exec]
==
[exec]
=
[
https://issues.apache.org/jira/browse/HADOOP-5620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12712525#action_12712525
]
Hadoop QA commented on HADOOP-5620:
---
-1 overall. Here are the results of testing the la
See http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-vesta.apache.org/390/
--
[...truncated 514737 lines...]
[exec] [junit] 09/05/24 08:53:40 INFO mapred.TaskTracker:
attempt_200905240853_0001_m_01_0 0.0%
[exec] [junit] 09/05/24
If the client and all the datanode(s) for a block are dead, then the file is
corrupt. It cannot be recovered and the lease cannot be reclaimed. Is that a
problem?
> your replication factor is 3 and the NN's minReplication is also 3.
In the current trunk, the NN guarantees to keep blocks replicat
[
https://issues.apache.org/jira/browse/HADOOP-5759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12712524#action_12712524
]
dhruba borthakur commented on HADOOP-5759:
--
This patch keeps the original aim of
38 matches
Mail list logo