I built the release from the rc tag, enabled timeline history service and
ran a sleep job on a pseudo-distributed cluster.
I encourage another rc, for 2.4.0 (non-binding)
1) Despite the discussion on YARN-1701, timeline AHS still sets
yarn.timeline-service.generic-application-history.fs-history-store.uri to a
location under ${hadoop.log.dir} that is meant for local file system, but
uses it on HDFS by default.
2) Critical patch for WebHdfs/Hftp to fix the filesystem contract HDFS-6143
is not included
3) Several patches that already proved themselves useful for diagnostics in
production and have been available for some months are still not included.
MAPREDUCE-5044/YARN-1515 is the most obvious example. Our users need to see
where the task container JVM got stuck when it was timed out by AM.
Thanks,
Gera
On Fri, Apr 4, 2014 at 3:51 PM, Azuryy <azury...@gmail.com> wrote:
> Arun,
>
> Do you mean you will cut another RC for 2.4?
>
>
> Sent from my iPhone5s
>
> > On 2014年4月5日, at 3:50, "Arun C. Murthy" <a...@hortonworks.com> wrote:
> >
> > Thanks for helping Tsuyoshi. Pls mark them as Blockers and set the
> fix-version to 2.4.1.
> >
> > Thanks again.
> >
> > Arun
> >
> >
> >> On Apr 3, 2014, at 11:38 PM, Tsuyoshi OZAWA <ozawa.tsuyo...@gmail.com>
> wrote:
> >>
> >> Hi,
> >>
> >> Updated a test result log based on the result of 2.4.0-rc0:
> >> https://gist.github.com/oza/9965197
> >>
> >> IMO, there are some blockers to be fixed:
> >> * MAPREDUCE-5815(TestMRAppMaster failure)
> >> * YARN-1872(TestDistributedShell failure)
> >> * HDFS: TestSymlinkLocalFSFileSystem failure on Linux (I cannot find
> >> JIRA about this failure)
> >>
> >> Now I'm checking the problem reported by Azuryy.
> >>
> >> Thanks,
> >> - Tsuyoshi
> >>
> >>> On Fri, Apr 4, 2014 at 8:55 AM, Tsuyoshi OZAWA <
> ozawa.tsuyo...@gmail.com> wrote:
> >>> Hi,
> >>>
> >>> Ran tests and confirmed that some tests(TestSymlinkLocalFSFileSystem)
> fail.
> >>> The log of the test failure is as follows:
> >>>
> >>> https://gist.github.com/oza/9965197
> >>>
> >>> Should we fix or disable the feature?
> >>>
> >>> Thanks,
> >>> - Tsuyoshi
> >>>
> >>>> On Mon, Mar 31, 2014 at 6:22 PM, Arun C Murthy <a...@hortonworks.com>
> wrote:
> >>>> Folks,
> >>>>
> >>>> I've created a release candidate (rc0) for hadoop-2.4.0 that I would
> like to get released.
> >>>>
> >>>> The RC is available at:
> http://people.apache.org/~acmurthy/hadoop-2.4.0-rc0
> >>>> The RC tag in svn is here:
> https://svn.apache.org/repos/asf/hadoop/common/tags/release-2.4.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
> >>>>
> >>>> --
> >>>> 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.
> >>>
> >>>
> >>>
> >>> --
> >>> - Tsuyoshi
> >>
> >>
> >>
> >> --
> >> - Tsuyoshi
> >
> > --
> > 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.
>
