Re: 0.23 & trunk tars, we'll we publishing 1 tar per component or a single tar? What about source tar?

+1 for option 4. Let the User starts required services from it. Regards, Uma - Original Message - From: giridharan kesavan Date: Wednesday, October 12, 2011 11:24 pm Subject: Re: 0.23 & trunk tars, we'll we publishing 1 tar per component or a single tar? What about source tar? To: hdfs-

Re: Problem in NetUtils

Please check the issue for more details. https://issues.apache.org/jira/browse/HADOOP-6682 issue : NetUtils:normalizeHostName does not process hostnames starting with [a-f] correctly Kihwal already mentioned the fixed versions. is this the issue you are facing? Regards, Uma - Original Mes

Re: Problem in NetUtils

0.21 is not actively maintained. The bug was fixed in other active branches (0.20-security, 0.22, 0.23, etc.) and trunk. Kihwal On 10/12/11 7:50 PM, "Beckham007" wrote: Hi, Today, I use org.apache.hadoop.net.NetUtils Class to change IP address and hostname. normalizeHostName but I think the

[jira] [Created] (HDFS-2444) A bug in unit test: TestDFSShell.testText()

A bug in unit test: TestDFSShell.testText() --- Key: HDFS-2444 URL: https://issues.apache.org/jira/browse/HDFS-2444 Project: Hadoop HDFS Issue Type: Bug Components: test Affects Versions:

[jira] [Created] (HDFS-2443) A bug in unit test: TestDFSShell.testPut()

A bug in unit test: TestDFSShell.testPut() -- Key: HDFS-2443 URL: https://issues.apache.org/jira/browse/HDFS-2443 Project: Hadoop HDFS Issue Type: Bug Components: test Affects Versions: 0

Problem in NetUtils

Hi, Today, I use org.apache.hadoop.net.NetUtils Class to change IP address and hostname. normalizeHostName but I think the normalizeHostName didn't works well. The Character.digit(name.charAt(0), 16) != -1 couldn't tell whether it's a IP address or a hostname. public static String normalizeHost

[jira] [Resolved] (HDFS-2231) Configuration changes for HA namenode

[ https://issues.apache.org/jira/browse/HDFS-2231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suresh Srinivas resolved HDFS-2231. --- Resolution: Fixed Hadoop Flags: Reviewed Todd, I have committed the patch. If you have a

[jira] [Resolved] (HDFS-2425) webhdfs GETFILESTATUS calls shows the localName as empty

[ https://issues.apache.org/jira/browse/HDFS-2425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arpit Gupta resolved HDFS-2425. --- Resolution: Not A Problem localName should be empty for this scenario > webhdfs GETFI

[jira] [Resolved] (HDFS-2431) webhdfs setpermission,settimes,setowner api does not return any content upon success

[ https://issues.apache.org/jira/browse/HDFS-2431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arpit Gupta resolved HDFS-2431. --- Resolution: Not A Problem expected empty content > webhdfs setpermission,settimes,set

replication in HDFS

Hello all, Right now HDFS is still using simple replication to increase data reliability. Even though it works, it just wastes the disk space, network and disk bandwidth. For data-intensive applications (that needs to write large result to the HDFS), it just limits the throughput of MapReduce. Als

Re: 0.23 & trunk tars, we'll we publishing 1 tar per component or a single tar? What about source tar?

+1 for option 4 On 10/12/11 9:50 AM, Eric Yang wrote: Option #4 is the most practical use case for making a release. For bleeding edge developers, they would prefer to mix and match different version of hdfs and mapreduce. Hence, it may be good to release the single tarball for release, bu

Re: 0.23 & trunk tars, we'll we publishing 1 tar per component or a single tar? What about source tar?

Option #4 is the most practical use case for making a release. For bleeding edge developers, they would prefer to mix and match different version of hdfs and mapreduce. Hence, it may be good to release the single tarball for release, but continue to support component tarballs for developers an

Re: A possible bug in unit test: TestDFSShell.testPut()

Hi Hou Song, This sounds like a bug to me. Please file a JIRA in the HDFS project by going to this link: https://issues.apache.org/jira/secure/CreateIssue!default.jspa -- Aaron T. Myers Software Engineer, Cloudera 2011/10/12 侯松 > Hi all, > > Recently I am rewriting testcases of Hadoop, and I

0.23 & trunk tars, we'll we publishing 1 tar per component or a single tar? What about source tar?

Currently common, hdfs and mapred create partial tars which are not usable unless they are stitched together into a single tar. With HADOOP-7642 the stitching happens as part of the build. The build currently produces the following tars: 1* common TAR 2* hdfs (partial) TAR 3* mapreduce (partial)

Jenkins build is still unstable: Hadoop-Hdfs-0.23-Build #37

See

Hadoop-Hdfs-0.23-Build - Build # 37 - Still Unstable

See https://builds.apache.org/job/Hadoop-Hdfs-0.23-Build/37/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 9775 lines...] main: [INFO] Executed tasks [INFO] [I

Hadoop-Hdfs-trunk - Build # 828 - Still Failing

See https://builds.apache.org/job/Hadoop-Hdfs-trunk/828/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 10372 lines...] [INFO] canGenerate is true [INFO] ** F

Build failed in Jenkins: Hadoop-Hdfs-trunk #828

See Changes: [ravigummadi] MAPREDUCE-3157. [Rumen] Fix TraceBuilder to handle 0.20 history file names also. [vinodkv] MAPREDUCE-3125. Modified TaskImpl to consider only non-failed, non-killed task-attempts for obtaining task's progr

A possible bug in unit test: TestDFSShell.testPut()

Hi all, Recently I am rewriting testcases of Hadoop, and I’ve just found a possible bug in TestDFSShell.testPut(). testPut() tries to copy a file from local to a destination “dst” in HDFS, and uses a SecurityManager to capture this action. The new SecurityManager filters out this copy action f