Just curious, has something changed in the LoadBalancer? My own personal balancer was working fine with 2.0.0-b1 but doesn't seems to work anymore with 2.0.0-b2: 2018-03-05 20:33:55,073 ERROR [master/node2:60000] master.HMaster: Failed to become active master java.lang.NoSuchFieldError: clusterStatus at c.c.s.hbase.LoadBasedBalancer.initialize(LoadBasedBalancer.java:42) at org.apache.hadoop.hbase.master.HMaster.finishActiveMasterInitialization(HMaster.java:869) at org.apache.hadoop.hbase.master.HMaster.startActiveMasterManager(HMaster.java:2020) at org.apache.hadoop.hbase.master.HMaster.run(HMaster.java:553) at java.lang.Thread.run(Thread.java:748)
Has the visibility of the clusterStatus field from StochasticLoadBalancer changed between the 2 versions? I'm not good enough at GIT to be able to compare them :( JMS 2018-03-05 16:15 GMT-05:00 Umesh Agashe <[email protected]>: > Thanks Stack! Created HBASE-20135. > > On Mon, Mar 5, 2018 at 11:31 AM, Stack <[email protected]> wrote: > > > Thanks Umesh. File an issue though? Stuff Anoops comment in it. While > > 'harmless', it will scare users; we should fix it. > > Thanks for trying the RC, > > S > > > > On Sun, Mar 4, 2018 at 8:18 PM, Umesh Agashe <[email protected]> > wrote: > > > > > Yes, I started hbase2 over hbase1 when I got the exception. I also > tried > > > running TestReplicationAdmin a couple of times and can not reliably > > > reproduce the problem. > > > > > > I am changing my vote to +1. > > > > > > Thanks, > > > Umesh > > > > > > > > > On Sun, Mar 4, 2018 at 2:43 PM, Stack <[email protected]> wrote: > > > > > > > Thank Umesh for giving it a run. > > > > > > > > Did you start the hbase2 over an hbase1 dataset. I've seen the > > exception > > > > you note when I've done this. The startup keeps going over this > > > exception, > > > > right? (IIRC, its a complaint reading a file written w/ hbase1... We > > fail > > > > to read in the bloom filter which is not the end-of-the-world). > > > > > > > > On the replication failures, you can reproduce reliably? > > > > > > > > Thanks, > > > > St.Ack > > > > > > > > > > > > > > > > On Sun, Mar 4, 2018 at 9:04 AM, Umesh Agashe <[email protected]> > > > wrote: > > > > > > > > > -1 non-binding (concerns noted below) > > > > > > > > > > download src & bin tar ball - OK > > > > > signatures & sums - > OK > > > > > build from source (openjdk version "1.8.0_151") - OK > > > > > rat check > > > - > > > > > OK > > > > > unit tests > > > > - > > > > > NOT OK > > > > > start local instance from bin & CRUD from shell - OK > > > > > LTT write, read1 million rows, 2 cols/row - OK > > > > > Upgrade from 1.4.2 - > OK > > > > > check logs > > > - > > > > > NOT OK > > > > > > > > > > NOTE: > > > > > * Error message in the log is concerning. > > > > > > > > > > Found following exception logged multiple times (~11) in the log: > > > > > ERROR [StoreFileOpenerThread-test_cf-1] > > regionserver.StoreFileReader: > > > > > Error > > > > > reading bloom filter meta for GENERAL_BLOOM_META -- proceeding > > without > > > > > java.io.IOException: Comparator class > > > > > org.apache.hadoop.hbase.KeyValue$RawBytesComparator > > > > > is not instantiable > > > > > at org.apache.hadoop.hbase.io.hfile.FixedFileTrailer. > > > createComp > > > > > arator(FixedFileTrailer.java:628) > > > > > at org.apache.hadoop.hbase.io.hfile.CompoundBloomFilter.< > > > init>( > > > > > CompoundBloomFilter.java:79) > > > > > at org.apache.hadoop.hbase.util.BloomFilterFactory. > > > createFromMe > > > > > ta(BloomFilterFactory.java:104) > > > > > at org.apache.hadoop.hbase.regionserver.StoreFileReader. > > > loadBlo > > > > > omfilter(StoreFileReader.java:479) > > > > > at org.apache.hadoop.hbase.regionserver.HStoreFile.open( > > > HStoreF > > > > > ile.java:425) > > > > > at org.apache.hadoop.hbase.regionserver.HStoreFile. > > > initReader(H > > > > > StoreFile.java:460) > > > > > at org.apache.hadoop.hbase.regionserver.HStore. > > > createStoreFileA > > > > > ndReader(HStore.java:671) > > > > > at org.apache.hadoop.hbase.regionserver.HStore.lambda$ > > > openStore > > > > > Files$0(HStore.java:537) > > > > > at java.util.concurrent.FutureTask.run(FutureTask. > java:266) > > > > > at java.util.concurrent.Executors$RunnableAdapter. > > > call(Executor > > > > > s.java:511) > > > > > at java.util.concurrent.FutureTask.run(FutureTask. > java:266) > > > > > at java.util.concurrent.ThreadPoolExecutor.runWorker( > > > ThreadPool > > > > > Executor.java:1149) > > > > > at java.util.concurrent.ThreadPoolExecutor$Worker.run( > > > ThreadPoo > > > > > lExecutor.java:624) > > > > > at java.lang.Thread.run(Thread.java:748) > > > > > Caused by: java.lang.NullPointerException > > > > > > > > > > > > > > > * Some of the replication UTs failed with message "peer doesn't > > exist" > > > in > > > > > the log > > > > > > > > > > [ERROR] Errors: > > > > > [ERROR] TestReplicationAdmin.testAddPeerWithState:171 » > > > > RetriesExhausted > > > > > Failed after ... > > > > > [ERROR] TestReplicationAdmin.testAppendPeerTableCFs:273 » > > > > > RetriesExhausted Failed afte... > > > > > [ERROR] TestReplicationAdmin.testEnableDisable:247 » > > > RetriesExhausted > > > > > Failed after att... > > > > > [ERROR] TestReplicationAdmin.testPeerBandwidth:763 » > > > RetriesExhausted > > > > > Failed after att... > > > > > [ERROR] TestReplicationAdmin.testPeerClusterKey:779 » > > > RetriesExhausted > > > > > Failed after at... > > > > > [ERROR] TestReplicationAdmin.testPeerConfig:192 » > RetriesExhausted > > > > > Failed > > > > > after attemp... > > > > > [ERROR] TestReplicationAdmin.testPeerConfigConflict:656 » > > > > > RetriesExhausted Failed afte... > > > > > [ERROR] TestReplicationAdmin.testPeerExcludeNamespaces:515 » > > > > > RetriesExhausted Failed a... > > > > > [ERROR] TestReplicationAdmin.testPeerReplicationEndpointImpl:795 > » > > > > > RetriesExhausted Fa... > > > > > [ERROR] TestReplicationAdmin.testSetPeerNamespaces:457 » > > > > > RetriesExhausted > > > > > Failed after... > > > > > [ERROR] TestReplicationAdmin.testSetReplicateAllUserTables:490 » > > > > > RetriesExhausted Fail... > > > > > [INFO] > > > > > [ERROR] Tests run: 1906, Failures: 0, Errors: 11, Skipped: 21 > > > > > > > > > > > > > > > On Fri, Mar 2, 2018 at 3:40 PM, Stack <[email protected]> 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/ > > > > > > > > > > > > > > > > > > > > >
