belated +1 - ran the docker build on MacOS - ran through kudu and impala quickstarts twice (first time encountered error with impala-shell, which I was not able to reproduce)
Greg On Thu, Apr 30, 2020 at 6:22 PM Andrew Wong <[email protected]> wrote: > +1 > > I ran through all C++ tests on CentOS 7. I had a running HMS instance that > prevented many HMS tests from passing, but the C++ tests passed otherwise. > > I also deployed the binaries on a 10-node cluster. > - Ran a small Spark insert + Impala scan workload against the cluster while > orchestrated a rolling restart using the maintenance mode and quiescing > tooling. > - Looked through the web UI pages for the new changes mentioned in the > release notes. > - Used the `kudu table create` tool to create some tables. > - Used the `kudu cluster rebalance` tool to move all replicas off of a > single tablet server after running `kudu tserver state enter_maintenance` > for a specific server. > - I enabled auto rebalancing and I think I found an issue with it in that > it doesn't seem to successfully schedule moves. I filed KUDU-3113 > <https://jira.apache.org/jira/browse/KUDU-3113> for the issue, in which I > suggest removing its release note. Given it's already marked experimental, > I don't think it's a release blocker. > - It's also worth noting the bloom filter predicate requires this patch > <https://gerrit.cloudera.org/c/15767/> to run, otherwise it may result in > a > crash. I think this probably warrants the removal of its release note for > now. > > On Thu, Apr 30, 2020 at 5:10 PM Bankim Bhavsar <[email protected] > > > wrote: > > > +1 > > > > I was able to successfully compile debug and release builds on Linux and > > Mac OS. > > > > I ran C++ tests against debug and release builds on Linux using > dist-test. > > Only the following test failed on release build. > > > > [ RUN ] > > MaintenanceManagerTest.TestPrioritizeLogRetentionUnderMemoryPressure > > /data/12/bankim/src/kudu/src/kudu/util/maintenance_manager-test.cc:394: > > Failure > > Expected: op_and_why.second > > Which is: "under memory pressure (2.00% used), 100 bytes log > > retention, and flush 100 bytes memory" > > To be equal to: "under memory pressure (0.00% used), 100 bytes log > > retention, and " "flush 100 bytes memory" > > Which is: "under memory pressure (0.00% used), 100 bytes log > > retention, and flush 100 bytes memory" > > [ FAILED ] > > MaintenanceManagerTest.TestPrioritizeLogRetentionUnderMemoryPressure (1 > ms) > > > > > > > > On Thu, Apr 30, 2020 at 3:51 PM Attila Bukor <[email protected]> wrote: > > > > > +1 > > > > > > Verified the checksum and signature, diffed against the git tag with no > > > differences in source code, built in release mode on el7. > Unfortunately I > > > couldn't get all tests to pass due to disk space issues though. > > > > > > Attila > > > > > > On Wed, Apr 29, 2020 at 02:17:36PM -0500, Grant Henke wrote: > > > > +1 I verified the kudu-binary jar issue I saw in the last RC is > > resolved. > > > > > > > > On Mon, Apr 27, 2020 at 6:32 PM Hao Hao <[email protected] > > > > > > wrote: > > > > > > > > > Hello Kudu devs! > > > > > > > > > > The Apache Kudu team is happy to announce the second release > > candidate > > > for > > > > > Apache Kudu 1.12.0. > > > > > > > > > > Apache Kudu 1.12.0 is a minor release that offers many improvements > > and > > > > > fixes since the prior release. > > > > > > > > > > This is a source-only release. The artifacts have been staged here: > > > > > https://dist.apache.org/repos/dist/dev/kudu/1.12.0-RC2/ > > > > > > > > > > Java convenience binaries in the form of a Maven repository are > > staged > > > > > here: > > > > > > > https://repository.apache.org/content/repositories/orgapachekudu-1062 > > > > > > > > > > Linux and macOS kudu-binary JAR artifacts are staged here > > > correspondingly: > > > > > > > > https://repository.apache.org/content/repositories/orgapachekudu-1063/ > > > > > > > > https://repository.apache.org/content/repositories/orgapachekudu-1064/ > > > > > > > > > > It is tagged in Git as 1.12.0-RC2 and the corresponding hash is the > > > > > following: > > > > > > > > > > > > > > > > https://gitbox.apache.org/repos/asf?p=kudu.git;a=commit;h=80e35e5f9d6a02010ff65ab0e5bd1fc115d190df > > > > > > > > > > The WIP release notes can be found here: > > > > > https://gerrit.cloudera.org/c/15685/ > > > > > > > > > > The KEYS file to verify the artifact signatures can be found here: > > > > > https://dist.apache.org/repos/dist/release/kudu/KEYS > > > > > > > > > > I'd suggest going through the README and 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 Thursday Apr 30 18:00:00 PST 2020. > > > > > > > > > > Best, > > > > > Hao > > > > > > > > > > > > > > > > > -- > > > > Grant Henke > > > > Software Engineer | Cloudera > > > > [email protected] | twitter.com/gchenke | > linkedin.com/in/granthenke > > > > > >
