+1

I checked out Kudu's source tagged with 1.13.0-RC2 from
https://github.com/apache/kudu git mirror and built it on CentOS6 in
RELEASE configuration.  I installed binaries at a 6-node cluster, and ran a
test workload of inserting 4B rows and then upserting them using tens of
Kudu C++ clients.  All worked as expected.

I checked out Kudu's source tagged with 1.13.0-RC2 from
https://github.com/apache/kudu git mirror and built it on CentOS Linux
release 8.2.2004 (Core) in DEBUG configuration.  Ran tests with ctest -j4,
and got the following stats:

99% tests passed, 6 tests failed out of 441

Label Time Summary:
no_dist_test    =  46.06 sec*proc (3 tests)
no_tsan         =  12.11 sec*proc (3 tests)

Total Test time (real) = 5067.18 sec

The following tests FAILED:
        109 - client-stress-test (Failed)
        111 - consistency-itest (Failed)
        214 - webserver-crawl-itest (Failed)
        217 - minidump_generation-itest (Failed)
        223 - master-test (Failed)
        231 - mini_ranger-test (Failed)

Out of the failed tests, mini_ranger-test failed due to the long startup
times of Ranger, and I posted a small patch to increase Ranger start
timeout (the test passed with the patch).  The rest failed due to a timeout
while negotiating a connection because of DNS resolution failures:

  913 09:35:43.932912 2169799 net_util.cc:413] Time spent look up canonical
hostname for localhost 'xxx-wifi': real 10.014s  user 0.000s     sys 0.000s

Once I fixed the name resolution issue, the tests passed with no issues.

I also successfully built Kudu at macOS HighSierra in debug configuration.
I ran 'ctest -j4': the majority of tests passed.  Some tests failed, but I
guess that's not a release stopper because macOS is a developer-only
platform for Kudu (IIRC, we haven't had all tests passing on macOS for a
long time).


Kind regards,

Alexey


On Fri, Sep 11, 2020 at 2:09 PM Attila Bukor <[email protected]> wrote:

> Hello Kudu devs!
>
> The Apache Kudu team is happy to announce the second release candidate for
> Apache Kudu 1.13.0.
>
> Apache Kudu 1.13.0 is a minor release that offers many improvements and
> fixes
> since Apache Kudu 1.12.0.
>
> This is a source-only release. The artifacts have been staged here:
> https://dist.apache.org/repos/dist/dev/kudu/1.13.0-RC2/
>
> Java convenience binaries in the form of a Maven repository are staged
> here:
> https://repository.apache.org/content/repositories/orgapachekudu-1085
>
> Linux (built on CentOS 6) and macOS (built on Catalina) test-only Kudu
> binary
> JAR artifacts are staged here:
> https://repository.apache.org/content/repositories/orgapachekudu-1087
>
> It is tagged in Git as 1.13.0-RC2 and signed with my key (found in the
> KEYS file
> below). Its commit hash is b4e0ad597fd9a88d63fa524e37141426a28c406a, you
> can
> check it out from ASF Gitbox or the official GitHub mirror:
>
> https://gitbox.apache.org/repos/asf?p=kudu.git;a=tag;h=refs/tags/1.13.0-RC2
> https://github.com/apache/kudu/releases/tag/1.13.0-RC2
>
> The KEYS file to verify the artifact and tag signatures can be found here:
> https://dist.apache.org/repos/dist/release/kudu/KEYS
>
> The release notes can be found here:
> https://github.com/apache/kudu/blob/1.13.0-RC2/docs/release_notes.adoc
>
> I'd suggest going through the release notes, building Kudu, and running
> the unit
> tests. Testing out the Maven repo would also be appreciated. Also, it's
> worth
> running Kudu Java tests against kudu-binary JAR artifact as described in
> the
> commit message here:
>
>
> https://gitbox.apache.org/repos/asf?p=kudu.git;a=commit;h=8a6faaa93f3e206ac75e8087731daccaf7ab646a
>
> The vote will run until a majority[1] is achieved, but at least until
> Wednesday
> Sep 16th 9:00:00 CEST 2020, which is a bit over the suggested 72 hours due
> to
> the weekend, to give everyone a chance to review this release candidate and
> vote.
>
> Thank You,
> Attila
>
> [1] https://www.apache.org/foundation/voting.html#ReleaseVotes
>
>

Reply via email to