See https://builds.apache.org/job/Hadoop-Common-trunk/488/
--
[...truncated 26568 lines...]
[DEBUG] (s) debug = false
[DEBUG] (s) effort = Default
[DEBUG] (s) failOnError = true
[DEBUG] (s) findbugsXmlOutput = false
[DEBUG] (s)
Costin Leau created HADOOP-8632:
---
Summary: Configuration leaking class-loaders
Key: HADOOP-8632
URL: https://issues.apache.org/jira/browse/HADOOP-8632
Project: Hadoop Common
Issue Type: Bug
Daryn Sharp created HADOOP-8633:
---
Summary: Interrupted FsShell copies may leave tmp files
Key: HADOOP-8633
URL: https://issues.apache.org/jira/browse/HADOOP-8633
Project: Hadoop Common
Issue
Daryn Sharp created HADOOP-8634:
---
Summary: Ensure FileSystem#close doesn't squawk for deleteOnExit
paths
Key: HADOOP-8634
URL: https://issues.apache.org/jira/browse/HADOOP-8634
Project: Hadoop Common
What do you have set as the fs.defaultFS in your configuration? Make sure
that that is a fully-qualified domain name.
--
Aaron T. Myers
Software Engineer, Cloudera
On Fri, Jul 27, 2012 at 1:57 PM, Arpit Gupta ar...@hortonworks.com wrote:
That does seem to be valid issue. Could you log a jira
Dear all,
We are running a hadoop 0.20.2 single node with hbase 0.20.4 and cannot restart
namenode after the disk got full. I have freed more space but cannot restart
Namenode and get the following error:
Someone has suggeted that the edits file was corrupted? How do you fix that?
Thanks.
Hello all,
I have just had a problem with a NameNode restart and someone on the mailing
list kindly suggested that the edits file was corrupted. I have made a backup
copy of the file and checked my /namesecondary/previous.checkpoint but the
edits file there is empty 4kb with ? inside.
Probably the last entry is partial or is complete but not terminated
properly. You need to hexedit the file in order to correct the error. You
can also pull HDFS-1378 and figure out the offset where you can put
OP_INVALID (0xff). HDFS-3055 implements the interactive recovery mode,
which makes it
Brahma Reddy Battula created HADOOP-8636:
Summary: Decommissioned nodes are included in cluster after switch
which is not expected
Key: HADOOP-8636
URL: https://issues.apache.org/jira/browse/HADOOP-8636
