Re: Apache git mirrors, post project split

Chris Douglas wrote: The new git repositories for HDFS and Map/Reduce, git://git.apache.org/hadoop-{mapreduce,hdfs}.git are up. There are two open issues: (1) What to do with the defunct git mirror that points to core (2) What to call the common mirror For (1), I'd advocate simply deleting it.

[jira] Commented: (HADOOP-6107) Have some log messages designed for machine parsing, either real-time or post-mortem

[ https://issues.apache.org/jira/browse/HADOOP-6107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12724536#action_12724536 ] Steve Loughran commented on HADOOP-6107: sounds like you need a way of ha

[jira] Commented: (HADOOP-5555) JobClient should provide an API to return the job names of jobs

[ https://issues.apache.org/jira/browse/HADOOP-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12724142#action_12724142 ] Steve Loughran commented on HADOOP-: this is needed if you want a usable

[jira] Commented: (HADOOP-5388) Add ids to tables in JSP pages to ease scraping of the data.

[ https://issues.apache.org/jira/browse/HADOOP-5388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12724141#action_12724141 ] Steve Loughran commented on HADOOP-5388: -ids makes testing with HtmlUnit ea

Re: more information about project split

> Choices: >1. create/resolve/close to dev >2. create/resolve/close to dev, others to jira >3. create/comment/resolve/close to dev >4. all to dev > > The problem with 3 is that you can add comments on most of the > actions. So either you capture all events or you only capture part

[jira] Commented: (HADOOP-6107) Have some log messages designed for machine parsing, either real-time or post-mortem

[ https://issues.apache.org/jira/browse/HADOOP-6107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12724078#action_12724078 ] Steve Loughran commented on HADOOP-6107: and server side, similar issues {

[jira] Issue Comment Edited: (HADOOP-6107) Have some log messages designed for machine parsing, either real-time or post-mortem

[ https://issues.apache.org/jira/browse/HADOOP-6107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12724076#action_12724076 ] Steve Loughran edited comment on HADOOP-6107 at 6/25/09 5:5

[jira] Commented: (HADOOP-6107) Have some log messages designed for machine parsing, either real-time or post-mortem

[ https://issues.apache.org/jira/browse/HADOOP-6107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12724076#action_12724076 ] Steve Loughran commented on HADOOP-6107: as examples of the problem, some cl

[jira] Created: (HADOOP-6107) Have some log messages designed for machine parsing, either real-time or post-mortem

: Hadoop Common Issue Type: Improvement Affects Versions: 0.21.0 Reporter: Steve Loughran Many programs take the log output of bits of Hadoop, and try and parse it. Some may also put their own back end behind commons-logging, to capture the input without going via Log4J

[jira] Commented: (HADOOP-5073) Hadoop 1.0 Interface Classification - scope (visibility - public/private) and stability

[ https://issues.apache.org/jira/browse/HADOOP-5073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12724070#action_12724070 ] Steve Loughran commented on HADOOP-5073: @Jiaqi -that's a a separat

[jira] Commented: (HADOOP-5254) Xinclude setup results in a stack trace

[ https://issues.apache.org/jira/browse/HADOOP-5254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12723990#action_12723990 ] Steve Loughran commented on HADOOP-5254: For people seeing this -it may be

[jira] Commented: (HADOOP-6078) Ability to re-configure hadoop daemons online

[ https://issues.apache.org/jira/browse/HADOOP-6078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12721776#action_12721776 ] Steve Loughran commented on HADOOP-6078: * You could do much of this jus

[jira] Commented: (HADOOP-5478) Provide a node health check script and run it periodically to check the node health status

[ https://issues.apache.org/jira/browse/HADOOP-5478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12720731#action_12720731 ] Steve Loughran commented on HADOOP-5478: > Though, at both times, the o

[jira] Commented: (HADOOP-5700) INode.getPathComponents throws NPE when given a non-absolute path

[ https://issues.apache.org/jira/browse/HADOOP-5700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12720662#action_12720662 ] Steve Loughran commented on HADOOP-5700: I've just marked HADOOP-

[jira] Resolved: (HADOOP-6028) NPE server side when getting http://namenode/fileChecksum/*

[ https://issues.apache.org/jira/browse/HADOOP-6028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran resolved HADOOP-6028. Resolution: Duplicate > NPE server side when getting http://namenode/fileCheck

[jira] Commented: (HADOOP-5478) Provide a node health check script and run it periodically to check the node health status

[ https://issues.apache.org/jira/browse/HADOOP-5478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12720655#action_12720655 ] Steve Loughran commented on HADOOP-5478: # timestamps would help, would push

[jira] Commented: (HADOOP-6059) Should HDFS restrict the names used for files?

[ https://issues.apache.org/jira/browse/HADOOP-6059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12720616#action_12720616 ] Steve Loughran commented on HADOOP-6059: +1 for restrictions. I'd go

[jira] Commented: (HADOOP-5137) Move Datanode packet IO logging to its own log

[ https://issues.apache.org/jira/browse/HADOOP-5137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12720233#action_12720233 ] Steve Loughran commented on HADOOP-5137: Also block reports are fairly chatty

[jira] Commented: (HADOOP-3437) mapred.job.tracker default value/docs appear out of sync with code

[ https://issues.apache.org/jira/browse/HADOOP-3437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12720099#action_12720099 ] Steve Loughran commented on HADOOP-3437: 1. JobTracker should clearly recog

[jira] Commented: (HADOOP-3628) Add a lifecycle interface for Hadoop components: namenodes, job clients, etc.

[ https://issues.apache.org/jira/browse/HADOOP-3628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12720096#action_12720096 ] Steve Loughran commented on HADOOP-3628: I should add that the ping() metho

[jira] Commented: (HADOOP-6056) Use java.net.preferIPv4Stack to force IPv4

[ https://issues.apache.org/jira/browse/HADOOP-6056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12720072#action_12720072 ] Steve Loughran commented on HADOOP-6056: Correction, HADOOP-3437 &

[jira] Created: (HADOOP-6056) Use java.net.preferIPv4Stack to force IPv4

Affects Versions: 0.21.0 Reporter: Steve Loughran Fix For: 0.21.0 This was mentioned on HADOOP-3427, there is a property, java.net.preferIPv4Stack, which you set to true for the java net process to switch to IPv4 everywhere. As Hadoop doesn't work on IPv6, this shou

[jira] Commented: (HADOOP-5478) Provide a node health check script and run it periodically to check the node health status

[ https://issues.apache.org/jira/browse/HADOOP-5478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12720061#action_12720061 ] Steve Loughran commented on HADOOP-5478: 1. The timeouts in Shell would

[jira] Updated: (HADOOP-3628) Add a lifecycle interface for Hadoop components: namenodes, job clients, etc.

[ https://issues.apache.org/jira/browse/HADOOP-3628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated HADOOP-3628: --- Affects Version/s: (was: 0.20.0) 0.21.0 Status

[jira] Updated: (HADOOP-3628) Add a lifecycle interface for Hadoop components: namenodes, job clients, etc.

[ https://issues.apache.org/jira/browse/HADOOP-3628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated HADOOP-3628: --- Attachment: HADOOP-3628-18.patch This is the lifecycle code running against SVN_HEAD

[jira] Created: (HADOOP-6045) Not all of DfsClient's operations check the FS is open before calling the remote system

-6045 Project: Hadoop Core Issue Type: Bug Components: dfs Affects Versions: 0.21.0 Reporter: Steve Loughran Priority: Minor {{DFSClient.getDiskStatus()}} doesn't call {{checkOpen()}} before use; there look to be a few other operations t

[jira] Created: (HADOOP-6032) reference to java1.5 in conf/hadoop-env.sh

Versions: 0.21.0 Reporter: Steve Loughran Priority: Trivial conf/hadoop-env.sh has a commented out line # export JAVA_HOME=/usr/lib/j2sdk1.5-sun that path should be moved up to java 1.6 -- This message is automatically generated by JIRA. - You can reply to this email to add a

[jira] Commented: (HADOOP-6028) NPE server side when getting http://namenode/fileChecksum/*

[ https://issues.apache.org/jira/browse/HADOOP-6028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12718852#action_12718852 ] Steve Loughran commented on HADOOP-6028: Also, the fileChecksum servlet

[jira] Commented: (HADOOP-6028) NPE server side when getting http://namenode/fileChecksum/*

[ https://issues.apache.org/jira/browse/HADOOP-6028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12718851#action_12718851 ] Steve Loughran commented on HADOOP-6028: the line in question is part of

[jira] Commented: (HADOOP-6028) NPE server side when getting http://namenode/fileChecksum/*

[ https://issues.apache.org/jira/browse/HADOOP-6028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12718848#action_12718848 ] Steve Loughran commented on HADOOP-6028: web page contents {code} {code} s

[jira] Created: (HADOOP-6028) NPE server side when getting http://namenode/fileChecksum/*

Components: dfs Affects Versions: 0.21.0 Reporter: Steve Loughran Priority: Minor when using http://namenode/fileChecksum/* to see if the checksum servlet is live, I see an NPE message client side, and a stack trace on the namenode -- This message is automatically

[jira] Commented: (HADOOP-5478) Provide a node health check script and run it periodically to check the node health status

[ https://issues.apache.org/jira/browse/HADOOP-5478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12718819#action_12718819 ] Steve Loughran commented on HADOOP-5478: I do a fair amount of health monito

[jira] Commented: (HADOOP-5921) JobTracker does not come up because of NotReplicatedYetException

[ https://issues.apache.org/jira/browse/HADOOP-5921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12718425#action_12718425 ] Steve Loughran commented on HADOOP-5921: looks ok to me. could you change

[jira] Commented: (HADOOP-5993) Modify TestTaskLimits to improve execution time

[ https://issues.apache.org/jira/browse/HADOOP-5993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12717837#action_12717837 ] Steve Loughran commented on HADOOP-5993: failing tes

[jira] Updated: (HADOOP-4768) Dynamic Priority Scheduler that allows queue shares to be controlled dynamically by a currency

[ https://issues.apache.org/jira/browse/HADOOP-4768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated HADOOP-4768: --- Resolution: Fixed Status: Resolved (was: Patch Available) Committed. Thomas, I

[jira] Commented: (HADOOP-4768) Dynamic Priority Scheduler that allows queue shares to be controlled dynamically by a currency

[ https://issues.apache.org/jira/browse/HADOOP-4768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12717725#action_12717725 ] Steve Loughran commented on HADOOP-4768: OK, I'm patching it as we spea

[jira] Commented: (HADOOP-5478) Provide a node health check script and run it periodically to check the node health status

[ https://issues.apache.org/jira/browse/HADOOP-5478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12717209#action_12717209 ] Steve Loughran commented on HADOOP-5478: Cron? No, because you want to be abl

[jira] Commented: (HADOOP-4768) Dynamic Priority Scheduler that allows queue shares to be controlled dynamically by a currency

[ https://issues.apache.org/jira/browse/HADOOP-4768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12717082#action_12717082 ] Steve Loughran commented on HADOOP-4768: failing test is in HDFS proxy. This

[jira] Commented: (HADOOP-3625) Add an ip address mask to rack name java plugin

[ https://issues.apache.org/jira/browse/HADOOP-3625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12717081#action_12717081 ] Steve Loughran commented on HADOOP-3625: you can use {{netmask.length()==0)

[jira] Commented: (HADOOP-5478) Provide a node health check script and run it periodically to check the node health status

[ https://issues.apache.org/jira/browse/HADOOP-5478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12717040#action_12717040 ] Steve Loughran commented on HADOOP-5478: One thing to consider here is do

[jira] Commented: (HADOOP-4901) Upgrade to JUnit 4

[ https://issues.apache.org/jira/browse/HADOOP-4901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12716283#action_12716283 ] Steve Loughran commented on HADOOP-4901: remember that some of the criticism

[jira] Commented: (HADOOP-4901) Upgrade to JUnit 4

[ https://issues.apache.org/jira/browse/HADOOP-4901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12716277#action_12716277 ] Steve Loughran commented on HADOOP-4901: a lot of the tests are a bit wea

[jira] Updated: (HADOOP-4768) Dynamic Priority Scheduler that allows queue shares to be controlled dynamically by a currency

[ https://issues.apache.org/jira/browse/HADOOP-4768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated HADOOP-4768: --- Status: Patch Available (was: Open) > Dynamic Priority Scheduler that allows queue sha

[jira] Commented: (HADOOP-4768) Dynamic Priority Scheduler that allows queue shares to be controlled dynamically by a currency

[ https://issues.apache.org/jira/browse/HADOOP-4768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12716048#action_12716048 ] Steve Loughran commented on HADOOP-4768: If hudson is happy with this, I

[jira] Updated: (HADOOP-4768) Dynamic Priority Scheduler that allows queue shares to be controlled dynamically by a currency

[ https://issues.apache.org/jira/browse/HADOOP-4768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated HADOOP-4768: --- Status: Open (was: Patch Available) > Dynamic Priority Scheduler that allows queue sha

[jira] Updated: (HADOOP-4768) Dynamic Priority Scheduler that allows queue shares to be controlled dynamically by a currency

[ https://issues.apache.org/jira/browse/HADOOP-4768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated HADOOP-4768: --- Attachment: HADOOP-4768-6.patch This is the previous patch with the line ending property

[jira] Commented: (HADOOP-5945) Support running multiple DataNodes/TaskTrackers simultaneously in a single node

[ https://issues.apache.org/jira/browse/HADOOP-5945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12715909#action_12715909 ] Steve Loughran commented on HADOOP-5945: >only one datanode server per n

[jira] Commented: (HADOOP-5921) JobTracker does not come up because of NotReplicatedYetException

[ https://issues.apache.org/jira/browse/HADOOP-5921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12715527#action_12715527 ] Steve Loughran commented on HADOOP-5921: I have done a refactoring of th

[jira] Commented: (HADOOP-4901) Upgrade to JUnit 4

[ https://issues.apache.org/jira/browse/HADOOP-4901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12715523#action_12715523 ] Steve Loughran commented on HADOOP-4901: -you can run junit4 under , but

[jira] Commented: (HADOOP-5945) Support running multiple DataNodes/TaskTrackers simultaneously in a single node

[ https://issues.apache.org/jira/browse/HADOOP-5945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12715519#action_12715519 ] Steve Loughran commented on HADOOP-5945: The big issue is what do you gai

[jira] Commented: (HADOOP-4383) Add standard interface/methods for all services to query IPC and HTTP addresses and ports

[ https://issues.apache.org/jira/browse/HADOOP-4383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12715080#action_12715080 ] Steve Loughran commented on HADOOP-4383: Jeff, HADOOP-3628 adds a common

[jira] Commented: (HADOOP-5933) Make it harder to accidentally close a shared DFSClient

[ https://issues.apache.org/jira/browse/HADOOP-5933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12714436#action_12714436 ] Steve Loughran commented on HADOOP-5933: There isn't direct ca

[jira] Commented: (HADOOP-5792) to resolve jsp-2.1 jars through IVY

[ https://issues.apache.org/jira/browse/HADOOP-5792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12714423#action_12714423 ] Steve Loughran commented on HADOOP-

[jira] Updated: (HADOOP-5933) Make it harder to accidentally close a shared DFSClient

[ https://issues.apache.org/jira/browse/HADOOP-5933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated HADOOP-5933: --- Attachment: HADOOP-5933.patch This is the first solution, some extra diagnostics. It's

[jira] Commented: (HADOOP-5933) Make it harder to accidentally close a shared DFSClient

[ https://issues.apache.org/jira/browse/HADOOP-5933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12714027#action_12714027 ] Steve Loughran commented on HADOOP-5933: Some options # if the log is at d

[jira] Created: (HADOOP-5933) Make it harder to accidentally close a shared DFSClient

Components: fs Affects Versions: 0.21.0 Reporter: Steve Loughran Priority: Minor Every so often I get stack traces telling me that DFSClient is closed, usually in {{org.apache.hadoop.hdfs.DFSClient.checkOpen() }} . The root cause of this is usually that one thread has

[jira] Commented: (HADOOP-5792) to resolve jsp-2.1 jars through IVY

[ https://issues.apache.org/jira/browse/HADOOP-5792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12713937#action_12713937 ] Steve Loughran commented on HADOOP-5792: findjar implies that this missing

Re: 0.19.2 release needed

Brian Bockelman wrote: Hey Scott, We use 0.19.1 (plus some patches) heavily. The other CMS sites use the same version -- represents about 600TB of user community :) presumably this means you have enough of a cluster to do some testing on an RC? I'd be interested in seeing a 0.19.2 release

[jira] Commented: (HADOOP-5921) JobTracker does not come up because of NotReplicatedYetException

[ https://issues.apache.org/jira/browse/HADOOP-5921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12713934#action_12713934 ] Steve Loughran commented on HADOOP-5921: I'd like to see some way to

[jira] Commented: (HADOOP-4901) Upgrade to JUnit 4

[ https://issues.apache.org/jira/browse/HADOOP-4901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12713933#action_12713933 ] Steve Loughran commented on HADOOP-4901: testng runs junit3 tests, not junit4

[jira] Commented: (HADOOP-3628) Add a lifecycle interface for Hadoop components: namenodes, job clients, etc.

[ https://issues.apache.org/jira/browse/HADOOP-3628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12713535#action_12713535 ] Steve Loughran commented on HADOOP-3628: There is a new branch for this HA

[jira] Work started: (HADOOP-3628) Add a lifecycle interface for Hadoop components: namenodes, job clients, etc.

[ https://issues.apache.org/jira/browse/HADOOP-3628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HADOOP-3628 started by Steve Loughran. > Add a lifecycle interface for Hadoop components: namenodes, job clients,

[jira] Commented: (HADOOP-5573) TestBackupNode sometimes fails

[ https://issues.apache.org/jira/browse/HADOOP-5573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12713525#action_12713525 ] Steve Loughran commented on HADOOP-5573: I'm seeing this test fail with

[jira] Commented: (HADOOP-5921) JobTracker does not come up because of NotReplicatedYetException

[ https://issues.apache.org/jira/browse/HADOOP-5921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12713512#action_12713512 ] Steve Loughran commented on HADOOP-5921: Presumably that is because the NN i

[jira] Commented: (HADOOP-5626) SecondaryNamenode may report incorrect info host name

[ https://issues.apache.org/jira/browse/HADOOP-5626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12713211#action_12713211 ] Steve Loughran commented on HADOOP-5626: +1 to having something common I t

[jira] Created: (HADOOP-5909) Capacity Scheduler test TestQueueCapacities.testSingleQueue timing out -breaks hudson

Project: Hadoop Core Issue Type: Bug Components: contrib/capacity-sched Affects Versions: 0.21.0 Reporter: Steve Loughran Hudson is only failing now on one test: TestQueueCapacities.testSingleQueue in contrib/capacity-scheduler The test is timing out. -- This

[jira] Updated: (HADOOP-5890) Use exponential backoff on Thread.sleep during DN shutdown

[ https://issues.apache.org/jira/browse/HADOOP-5890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated HADOOP-5890: --- Resolution: Fixed Fix Version/s: 0.21.0 Status: Resolved (was: Patch

[jira] Commented: (HADOOP-5906) Stream test TestStreamingExitStatus fails with Out of Memory

[ 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 nee

[jira] Created: (HADOOP-5906) Stream test TestStreamingExitStatus fails with Out of Memory

Components: contrib/streaming Affects Versions: 0.21.0 Environment: OS/X, 64-bit x86 imac, 4GB RAM. Reporter: Steve Loughran Priority: Minor contrib/streaming tests are failing a test with an Out of Memory error on an OS/X Mac -same problem does not surface

[jira] Commented: (HADOOP-5847) Streaming unit tests failing for a while on trunk

[ 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,

[jira] Commented: (HADOOP-5847) Streaming unit tests failing for a while on trunk

[ 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

[jira] Commented: (HADOOP-5905) Provide better error messages when fs.default.name is invalid

[ https://issues.apache.org/jira/browse/HADOOP-5905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12712461#action_12712461 ] Steve Loughran commented on HADOOP-5905: I've submitted a patch that is

[jira] Updated: (HADOOP-5905) Provide better error messages when fs.default.name is invalid

[ https://issues.apache.org/jira/browse/HADOOP-5905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated HADOOP-5905: --- Status: Patch Available (was: Open) > Provide better error messages when fs.default.n

[jira] Updated: (HADOOP-5905) Provide better error messages when fs.default.name is invalid

[ https://issues.apache.org/jira/browse/HADOOP-5905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated HADOOP-5905: --- Attachment: HADOOP-5095-1.patch > Provide better error messages when fs.default.name

[jira] Created: (HADOOP-5905) Provide better error messages when fs.default.name is invalid

Components: dfs Affects Versions: 0.21.0 Reporter: Steve Loughran Assignee: Steve Loughran Priority: Minor this the followon to HADOOP-5687 - its not enough to detect bad uris, we need good error messages and a set of tests to make sure

[jira] Commented: (HADOOP-5687) Hadoop NameNode throws NPE if fs.default.name is the default value

[ https://issues.apache.org/jira/browse/HADOOP-5687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12712458#action_12712458 ] Steve Loughran commented on HADOOP-5687: well, I was just adding the tests t

[jira] Commented: (HADOOP-5687) Hadoop NameNode throws NPE if fs.default.name is the default value

[ https://issues.apache.org/jira/browse/HADOOP-5687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12712290#action_12712290 ] Steve Loughran commented on HADOOP-5687: Phil, are you looking at the -1.patc

[jira] Commented: (HADOOP-5890) Use exponential backoff on Thread.sleep during DN shutdown

[ https://issues.apache.org/jira/browse/HADOOP-5890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12712251#action_12712251 ] Steve Loughran commented on HADOOP-5890: +1 to anything that boosts s

[jira] Updated: (HADOOP-5687) Hadoop NameNode throws NPE if fs.default.name is the default value

[ https://issues.apache.org/jira/browse/HADOOP-5687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated HADOOP-5687: --- Status: Patch Available (was: Open) > Hadoop NameNode throws NPE if fs.default.name is

[jira] Updated: (HADOOP-5687) Hadoop NameNode throws NPE if fs.default.name is the default value

[ https://issues.apache.org/jira/browse/HADOOP-5687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated HADOOP-5687: --- Attachment: HADOOP-5687-extension-2.patch This patch -checks for hdfs before worrying

[jira] Updated: (HADOOP-5687) Hadoop NameNode throws NPE if fs.default.name is the default value

[ https://issues.apache.org/jira/browse/HADOOP-5687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated HADOOP-5687: --- Status: Open (was: Patch Available) > Hadoop NameNode throws NPE if fs.default.name is

[jira] Commented: (HADOOP-5901) FileSystem.fixName() has unexpected behaviour

[ https://issues.apache.org/jira/browse/HADOOP-5901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12712239#action_12712239 ] Steve Loughran commented on HADOOP-5901: examples {code} fixName("&

[jira] Created: (HADOOP-5901) FileSystem.fixName() has unexpected behaviour

Versions: 0.21.0 Reporter: Steve Loughran Priority: Minor {{FileSystem.fixName()}} tries to patch up fs.default.name values, but I'm not sure it helps that well. Has it been warning about deprecated values for long enough for it to be turned off? -- This messa

[jira] Commented: (HADOOP-5687) Hadoop NameNode throws NPE if fs.default.name is the default value

[ https://issues.apache.org/jira/browse/HADOOP-5687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12712238#action_12712238 ] Steve Loughran commented on HADOOP-5687: also, if fs.default.name=="&

[jira] Commented: (HADOOP-5140) setting fs.default.name to an invalid URI format kills init thread in JobTracker

[ https://issues.apache.org/jira/browse/HADOOP-5140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12712237#action_12712237 ] Steve Loughran commented on HADOOP-5140: This is only loosely related to HA

[jira] Commented: (HADOOP-5626) SecondaryNamenode may report incorrect info host name

[ https://issues.apache.org/jira/browse/HADOOP-5626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12712235#action_12712235 ] Steve Loughran commented on HADOOP-5626: I think we could tease out the code

[jira] Updated: (HADOOP-5687) Hadoop NameNode throws NPE if fs.default.name is the default value

[ https://issues.apache.org/jira/browse/HADOOP-5687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated HADOOP-5687: --- Status: Patch Available (was: Reopened) This will fail, but I want everyone to see the

[jira] Updated: (HADOOP-5687) Hadoop NameNode throws NPE if fs.default.name is the default value

[ https://issues.apache.org/jira/browse/HADOOP-5687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated HADOOP-5687: --- Attachment: HADOOP-5687-extension-1.patch this adds a new test case for the method. These

[jira] Commented: (HADOOP-5687) Hadoop NameNode throws NPE if fs.default.name is the default value

[ https://issues.apache.org/jira/browse/HADOOP-5687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12712219#action_12712219 ] Steve Loughran commented on HADOOP-5687: I'm going to stick some more

[jira] Reopened: (HADOOP-5687) Hadoop NameNode throws NPE if fs.default.name is the default value

[ https://issues.apache.org/jira/browse/HADOOP-5687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran reopened HADOOP-5687: reopening so we can get the error messages right > Hadoop NameNode throws NPE

[jira] Commented: (HADOOP-5626) SecondaryNamenode may report incorrect info host name

[ https://issues.apache.org/jira/browse/HADOOP-5626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12712217#action_12712217 ] Steve Loughran commented on HADOOP-5626: Todd, -can you use the code in DN

[jira] Updated: (HADOOP-4768) Dynamic Priority Scheduler that allows queue shares to be controlled dynamically by a currency

[ https://issues.apache.org/jira/browse/HADOOP-4768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated HADOOP-4768: --- Attachment: HADOOP-4768-5.patch updated patch -took all the IDEs suggestions on board

[jira] Updated: (HADOOP-4768) Dynamic Priority Scheduler that allows queue shares to be controlled dynamically by a currency

[ https://issues.apache.org/jira/browse/HADOOP-4768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated HADOOP-4768: --- Status: Patch Available (was: Open) > Dynamic Priority Scheduler that allows queue sha

[jira] Updated: (HADOOP-4768) Dynamic Priority Scheduler that allows queue shares to be controlled dynamically by a currency

[ https://issues.apache.org/jira/browse/HADOOP-4768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated HADOOP-4768: --- Status: Open (was: Patch Available) > Dynamic Priority Scheduler that allows queue sha

[jira] Commented: (HADOOP-5687) Hadoop NameNode throws NPE if fs.default.name is the default value

[ https://issues.apache.org/jira/browse/HADOOP-5687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12712089#action_12712089 ] Steve Loughran commented on HADOOP-5687: Linking to my duplicate bugrep

[jira] Resolved: (HADOOP-5200) NPE when the namenode comes up but the filesystem is set to file://

[ https://issues.apache.org/jira/browse/HADOOP-5200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran resolved HADOOP-5200. Resolution: Duplicate Fix Version/s: 0.21.0 > NPE when the namenode comes up

[jira] Commented: (HADOOP-5891) If dfs.http.address is default, SecondaryNameNode can't find NameNode

[ https://issues.apache.org/jira/browse/HADOOP-5891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12712083#action_12712083 ] Steve Loughran commented on HADOOP-5891: this whole problem of bootstrappi

[jira] Commented: (HADOOP-5200) NPE when the namenode comes up but the filesystem is set to file://

[ https://issues.apache.org/jira/browse/HADOOP-5200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12712036#action_12712036 ] Steve Loughran commented on HADOOP-5200: Yes, this duplicates HADOOP-5687, th

[jira] Updated: (HADOOP-5200) NPE when the namenode comes up but the filesystem is set to file://

[ https://issues.apache.org/jira/browse/HADOOP-5200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated HADOOP-5200: --- Summary: NPE when the namenode comes up but the filesystem is set to file:// (was: NPE

[jira] Commented: (HADOOP-2778) Hadoop job submission via ant using HMRExec

[ https://issues.apache.org/jira/browse/HADOOP-2778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12712031#action_12712031 ] Steve Loughran commented on HADOOP-2778: Putting my Ant team hat on here, we

  1   2   3   4   5   6   7   8   9   10   >