Thanks Shashikant for flagging the blocker issue.

RC1 now stands cancelled.

I will initiate RC2 shortly.



On Fri, Mar 13, 2020 at 12:08 PM Arpit Agarwal
<aagar...@cloudera.com.invalid> wrote:

> HDDS-3116 is now fixed in the ozone-0.5.0 branch.
>
> Folks - any more potential blockers before Dinesh spins RC2? I don’t see
> anything in Jira at the moment:
>
>
> https://issues.apache.org/jira/issues/?jql=project%20in%20(%22HDDS%22)%20and%20%22Target%20Version%2Fs%22%20in%20(0.5.0)%20and%20resolution%20in%20(Unresolved)%20and%20priority%20in%20(Blocker)
> <
> https://issues.apache.org/jira/issues/?jql=project%20in%20(%22HDDS%22)%20and%20%22Target%20Version/s%22%20in%20(0.5.0)%20and%20resolution%20in%20(Unresolved)%20and%20priority%20in%20(Blocker)
> >
>
> Thanks,
> Arpit
>
>
> > On Mar 9, 2020, at 6:15 PM, Shashikant Banerjee 
> > <sbaner...@cloudera.com.INVALID>
> wrote:
> >
> > I think https://issues.apache.org/jira/browse/HDDS-3116 <
> https://issues.apache.org/jira/browse/HDDS-3116> is a blocker for
> > the release. Because of this, datanodes fail to communicate with SCM and
> > marked dead and don't seem to recover.
> > This has been observed in multiple test setups.
> >
> > Thanks
> > Shashi
> >
> > On Mon, Mar 9, 2020 at 9:20 PM Attila Doroszlai <adorosz...@apache.org
> <mailto:adorosz...@apache.org>>
> > wrote:
> >
> >> +1
> >>
> >> * Verified GPG signature and SHA512 checksum
> >> * Compiled sources
> >> * Ran ozone smoke test against both binary and locally compiled versions
> >>
> >> Thanks Dinesh for RC1.
> >>
> >> -Attila
> >>
> >> On Sun, Mar 8, 2020 at 2:34 AM Arpit Agarwal
> >> <aagar...@cloudera.com.invalid> wrote:
> >>>
> >>> +1 (binding)
> >>> Verified mds, sha512
> >>> Verified signatures
> >>> Built from source
> >>> Deployed to 3 node cluster
> >>> Tried a few ozone shell and filesystem commands
> >>> Ran freon load generator
> >>> Thanks Dinesh for putting the RC1 together.
> >>>
> >>>
> >>>
> >>>> On Mar 6, 2020, at 4:46 PM, Dinesh Chitlangia <dineshc....@gmail.com>
> >> wrote:
> >>>>
> >>>> Hi Folks,
> >>>>
> >>>> We have put together RC1 for Apache Hadoop Ozone 0.5.0-beta.
> >>>>
> >>>> The RC artifacts are at:
> >>>> https://home.apache.org/~dineshc/ozone-0.5.0-rc1/
> >>>>
> >>>> The public key used for signing the artifacts can be found at:
> >>>> https://dist.apache.org/repos/dist/release/hadoop/common/KEYS
> >>>>
> >>>> The maven artifacts are staged at:
> >>>>
> >> https://repository.apache.org/content/repositories/orgapachehadoop-1260
> >>>>
> >>>> The RC tag in git is at:
> >>>> https://github.com/apache/hadoop-ozone/tree/ozone-0.5.0-beta-RC1
> >>>>
> >>>> This release contains 800+ fixes/improvements [1].
> >>>> Thanks to everyone who put in the effort to make this happen.
> >>>>
> >>>> *The vote will run for 7 days, ending on March 13th 2020 at 11:59 pm
> >> PST.*
> >>>>
> >>>> Note: This release is beta quality, it’s not recommended to use in
> >>>> production but we believe that it’s stable enough to try out the
> >> feature
> >>>> set and collect feedback.
> >>>>
> >>>>
> >>>> [1] https://s.apache.org/ozone-0.5.0-fixed-issues
> >>>>
> >>>> Thanks,
> >>>> Dinesh Chitlangia
> >>>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org <mailto:
> hdfs-dev-unsubscr...@hadoop.apache.org>
> >> For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org
> <mailto:hdfs-dev-h...@hadoop.apache.org>
>

Reply via email to