Hi All,
Voting has ended with:
6 binding +1s
7 non-binding +1s (including mine)
0 -1s
0 0s
A few minor issues were reported by Xiaoyu/Bharat, I will file jira for
those.
I will proceed with releasing the artifacts and announcement.
Thank you all for voting for Ozone 0.5.0 beta RC2.
Regards,
Dinesh
On Mon, Mar 23, 2020 at 7:17 AM Shashikant Banerjee
<sbaner...@cloudera.com.invalid> wrote:
> +1 binding.
>
> - Verified hashes and signatures
> - Built from source
> - Ran Freon Random key generator
> - Verified unit tests
>
>
> Thanks Dinesh for driving the release.
>
> Thanks
> Shashi
>
> On Mon, Mar 23, 2020 at 8:58 AM Xiaoyu Yao <x...@cloudera.com.invalid>
> wrote:
>
> > +1 binding
> > Download source and verify signature.
> > Verify build and documents.
> > Deployed an 11 node cluster (3 om with ha, 6 datanodes, 1 scm and 1 s3g)
> > Verify multiple RATIS-3 pipelines are created as expected.
> > Tried ozone shell commands via o3 and o3fs, focus on security and HA
> > related.
> > Only find a few minor issues that we can fix in followup JIRAs.
> > 1) ozone getconf -ozonemanagers does not return all the om instances
> > bash-4.2$ ozone getconf -ozonemanagers
> > 0.0.0.0
> > 2) The document on specifying service/ID can be improved. More
> > specifically, the URI should give examples for the Service ID in HA.
> > Currently, it only mentions host/port.
> >
> > ozone sh vol create /vol1
> > Service ID or host name must not be omitted when ozone.om.service.ids is
> > defined.
> > bash-4.2$ ozone sh vol create --help
> > Usage: ozone sh volume create [-hV] [--root] [-q=<quota>] [-u=<userName>]
> > <uri>
> > Creates a volume for the specified user
> > <uri> URI of the volume.
> > Ozone URI could start with o3:// or without
> > prefix. URI
> > may contain the host and port of the OM
> server.
> > Both are
> > optional. If they are not specified it will
> be
> > identified from the config files.
> > 3). ozone scmcli container list seems report incorrect numberOfKeys and
> > usedBytes
> > Also, container owner is set as the current leader om(om3), should we use
> > the om service id here instead?
> > bash-4.2$ ozone scmcli container list
> > {
> > "state" : "OPEN",
> > "replicationFactor" : "THREE",
> > "replicationType" : "RATIS",
> > "usedBytes" : 3813,
> > "numberOfKeys" : 1,
> > ...
> > bash-4.2$ ozone sh key list o3://id1/vol1/bucket1/
> > {
> > "volumeName" : "vol1",
> > "bucketName" : "bucket1",
> > "name" : "k1",
> > "dataSize" : 3813,
> > "creationTime" : "2020-03-23T03:23:30.670Z",
> > "modificationTime" : "2020-03-23T03:23:33.207Z",
> > "replicationType" : "RATIS",
> > "replicationFactor" : 3
> > }
> > {
> > "volumeName" : "vol1",
> > "bucketName" : "bucket1",
> > "name" : "k2",
> > "dataSize" : 3813,
> > "creationTime" : "2020-03-23T03:18:46.735Z",
> > "modificationTime" : "2020-03-23T03:20:15.005Z",
> > "replicationType" : "RATIS",
> > "replicationFactor" : 3
> > }
> >
> >
> > Run freon with random key generation.
> >
> > Thanks Dinesh for driving the the release of Beta RC2.
> >
> > Xiaoyu
> >
> > On Sun, Mar 22, 2020 at 2:51 PM Aravindan Vijayan
> > <avija...@cloudera.com.invalid> wrote:
> >
> > > +1
> > > Deployed a 3 node cluster
> > > Tried ozone shell and filesystem commands
> > > Ran freon load generator
> > >
> > > Thanks Dinesh for working on the RC2.
> > >
> > > On Sun, Mar 15, 2020 at 7:27 PM Dinesh Chitlangia <
> dineshc....@gmail.com
> > >
> > > wrote:
> > >
> > > > Hi Folks,
> > > >
> > > > We have put together RC2 for Apache Hadoop Ozone 0.5.0-beta.
> > > >
> > > > The RC artifacts are at:
> > > > https://home.apache.org/~dineshc/ozone-0.5.0-rc2/
> > > >
> > > > 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-1262
> > > >
> > > > The RC tag in git is at:
> > > > https://github.com/apache/hadoop-ozone/tree/ozone-0.5.0-beta-RC2
> > > >
> > > > 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 22nd 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
> > > >
> > >
> >
>
