Hi Arpit

  This RC has incompatibilities with 1.0, such as 1.0 client can not talk
to 2.0 server

Thanks,
runzhiwang

Arpit Agarwal <[email protected]> 于2021年3月3日周三 上午5:51写道:

> Does this RC have any known wire incompatibilities with 1.0?
>
> E.g. will the following work?
>
>         - 1.0 client talking to 2.0 server and vice versa.
>         - 1.0 server and 2.0 server in the same raft group
>
> Thanks,
> Arpit
>
>
> > On Mar 1, 2021, at 3:34 PM, Rui Wang <[email protected]> wrote:
> >
> > +1 (non-binding)
> >
> > - built and ran test from the staged source: ok
> > - verify gpg signature: ok
> > - verify that sha512 and md5: ok
> > - confirm the most recent commits of git tag ratis-2.0.0-rc1 are in the
> > source: ok
> >
> > Thanks for working on this release @runzhiwang
> >
> > -Rui
> >
> > On Mon, Mar 1, 2021 at 6:50 AM Elek, Marton <[email protected]> wrote:
> >
> >> +1 (binding)
> >>
> >>  * checked the signatures
> >>  * checked the checksums (note: checksum files are not "sha512sum -c"
> >> compatible)
> >>  * Compiled ratis from the source
> >>  * Compared source package with the content of the tagged commit
> >>
> >>  * Executed full Ozone CI test suite on a branch which used the
> >> stagedartifacts: https://github.com/elek/ozone/actions/runs/610315967
> >>
> >>  * Deployed Ozone (updated to use 2.0.0 rc1) to Kubernetes and executed
> >> simple freon test (previous annoying NPE has been disappeared <3 )
> >>
> >> ozone version
> >>
> >> Source code repository https://github.com/apache/ozone.git -r
> >> 220bbdd5394384ce65c9a22bf072e6190a6ba16d
> >> Compiled by root on 2021-03-01T13:38Z
> >> Compiled with protoc 2.5.0
> >> From source with checksum cd133d775af90a27db52eebe6b95f
> >> With Apache Ratis: 2.0.0 from 797247f88fc046b2d5334881d92e7553859a19a8
> >>
> >> Using HDDS 1.1.0-SNAPSHOT
> >> Source code repository https://github.com/apache/ozone.git -r
> >> 220bbdd5394384ce65c9a22bf072e6190a6ba16d
> >> Compiled by root on 2021-03-01T13:37Z
> >> Compiled with protoc 2.5.0
> >> From source with checksum f5eeea37f69ac2fb4e154cc299c526ae
> >>
> >> Thanks for managing it @runzhiwang
> >> Marton
> >>
>
>

Reply via email to