+1
Built and ran tests on OS X 10.11.6 using custom version of Kerberos5
suite (1.15.1) and a small patch to adapt krb5 configuration to work on
krb5 1.15.1 (available in the main trunk in
b89dc9a28e7f49a1b429ca0b976643f3b16d1563).
All tests passed except for the delete_tablet-itest, which I think isn't
a blocker.
Best regards,
Alexey
On 4/17/17 4:52 PM, Dan Burkert wrote:
+1
Built and ran tests on OS X 10.10. delete_tablet-itest fails, but it
appears to fail on master as well, all they way back to when it was
introduced about a month ago. Not a blocker IMO.
- Dan
On Mon, Apr 17, 2017 at 4:32 PM, Todd Lipcon <[email protected]> wrote:
+1
Built the release build bits on CentOS 6.8 and CentOS 7.3 (from stock VM
images, following the docs).
Since no read/write path or consensus changes were made since 1.3.0 I
didn't bother rerunning any larger cluster tests or benchmarks. Instead I
focused on more targeted testing of the changes.
Ran release mode tests on both, no unexpected failures (couple timing
flakes due to overloaded VMs but succeeded on retry).
I also ran through the repro steps from KUDU-1968 a couple of times and
verified that no blocks were lost, servers could restart correctly, and
ksck with checksum_scan mode passed.
I also successfully ran RAT as part of building the release tarball.
-Todd
On Thu, Apr 13, 2017 at 2:35 PM, Adar Dembo <[email protected]> wrote:
+1
I downloaded, built on Ubuntu 16.04 for TSAN, and all the C++ tests
passed.
I recently filed KUDU-1975 which is (IMHO) an annoying regression, but
I don't think it should hold up the release.
On Thu, Apr 13, 2017 at 9:09 AM, Jean-Daniel Cryans <[email protected]
wrote:
+1
I downloaded the bits, verified the signature, md5, sha1. Built
everything
on CentOS 6.6 in release mode, ran all the tests, they passed. Same for
Java.
J-D
On Wed, Apr 12, 2017 at 10:15 PM, Todd Lipcon <[email protected]> wrote:
Hi,
The Apache Kudu team is happy to announce the first release candidate
for
Apache Kudu 1.3.1.
Apache Kudu 1.3.1 is a bug fix release which fixes critical issues
discovered in Apache Kudu 1.3.0. Please see the release notes for
details.
The is a source-only release. The artifacts were staged here:
https://dist.apache.org/repos/dist/dev/kudu/1.3.1-RC1/
Java convenience binaries in the form of a Maven repository are staged
here:
https://repository.apache.org/content/repositories/
orgapachekudu-1009/
It was built from this tag:
*https://git-wip-us.apache.org/repos/asf?p=kudu.git;a=commit;h=
afc0f479ba6e04ec84c3c10c55be940c0784c8e1
<https://git-wip-us.apache.org/repos/asf?p=kudu.git;a=commit;h=
afc0f479ba6e04ec84c3c10c55be940c0784c8e1>*
The release notes can be found here:
*https://github.com/apache/kudu/blob/branch-1.3.x/docs/
release_notes.adoc
<https://github.com/apache/kudu/blob/branch-1.3.x/docs/
release_notes.adoc
*
KEYS file:
http://www.apache.org/dist/kudu/KEYS
I'd suggest going through the README, building Kudu, and running the
unit tests. Testing out the Maven repo would also be appreciated.
The vote will run until Monday, April 17th at 6PM PDT (more than the
required minimum 72 hours so folks have three weekdays and don't feel
pressured to vote over the weekend).
Thanks,
Todd
--
Todd Lipcon
Software Engineer, Cloudera
