If it's not too late, I'd like to bring your attention to YARN-1692. We get a ConcurrentModificationException with the fair scheduler when it updates demand, and we saw RM get into a pretty bad shape around the time this happened. It would be great if this could make 2.3.0. I provided a patch for this fix already.
Thoughts? Thanks, Sangjin On Wed, Feb 12, 2014 at 11:41 AM, Stack <st...@duboce.net> wrote: > +1 > > Downloaded, deployed to small cluster, and then ran an hbase loading on top > of it. Looks good. > > Packaging wise, is it intentional that some jars show up a few times? I > can understand webapps bundling a copy but doesn't mapreduce depend on > commons? > > share/hadoop/mapreduce/lib/hadoop-annotations-2.3.0.jar > > share/hadoop/httpfs/tomcat/webapps/webhdfs/WEB-INF/lib/hadoop-annotations-2.3.0.jar > share/hadoop/common/lib/hadoop-annotations-2.3.0.jar > > If not intentional, I can make up a better report and file an issue. > > Thanks, > St.Ack > > > > > On Tue, Feb 11, 2014 at 6:49 AM, Arun C Murthy <a...@hortonworks.com> > wrote: > > > Folks, > > > > I've created a release candidate (rc0) for hadoop-2.3.0 that I would like > > to get released. > > > > The RC is available at: > > http://people.apache.org/~acmurthy/hadoop-2.3.0-rc0 > > The RC tag in svn is here: > > https://svn.apache.org/repos/asf/hadoop/common/tags/release-2.3.0-rc0 > > > > The maven artifacts are available via repository.apache.org. > > > > Please try the release and vote; the vote will run for the usual 7 days. > > > > thanks, > > Arun > > > > PS: Thanks to Andrew, Vinod & Alejandro for all their help in various > > release activities. > > -- > > 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. > > >
