I deployed it on 8 nodes, running many different things including MR, RowCounts, compactions, etc. Nothing new. So far so good...
2018-03-06 17:29 GMT-05:00 Stack <st...@duboce.net>: > On Tue, Mar 6, 2018 at 12:52 PM, Peter Somogyi <psomo...@apache.org> > wrote: > > > +1 (non-binding) > > > > - Signature, checksum OK > > - Test suite using 1.8.0_161 OK > > - Build and run from source OK > > - Run from bin tarball OK > > - PE 1M rows OK > > - LTT 1M rows OK > > - Basic operations from shell and Java client OK > > > > One thing I noticed: CHANGES.txt isn't updated, latest information is > about > > 0.93.0 - Unreleased. The 1.4.2 release contains up-to-date CHANGES.txt. > > Will the CHANGES.txt be updated only for the final 2.0.0 release? > > > > Thanks Peter for trying the RC. Yeah, CHANGES.txt needs to be up-to-date > by RC (I tried to note that this had not been done in the head of this > thread 'Note CHANGES has not yet been updated'). > > S > > > > > > > On Tue, Mar 6, 2018 at 10:58 AM, Artem Ervits <artemerv...@gmail.com> > > wrote: > > > > > +1 (non-binding) > > > > > > Hadoop Pseudo-distrbibuted: 2.7.5 > > > $M2_HOME from scratch > > > Apache Maven 3.5.2 (138edd61fd100ec658bfa2d307c43b76940a5d7d; > > > 2017-10-18T07:58:13Z) > > > Maven home: /opt/maven/apache-maven-3.5.2 > > > Java version: 1.8.0_161, vendor: Oracle Corporation > > > Java home: /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.161-0.b14.el7_4. > > > x86_64/jre > > > Default locale: en_US, platform encoding: UTF-8 > > > OS name: "linux", version: "3.10.0-693.11.6.el7.x86_64", arch: "amd64", > > > family: "unix" > > > > > > Binary Release: > > > Java 1M rows: OK > > > LTT 1M rows: OK > > > PE 1M rows: OK > > > MD5: OK > > > > > > hbase shell: OK > > > create, list, scan, count, truncate, disable, drop > > > snapshot, restore_snapshot > > > UI: > > > split: OK > > > merge: OK > > > > > > Source Release: > > > Build with: mvn clean -DskipTests -Dhadoop-two.version=2.7.5 > > > install && mvn clean -DskipTests -Dhadoop-two.version=2.7.5 package > > > assembly:single OK > > > MD5: OK > > > installed and ran from src: OK > > > > > > mvn test -P runSmallTests: NOK (this can be my own environment and I've > > > surfaced this in votes for 1.4.1 and 1.4.2 but failing class is the > same > > > but failure is different. > > > > > > [ESC[1;34mINFOESC[m] Results: > > > [ESC[1;34mINFOESC[m] > > > [ESC[1;31mERRORESC[m] ESC[1;31mFailures: ESC[m > > > [ESC[1;31mERRORESC[m] ESC[1;31m > > > TestSpnegoHttpServer.testAllowedClient:243->Assert. > > > assertEquals:631->Assert.assertEquals:645->Assert. > > > failNotEquals:834->Assert.fail:88 > > > expected:<200> but was:<401>ESC[m > > > [ESC[1;34mINFOESC[m] > > > > > > On Tue, Mar 6, 2018 at 10:57 AM, Josh Elser <els...@apache.org> wrote: > > > > > > > +1 (binding) > > > > > > > > * src release OK > > > > * xsums/sigs OK > > > > * Can build and run from src OK > > > > * Loaded some data locally > > > > > > > > > > > > On 3/2/18 6:40 PM, Stack wrote: > > > > > > > >> The first release candidate for HBase 2.0.0-beta-2 is up at > > > >> > > > >> https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0- > > beta-2.RC0/ > > > >> > > > >> Maven artifacts are available from a staging directory here: > > > >> > > > >> https://repository.apache.org/content/repositories/ > > > orgapachehbase-1199 > > > >> > > > >> All was signed with my key at 8ACC93D2 [1] > > > >> > > > >> I tagged the RC as 2.0.0-beta-2RC0.2 at > > > >> 9e9b347d667e1fc6165c9f8ae5ae7052147e8895 > > > >> > > > >> hbase-2.0.0-beta-2 is a not-for-production preview of hbase-2.0.0. > It > > is > > > >> meant for devs and downstreamers to test drive and flag us if we > > messed > > > up > > > >> on anything ahead of our rolling > > > >> actual 2.0.0 release candidates ("GAs"). > > > >> > > > >> hbase-2.0.0-beta-2 is our second beta release. More than 200 fixes > > have > > > >> gone in since > > > >> beta-1. Unit tests generallly pass when run against hadoop2 and > > > >> hadoop3[5]. > > > >> It includes > > > >> all that was in previous alphas and beta (new assignment manager, > > > offheap > > > >> read/write > > > >> path, in-memory compactions, etc).The list of features addressed in > > > 2.0.0 > > > >> so far can be > > > >> found here [3]. There are thousands. The list of ~3k+ fixes in 2.0.0 > > > >> exclusively can be > > > >> found here [4]. Our overview doc. on the state of 2.0.0 is at [6]. > > > >> > > > >> This beta was supposed to have as its focus rolling upgrade from > > > hbase-1.x > > > >> versions but > > > >> this is work not complete (At this late stage, it is looking like it > > > will > > > >> be a post-2.0.0 project). > > > >> > > > >> This is our last hbase-2.0.0 beta release. Next up, we'll be rolling > > an > > > >> actual 2.0.0 release > > > >> candidate. Look for this in a week or two after beta-2 goes out, > after > > > >> we've done more > > > >> testing and documentation (and we fix issues raised by you all > against > > > >> this > > > >> beta). > > > >> > > > >> One known issue, still unaddressed, is that the User API has not > been > > > >> properly filtered > > > >> so it shows more than just InterfaceAudience Public content > > > (HBASE-19663, > > > >> to be fixed > > > >> by release). > > > >> > > > >> Please take this beta for a spin. Please vote on whether it ok to > put > > > out > > > >> this RC as our second > > > >> beta (Note CHANGES has not yet been updated). Let the VOTE be open > for > > > at > > > >> least 72 hours > > > >> (Lets say Wednesday morning, March 7th). > > > >> > > > >> Thanks, > > > >> Your 2.0.0 Release Manager > > > >> > > > >> 1. http://pgp.mit.edu/pks/lookup?op=get&search=0x9816C7FC8ACC93D2 > > > >> 3. https://goo.gl/scYjJr > > > >> 4. https://goo.gl/dFFT8b > > > >> 5. https://builds.apache.org/job/HBase%20Nightly/job/branch-2/ > > > >> <https://goo.gl/dFFT8b> > > > >> 6. https://docs.google.com/document/d/1WCsVlnHjJeKUcl7wHwqb4 > > > >> z9iEu_ktczrlKHK8N4SZzs/ > > > >> > > > >> > > > > > >
