Re: hadoop-2.4.1
Hi Arun, I'd like to know when to release Hadoop 2.4.1. It looks like all of the blockers have been resolved. Thanks, Akira (2014/04/24 5:59), Arun C Murthy wrote: Folks, Here is a handy short-cut to track 2.4.1: http://s.apache.org/hadoop-2.4.1-blockers I'm hoping we can get the majority of this in by end-of-week and have an RC for consideration. Committers - I appreciate if you could try treat review/commit of these as high-priority. Also, please feel free to add other *really* important fixes you'd like to see - let's also try be super cautious adding new content. thanks, Arun
/docs/current doesn't point to 2.4.0
Hi committers, Currently the latest version is 2.4.0, but http://hadoop.apache.org/docs/current/ points to 2.3.0. Would you mind updating the link to point to the latest version? Thanks Jacek for reporting this. https://issues.apache.org/jira/browse/HADOOP-10620 Regards, Akira
Re: hadoop-2.4.1
I'd like to see YARN-2065 fixed -without that the AM restart feature doesn't work. Or at least it works, but you can't create new containers On 20 May 2014 07:40, Akira AJISAKA ajisa...@oss.nttdata.co.jp wrote: Hi Arun, I'd like to know when to release Hadoop 2.4.1. It looks like all of the blockers have been resolved. Thanks, Akira (2014/04/24 5:59), Arun C Murthy wrote: Folks, Here is a handy short-cut to track 2.4.1: http://s.apache.org/hadoop-2. 4.1-blockers I'm hoping we can get the majority of this in by end-of-week and have an RC for consideration. Committers - I appreciate if you could try treat review/commit of these as high-priority. Also, please feel free to add other *really* important fixes you'd like to see - let's also try be super cautious adding new content. thanks, Arun -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You.
[jira] [Resolved] (HADOOP-10621) Remove CRLF for xattr value base64 encoding for better display.
[
https://issues.apache.org/jira/browse/HADOOP-10621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uma Maheswara Rao G resolved HADOOP-10621.
--
Resolution: Fixed
Hadoop Flags: Reviewed
I have just committed this to branch!
Remove CRLF for xattr value base64 encoding for better display.
---
Key: HADOOP-10621
URL: https://issues.apache.org/jira/browse/HADOOP-10621
Project: Hadoop Common
Issue Type: Improvement
Affects Versions: HDFS XAttrs (HDFS-2006)
Reporter: Yi Liu
Assignee: Yi Liu
Priority: Minor
Fix For: HDFS XAttrs (HDFS-2006)
Attachments: HDFS-6426.patch
{{Base64.encodeBase64String(value)}} encodes binary data using the base64
algorithm into 76 character blocks separated by CRLF.
In fs shell, xattrs display like:
{code}
# file: /user
user.a1=0sMTIz
user.a2=0sMTIzNDU2
user.a3=0sMTIzNDU2
{code}
We don't need multiple line and CRLF for xattr value, and we can use:
{code}
Base64 base64 = new Base64(0);
base64.encodeToString(value);
{code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
Issues in compiling Hadoop Maven Plugins Project
Hi Team, Where will I raise JIRA for issues related to Apache Hadoop Maven Plugins project. Will that be under Hadoop Common? Regards, Yogesh
[jira] [Resolved] (HADOOP-10592) Add unit test case for net in hadoop native client
[ https://issues.apache.org/jira/browse/HADOOP-10592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin Patrick McCabe resolved HADOOP-10592. --- Resolution: Fixed Fix Version/s: HADOOP-10388 Add unit test case for net in hadoop native client --- Key: HADOOP-10592 URL: https://issues.apache.org/jira/browse/HADOOP-10592 Project: Hadoop Common Issue Type: Sub-task Affects Versions: HADOOP-10388 Reporter: Wenwu Peng Assignee: Wenwu Peng Fix For: HADOOP-10388 Attachments: HADOOP-10592-pnative.001.patch, HADOOP-10592-pnative.002.patch, HADOOP-10592-pnative.003.patch, HADOOP-10592-pnative.004.patch Add unit test case for net.c in hadoop native client -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (HADOOP-10622) Shell.runCommand can deadlock
Jason Lowe created HADOOP-10622: --- Summary: Shell.runCommand can deadlock Key: HADOOP-10622 URL: https://issues.apache.org/jira/browse/HADOOP-10622 Project: Hadoop Common Issue Type: Bug Affects Versions: 2.3.0 Reporter: Jason Lowe Priority: Critical Ran into a deadlock in Shell.runCommand. Stacktrace details to follow. -- This message was sent by Atlassian JIRA (v6.2#6252)
Re: hadoop-2.4.1
Akira, Waiting for one more issue, stay tuned. thanks, Arun On Mon, May 19, 2014 at 11:40 PM, Akira AJISAKA ajisa...@oss.nttdata.co.jpwrote: Hi Arun, I'd like to know when to release Hadoop 2.4.1. It looks like all of the blockers have been resolved. Thanks, Akira (2014/04/24 5:59), Arun C Murthy wrote: Folks, Here is a handy short-cut to track 2.4.1: http://s.apache.org/hadoop-2. 4.1-blockers I'm hoping we can get the majority of this in by end-of-week and have an RC for consideration. Committers - I appreciate if you could try treat review/commit of these as high-priority. Also, please feel free to add other *really* important fixes you'd like to see - let's also try be super cautious adding new content. thanks, Arun -- -- Arun C. Murthy Hortonworks Inc. http://hortonworks.com/ -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You.
