This vote will remain open for 72 hours (3 days), until Fri, 2014 May 2 21:30 UTC. (That's 5:30pm EDT on Friday.)
[ ] +1 - I have verified and accept... [ ] +/-0 - I have reservations, but not strong enough to vote against... [ ] -1 - Because..., I do not accept... ... these artifacts as the 1.6.0 release of Apache Accumulo.
* Verified signatures and hashes * Verified source artifact matches given commit (modulo known .gitignore issue) * Ran through ITs with both Hadoop profiles. * I agree previous tests needn't be invalidated by the changes in this RC
-Sean On Tue, Apr 29, 2014 at 4:33 PM, Christopher <[EMAIL PROTECTED]> wrote: Sean
Verified hashes/sigs. Verified commit matches tarball (minus known SCM file .gitignore). Verified bin tarball includes the same sealed jars staged for deploy to maven (minus expected accumulo-maven-plugin's jar, which is deliberately excluded from the binary tarball, as it's only useful in maven). Verified source jars and javadoc jars were built for each regular jar.
Successfully ran full ITs on hadoop 1 and 2 profiles with JDK 1.7/Maven 3.0.4 and JDK 1.6/Maven 3.0.4
Found ACCUMULO-2764, but it's not a blocker for me. Also saw ACCUMULO-2760 in a shared Jenkins during a separate full IT build, but also not a blocker for me.
* Verified proper license notices in place from failed RC4 * Xsums and sigs verified * Ingested and verified 2B entries with CI * Ran UT/IT against 2.4.0
Since no "big" changes since RC3 and RC4, did not more exhaustive tests. Copying high-level tests from old votes:
* Unit and Integration tests passed against 1.2.1, 2.2.0 and 2.3.0 using source tarball * Tested mapreduce via AccumuloStorage with Pig and binary tarball * Performance still on par after previous WAL fix
Verified all signatures and hashes. Verified contents of the source tar - matched git commit, modulo .gitignore file. Verified licence headers on all files, ignoring binary files. Verified unit tests. Verified that native maps build cleanly. Deployed on cluster and ran 4hr CI with agitation.
On Tue, Apr 29, 2014 at 5:33 PM, Christopher <[EMAIL PROTECTED]> wrote:
Verified signatures and hashes. Verified contents of source and binary tarballs via checksums, minus hidden files like .gitignore. Verified unit tests, functional tests (ITs) against default profile. Verified successful ShortEach and LongEach randomwalk. Randomwalk tests on rc4 (ShortEach, LongEach, 24-hr+ LongClean) would also apply here. Cluster: 7 node CDH 4.5, 2 master, 5 tserver, 3 ZK, CentOS 6.4.
On Thu, May 1, 2014 at 10:20 AM, Mike Drob <[EMAIL PROTECTED]> wrote: // Bill Havanki // Solutions Architect, Cloudera Govt Solutions // 443.686.9283
* Verified sigs and hashes * Was able to build Accismus against Staging repo (had to add pluginRepositories section to my maven config in addition to repositories section) * Was able to build native maps from bin.tgz * Ran 24hr CI w/ agitation on 20 node EC2 cluster... 8 billion written & verified.. found ACCUMULO-2768..
Used hadoop 2.2.0 (single non-HA NN) and ZK 3.4.5 (3 zookeepers) for test.
Used 3G native config w/ following changes for CI test.
tserver.mutation.queue.max=4M general.rpc.timeout=180s On Tue, Apr 29, 2014 at 5:33 PM, Christopher <[EMAIL PROTECTED]> wrote:
Verified hashes. I've also been working on Apache Bigtop-style packaging for Accumulo since 1.4.4, and now that Hadoop 2 is supported this will actually work in the Apache Bigtop stack. I've posted a patch to add Accumulo to Bigtop in BIGTOP-1175. I've built those packages from the 1.6.0 RC-5 source and run them on multiple Linux distros against multiple versions of Hadoop and ZooKeeper in psuedo-distributed mode. I was able to perform basic CRUD operations like table creation, inserting rows, deleting cells, etc.. On Thu, May 1, 2014 at 1:27 PM, Keith Turner <[EMAIL PROTECTED]> wrote:
This thread is for voting on an upcoming release, so you may want to download the source Christopher Tubbs posted, and see if you can build it and get Accumulo running. Use JIRA ( https://issues.apache.org/jira/browse/ACCUMULO) to report any bugs or improvements you have, and maybe even submit patches. On Fri, May 2, 2014 at 1:03 PM, Shakil Akhtar <[EMAIL PROTECTED]>wrote:
I've pushed the gpg-signed tag, and dropped the RC branches, and released the maven repo. I've also created a 1.6.1-SNAPSHOT branch, with the changes since RC5 merged in, and merged to master. And, I've pushed the tarballs and signatures to the dist repo for mirroring. (Note: I also fixed the incorrect whitespace in 1.5.1's hashes while I was there, so sha1sum -c and md5sum -c will work correctly). I also updated JIRA, to mark 1.6.0 as released. The date can be changed later, to reflect whatever day we announce it on (Monday?), if we care, but for now, it's the day the release was approved (today).
That's all I can do at the moment. Stuff that still needs to be done: 1. Update the website when Bill Havanki is done with the makeover. 2. Run "javadoc:aggregate" on the tag to generate javadocs for the website (if javadoc 1.6 is used, they need to be patched to address the cross-site scripting vulnerability, but I don't care if they are generated with javadoc 1.7 to make that easier) 3. Do the release announcement. Christopher L Tubbs II http://gravatar.com/ctubbsii On Fri, May 2, 2014 at 6:10 PM, Christopher <[EMAIL PROTECTED]> wrote:
Thanks, Josh. I haven't yet figured out the steps to update those files outside of svn, so I appreciate somebody else doing that. Let me know if you run into issues executing the relevant maven commands.
On Mon, May 5, 2014 at 11:33 AM, Christopher <[EMAIL PROTECTED]> wrote: That would be best for the list of known issues, as long as we properly organize things in jira nicely. We could use tags and or priority in jira to help users find the things they should know about when running 1.6.0. There is a ticket for defining some of this, but right now there is no established way to do this.
The idea w/ the release notes was to cut down on the amount of noise for the user. For example I doubt many users are interested in the agitator bug I found recently that impacts 1.6.0. The main drawback is the list in the release notes will likely become stale over time, where jira will not.
On Fri, May 2, 2014 at 4:15 PM, Joey Echeverria <joey+[EMAIL PROTECTED]>wrote:
I found the root cause of this and filed ACCUMULO-2780
NEW: Monitor These Apps!
Apache Lucene, Apache Solr and all other Apache Software Foundation projects and their respective logos are trademarks of the Apache Software Foundation.
Elasticsearch, Kibana, Logstash, and Beats are trademarks of Elasticsearch BV, registered in the U.S. and in other countries. This site and Sematext Group is in no way affiliated with Elasticsearch BV.
Service operated by Sematext