[jira] Updated: (HADOOP-491) streaming jobs should allow programs that don't do any IO for a long time

[ https://issues.apache.org/jira/browse/HADOOP-491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Dahiya updated HADOOP-491: - Status: Patch Available (was: Open) streaming jobs should allow programs that don't do any IO

unsubscribe

unsubscribe

[jira] Commented: (HADOOP-964) ClassNotFoundException in ReduceTaskRunner

[ https://issues.apache.org/jira/browse/HADOOP-964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12469798 ] Owen O'Malley commented on HADOOP-964: -- I think the classpath2.patch looks like the right approach for the

[jira] Commented: (HADOOP-964) ClassNotFoundException in ReduceTaskRunner

[ https://issues.apache.org/jira/browse/HADOOP-964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12469800 ] Owen O'Malley commented on HADOOP-964: -- (Although the preferred style is to make a new patch that includes all

[jira] Commented: (HADOOP-885) Reduce CPU usage on namenode: gettimeofday

[ https://issues.apache.org/jira/browse/HADOOP-885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12469815 ] dhruba borthakur commented on HADOOP-885: - I included the change to maxIdleTime in that patch because this

[jira] Created: (HADOOP-969) deadlock in job tracker RetireJobs

deadlock in job tracker RetireJobs -- Key: HADOOP-969 URL: https://issues.apache.org/jira/browse/HADOOP-969 Project: Hadoop Issue Type: Bug Components: mapred Reporter: Owen O'Malley

[jira] Updated: (HADOOP-862) Add handling of s3 to CopyFile tool

[ https://issues.apache.org/jira/browse/HADOOP-862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] [EMAIL PROTECTED] updated HADOOP-862: - Attachment: copyfiles-s3-4.diff New patch to fix broken unit test. Removes 'dfs'

[jira] Commented: (HADOOP-885) Reduce CPU usage on namenode: gettimeofday

[ https://issues.apache.org/jira/browse/HADOOP-885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12469827 ] Raghu Angadi commented on HADOOP-885: - Sine we poll on idle connections, there is cpu cost even for idle

[jira] Updated: (HADOOP-969) deadlock in job tracker RetireJobs

[ https://issues.apache.org/jira/browse/HADOOP-969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Owen O'Malley updated HADOOP-969: - Attachment: jt-dead.patch This code has gotten pretty hairy, but this patch goes through the

[jira] Updated: (HADOOP-964) ClassNotFoundException in ReduceTaskRunner

[ https://issues.apache.org/jira/browse/HADOOP-964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Kubes updated HADOOP-964: Attachment: classpath3.patch This patch contains both the classloader (classpath2.path) and the

[jira] Commented: (HADOOP-969) deadlock in job tracker RetireJobs

[ https://issues.apache.org/jira/browse/HADOOP-969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12469833 ] Mahadev konar commented on HADOOP-969: -- + 1 the patch fixes the problem. deadlock in job tracker RetireJobs

[jira] Created: (HADOOP-970) Reduce CPU usage of hadoop ipc package

Reduce CPU usage of hadoop ipc package -- Key: HADOOP-970 URL: https://issues.apache.org/jira/browse/HADOOP-970 Project: Hadoop Issue Type: Bug Components: ipc Reporter: dhruba

[jira] Commented: (HADOOP-862) Add handling of s3 to CopyFile tool

[ https://issues.apache.org/jira/browse/HADOOP-862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12469836 ] [EMAIL PROTECTED] commented on HADOOP-862: -- Mr 'Hadoop QA', do I have to do anything special to re-trigger

[jira] Updated: (HADOOP-964) ClassNotFoundException in ReduceTaskRunner

[ https://issues.apache.org/jira/browse/HADOOP-964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doug Cutting updated HADOOP-964: Resolution: Fixed Status: Resolved (was: Patch Available) I just fixed this. Thanks,

[jira] Commented: (HADOOP-862) Add handling of s3 to CopyFile tool

[ https://issues.apache.org/jira/browse/HADOOP-862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12469841 ] Doug Cutting commented on HADOOP-862: - Mr 'Hadoop QA' [ ... ] Please, call him Nigel. Add handling of s3 to

Re: [jira] Commented: (HADOOP-862) Add handling of s3 to CopyFile tool

org.apache.hadoop.mapred.TestMiniMRLocalFS hung the process. I'm restarting now... On Feb 2, 2007, at 11:38 AM, Doug Cutting (JIRA) wrote: [ https://issues.apache.org/jira/browse/HADOOP-862? page=com.atlassian.jira.plugin.system.issuetabpanels:comment- tabpanel#action_12469841 ]

[jira] Commented: (HADOOP-862) Add handling of s3 to CopyFile tool

[ https://issues.apache.org/jira/browse/HADOOP-862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12469853 ] Hadoop QA commented on HADOOP-862: -- +1, because

[jira] Updated: (HADOOP-969) deadlock in job tracker RetireJobs

[ https://issues.apache.org/jira/browse/HADOOP-969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doug Cutting updated HADOOP-969: Resolution: Fixed Status: Resolved (was: Patch Available) I just committed this. Thanks,

[jira] Updated: (HADOOP-692) Rack-aware Replica Placement

[ https://issues.apache.org/jira/browse/HADOOP-692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hairong Kuang updated HADOOP-692: - Attachment: (was: rack.patch) Rack-aware Replica Placement

[jira] Updated: (HADOOP-965) Isolation Runner looking for job.jar in wrong directory

[ https://issues.apache.org/jira/browse/HADOOP-965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doug Cutting updated HADOOP-965: Resolution: Fixed Status: Resolved (was: Patch Available) I just committed this. Thanks,

[jira] Commented: (HADOOP-969) deadlock in job tracker RetireJobs

[ https://issues.apache.org/jira/browse/HADOOP-969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12469861 ] Hadoop QA commented on HADOOP-969: -- -1, because the patch command could not apply the latest attachment

[jira] Updated: (HADOOP-803) Reducing memory consumption on Namenode : Part 1

[ https://issues.apache.org/jira/browse/HADOOP-803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doug Cutting updated HADOOP-803: Status: Open (was: Patch Available) Patch doesn't apply to latest trunk. Reducing memory

[jira] Updated: (HADOOP-803) Reducing memory consumption on Namenode : Part 1

[ https://issues.apache.org/jira/browse/HADOOP-803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doug Cutting updated HADOOP-803: Attachment: HADOOP-803_4.patch Updated patch. Reducing memory consumption on Namenode : Part 1

[jira] Updated: (HADOOP-803) Reducing memory consumption on Namenode : Part 1

[ https://issues.apache.org/jira/browse/HADOOP-803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doug Cutting updated HADOOP-803: Status: Patch Available (was: Open) Patch now applies to current trunk, assuming I resolved the

Re: [jira] Commented: (HADOOP-969) deadlock in job tracker RetireJobs

Diregard Hadoop QA last comment. The patch couldn't be applied because the patch has already been committed. On Feb 2, 2007, at 12:37 PM, Hadoop QA (JIRA) wrote: [ https://issues.apache.org/jira/browse/HADOOP-969? page=com.atlassian.jira.plugin.system.issuetabpanels:comment-

[jira] Updated: (HADOOP-309) NullPointerException in StatusHttpServer

[ https://issues.apache.org/jira/browse/HADOOP-309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doug Cutting updated HADOOP-309: Resolution: Fixed Status: Resolved (was: Patch Available) I just committed this. Thanks,

[jira] Commented: (HADOOP-940) pendingReplications of FSNamesystem is not informative

[ https://issues.apache.org/jira/browse/HADOOP-940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12469874 ] Marco Nicosia commented on HADOOP-940: -- +1 This problem is causing real issues on running clusters, affecting

[jira] Commented: (HADOOP-893) dead datanode set should be maintained in the file handle or file system for hdfs

[ https://issues.apache.org/jira/browse/HADOOP-893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12469876 ] Doug Cutting commented on HADOOP-893: - This patch conflicts with HADOOP-692. Which should take priority? dead

Re: [jira] Commented: (HADOOP-893) dead datanode set should be maintained in the file handle or file system for hdfs

This patch hasn't been code reviewed. 692 should take priority. On Feb 2, 2007, at 1:24 PM, Doug Cutting (JIRA) wrote: [ https://issues.apache.org/jira/browse/HADOOP-893? page=com.atlassian.jira.plugin.system.issuetabpanels:comment- tabpanel#action_12469876 ] Doug Cutting commented

[jira] Commented: (HADOOP-940) pendingReplications of FSNamesystem is not informative

[ https://issues.apache.org/jira/browse/HADOOP-940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12469877 ] dhruba borthakur commented on HADOOP-940: - if a block is in pendingReplication, then it means that this

[jira] Commented: (HADOOP-893) dead datanode set should be maintained in the file handle or file system for hdfs

[ https://issues.apache.org/jira/browse/HADOOP-893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12469878 ] Owen O'Malley commented on HADOOP-893: -- I vote for HADOOP-692. It has been much better reviewed and it bigger.

[jira] Updated: (HADOOP-491) streaming jobs should allow programs that don't do any IO for a long time

[ https://issues.apache.org/jira/browse/HADOOP-491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doug Cutting updated HADOOP-491: Status: Open (was: Patch Available) I think instead of adding a new configuration option, this

[jira] Commented: (HADOOP-893) dead datanode set should be maintained in the file handle or file system for hdfs

[ https://issues.apache.org/jira/browse/HADOOP-893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12469882 ] Raghu Angadi commented on HADOOP-893: - Yes, HADDOP-692. I will update this patch after that. Also Dhruba still

[jira] Updated: (HADOOP-893) dead datanode set should be maintained in the file handle or file system for hdfs

[ https://issues.apache.org/jira/browse/HADOOP-893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raghu Angadi updated HADOOP-893: Status: Open (was: Patch Available) dead datanode set should be maintained in the file handle or

[jira] Updated: (HADOOP-803) Reducing memory consumption on Namenode : Part 1

[ https://issues.apache.org/jira/browse/HADOOP-803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Owen O'Malley updated HADOOP-803: - Fix Version/s: (was: 0.11.0) 0.12.0 Reducing memory consumption on

[jira] Work started: (HADOOP-933) Application defined InputSplits do not work

[ https://issues.apache.org/jira/browse/HADOOP-933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HADOOP-933 started by Owen O'Malley. Application defined InputSplits do not work --- Key: HADOOP-933

[jira] Updated: (HADOOP-803) Reducing memory consumption on Namenode : Part 1

[ https://issues.apache.org/jira/browse/HADOOP-803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raghu Angadi updated HADOOP-803: Status: Open (was: Patch Available) Thanks Doug. The new patch looks fine. For now I am removing

[jira] Commented: (HADOOP-803) Reducing memory consumption on Namenode : Part 1

[ https://issues.apache.org/jira/browse/HADOOP-803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12469918 ] Hairong Kuang commented on HADOOP-803: -- If the blocks were created after Namenode is started, one in inode

[jira] Updated: (HADOOP-692) Rack-aware Replica Placement

[ https://issues.apache.org/jira/browse/HADOOP-692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hairong Kuang updated HADOOP-692: - Attachment: (was: rack.patch) Rack-aware Replica Placement

[jira] Updated: (HADOOP-692) Rack-aware Replica Placement

[ https://issues.apache.org/jira/browse/HADOOP-692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hairong Kuang updated HADOOP-692: - Attachment: rack.patch Rack-aware Replica Placement

[jira] Updated: (HADOOP-692) Rack-aware Replica Placement

[ https://issues.apache.org/jira/browse/HADOOP-692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hairong Kuang updated HADOOP-692: - Fix Version/s: 0.11.0 Affects Version/s: (was: 0.8.0) 0.10.1

Hadoop nightly build failure

init: [mkdir] Created dir: /tmp/hadoop-nightly/build/classes [mkdir] Created dir: /tmp/hadoop-nightly/build/src [mkdir] Created dir: /tmp/hadoop-nightly/build/webapps/task/WEB-INF [mkdir] Created dir: /tmp/hadoop-nightly/build/webapps/job/WEB-INF [mkdir] Created dir:

[jira] Commented: (HADOOP-692) Rack-aware Replica Placement

[ https://issues.apache.org/jira/browse/HADOOP-692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12469921 ] Hadoop QA commented on HADOOP-692: -- +1, because http://issues.apache.org/jira/secure/attachment/12350262/rack.patch

[jira] Updated: (HADOOP-692) Rack-aware Replica Placement

[ https://issues.apache.org/jira/browse/HADOOP-692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doug Cutting updated HADOOP-692: Resolution: Fixed Status: Resolved (was: Patch Available) I just committed this. Thanks,

[jira] Commented: (HADOOP-940) pendingReplications of FSNamesystem is not informative

[ https://issues.apache.org/jira/browse/HADOOP-940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12469923 ] Hairong Kuang commented on HADOOP-940: -- If a block is in neededReplication, it means that it needs more copies

[jira] Commented: (HADOOP-803) Reducing memory consumption on Namenode : Part 1

[ https://issues.apache.org/jira/browse/HADOOP-803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12469924 ] Raghu Angadi commented on HADOOP-803: - Even after a name node starts up, a block in inode does not share the

[jira] Commented: (HADOOP-940) pendingReplications of FSNamesystem is not informative

[ https://issues.apache.org/jira/browse/HADOOP-940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12469926 ] Hairong Kuang commented on HADOOP-940: -- The purpose of having targets in PendingReplication is for avoid