[jira] Created: (HADOOP-6416) Project Split Issue : Eclipse-Plugin under the Common Project in JIRA but the code is under the MapReduce project
Project Split Issue : Eclipse-Plugin under the Common Project in JIRA but the code is under the MapReduce project - Key: HADOOP-6416 URL: https://issues.apache.org/jira/browse/HADOOP-6416 Project: Hadoop Common Issue Type: Bug Components: contrib/eclipse-plugin Affects Versions: 0.20.1 Reporter: Stephen Watt Fix For: 0.20.2, 0.21.0, 0.22.0 contrib/eclipse-plugin is still listed under the Common Project in JIRA even though the code has been moved to the MapReduce project. As it stands, if one opens a JIRA issue for the eclipse plugin under the common project, one cannot provide a patch and resolve it as the code does not exist in that project. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: HDFS-758 in Hadoop-21 , Updates to Namenode health page
On Nov 25, 2009, at 12:46 PM, Allen Wittenauer wrote: Then you'll have no issues patching other things in 0.21 that are actual bug fixes that also meet this criteria, right? Or does this only apply to things that Yahoo! is hitting/deemed worthy? Allen raises a good point that the rest of the community may not need some of the features that Yahoo finds useful internally. It may clutter Hadoop unnecessarily. Most of these admin GUI improvements are pluggable. Perhaps this particular plugin did not even need to go into trunk. It could have been made available as a separate downloadable or contrib module. This way folks can use it across releases and only if they need it. Further, there are a few new GUI improvements in the hadoop community that are proprietary - we should make it easier to create new admin plugins easily. This way users can create new plugins that are useful to them internally; it also allows companies to create proprietary plugins for their customers. sanjay On 11/25/09 12:03 PM, Tsz Wo (Nicholas), Sze s29752-hadoop...@yahoo.com wrote: +1 on committing it to 0.21 I also agree that it does not impact the 0.21 release since the patch is already done. The argument of not committing it to 0.21 would be either (1) the patch is not safe, or (2) the patch is not that useful. I don't see they are the cases here. Nicholas Sze - Original Message From: Jakob Homan jho...@yahoo-inc.com To: common-dev@hadoop.apache.org Sent: Wed, November 25, 2009 11:31:08 AM Subject: Re: HDFS-758 in Hadoop-21 , Updates to Namenode health page +1. Backporting this does not in any way impact the release of 21. -Jakob Hairong Kuang wrote: +1. Although this is a new feature, I'd like to have it committed to 0.21 since we have so many issues with delayed decomission recently. Hairong On 11/24/09 6:06 PM, Suresh Srinivas wrote: +1. This will also help debug the issues when decommissioning takes a long time to complete. On 11/23/09 7:36 PM, Jitendra Nath Pandey wrote: Hi, We will be committing some changes to the Namenode Health page (dfshealth.jsp) as part of the fix in HDFS-758. This will enable us to monitor the progress of decommissioning of datanodes more effectively. Summary of changes : 1. A new link on the page for Decommissioning nodes. 2. This link will point to a new page with details about decommissioning status for each node which include a) Number of under-relplicated blocks in the node. b) Number of blocks with only no live replica (i.e. All its replicas are on decommissioning nodes). c) Number of under-replicated blocks in open files. d) Time since decommissioning started. 3. The main page will also contain total number of under- replicated blocks in the cluster. Thanks jitendra
Re: HDFS-758 in Hadoop-21 , Updates to Namenode health page
On Mon, Dec 7, 2009 at 2:00 PM, Sanjay Radia sra...@yahoo-inc.com wrote: On Nov 25, 2009, at 12:46 PM, Allen Wittenauer wrote: Then you'll have no issues patching other things in 0.21 that are actual bug fixes that also meet this criteria, right? Or does this only apply to things that Yahoo! is hitting/deemed worthy? Allen raises a good point that the rest of the community may not need some of the features that Yahoo finds useful internally. It may clutter Hadoop unnecessarily. Most of these admin GUI improvements are pluggable. Perhaps this particular plugin did not even need to go into trunk. It could have been made available as a separate downloadable or contrib module. This way folks can use it across releases and only if they need it. Further, there are a few new GUI improvements in the hadoop community that are proprietary - we should make it easier to create new admin plugins easily. This way users can create new plugins that are useful to them internally; it also allows companies to create proprietary plugins for their customers. +1 to administration plugins. I'm also +1 to HDFS-758 going into 21, would be genuinely useful to several customers. Thanks, Eli
[jira] Created: (HADOOP-6417) Alternative Java Distributions in the Hadoop Documention
Alternative Java Distributions in the Hadoop Documention Key: HADOOP-6417 URL: https://issues.apache.org/jira/browse/HADOOP-6417 Project: Hadoop Common Issue Type: Bug Components: documentation Affects Versions: 0.20.1 Reporter: Stephen Watt Priority: Minor Fix For: 0.20.2, 0.21.0, 0.22.0 The documentation on the Hadoop Site, Wiki and Download pages specify to use the Sun distribution of Java. While many people use and test with Sun Java, it is not always the appropriate choice, most notably when there is not a version available for the target OS. To help users In such situations we should provide them with information about the available alternatives. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
