Hudson failures with NoClassDefFoundError? (MAPREDUCE-1275)

For the past couple of weeks, I've seen errors like this popping up on a lot of Hudson HDFS test-patch builds. It's always NoClassDefFoundError and I think it's also always occurring for some cross-project class dependencies. Anyone have any ideas what's going on here? I thought at one point that

Re: Rolling a Hadoop 0.20.2

I don't think 101 is a real blocker - I haven't been able to reliably produce it. HDFS-793 fixes most of the issues I've seen in practice, and we now have a new patch in branch-20 which should fix that. 127 would be nice - there's a patch on that JIRA waiting for review as below. -Todd On Wed, J

Re: JIRA Edits?

I had called for a vote some time earlier on this (since I myself hate not being able to edit jira comments) but it did not pass. I doubt if folks who vetoed the vote have changed their opinions. Thanks mahadev On 1/26/10 9:06 PM, "Owen O'Malley" wrote: > Doug decided he didn't like the major

Re: Rolling a Hadoop 0.20.2

If the new release included (fixedup) hdfs-127 and hdfs-101, the hbase crew would be big fans of an hadoop 0.20.2. St.Ack On Tue, Jan 26, 2010 at 7:09 PM, Todd Lipcon wrote: > HDFS-127 was originally committed, then rolled back from 0.20 as it caused > test timeouts due to infinite loop. I put a

[jira] Created: (HADOOP-6517) Ability to add/get tokens from UserGroupInformation

Ability to add/get tokens from UserGroupInformation --- Key: HADOOP-6517 URL: https://issues.apache.org/jira/browse/HADOOP-6517 Project: Hadoop Common Issue Type: New Feature Report

[jira] Created: (HADOOP-6516) Distch is not documented?

Distch is not documented? - Key: HADOOP-6516 URL: https://issues.apache.org/jira/browse/HADOOP-6516 Project: Hadoop Common Issue Type: Bug Components: documentation Reporter: Allen Wittenauer

[jira] Resolved: (HADOOP-5436) job history directory grows without bound, locks up job tracker on new job submission

[ https://issues.apache.org/jira/browse/HADOOP-5436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jakob Homan resolved HADOOP-5436. - Resolution: Won't Fix > job history directory grows without bound, locks up job tracker on new j

[jira] Reopened: (HADOOP-5436) job history directory grows without bound, locks up job tracker on new job submission

[ https://issues.apache.org/jira/browse/HADOOP-5436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jakob Homan reopened HADOOP-5436: - > job history directory grows without bound, locks up job tracker on new job > submission > ---

[jira] Created: (HADOOP-6515) Make maximum number of http threads configurable

Make maximum number of http threads configurable Key: HADOOP-6515 URL: https://issues.apache.org/jira/browse/HADOOP-6515 Project: Hadoop Common Issue Type: Improvement Reporter: Sc

[jira] Created: (HADOOP-6514) Failed to run pseudo-distributed cluster on Win XP

Failed to run pseudo-distributed cluster on Win XP -- Key: HADOOP-6514 URL: https://issues.apache.org/jira/browse/HADOOP-6514 Project: Hadoop Common Issue Type: Bug Components: fs

Re: JIRA Edits?

Owen O'Malley wrote: Doug decided he didn't like the majority of people editing their comments on jira and disabled edits. I did propose that we disable comment editing. There was some discussion, but no one vetoed the proposal, so I implemented it. The rationale is that comment edits as im

Re: JIRA Edits?

On 1/26/10 9:06 PM, "Owen O'Malley" wrote: > Doug decided he didn't like the majority of people editing their comments on > jira and disabled edits. If you want it back, please start a vote on this > list. I think instead I'll just put comment after comment making corrections. Less bureaucrac