Updated f="${HBASE_HOME}/target/cached_classpath.txt" to
f="${HBASE_HOME}/hbase-build-configuration/target/cached_classpath.txt".
Then start hbase success. Anything wrong for my environment?Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-11T00:41:47+08:00) Maven home: /opt/soft/apache-maven-3.3.9 Java version: 1.8.0_131, vendor: Oracle Corporation Java home: /opt/soft/jdk1.8.0_131/jre Default locale: zh_CN, platform encoding: UTF-8 OS name: "linux", version: "3.13.0-46-generic", arch: "amd64", family: "unix" 2017-11-02 15:18 GMT+08:00 Guanghao Zhang <[email protected]>: > Download src and build pass. > But when start-hbase.sh, I found the master can't start in standalone mode. > > ``` > running master, logging to /home/hao/open_source/hbase_ > release/hbase-2.0.0-alpha4/bin/../logs/hbase-hao-master-Xiaohao.out > As this is a development environment, we need /home/hao/open_source/hbase_ > release/hbase-2.0.0-alpha4/bin/../target/cached_classpath.txt to be > generated from maven (command: mvn install -DskipTests) > : running regionserver, logging to /home/hao/open_source/hbase_ > release/hbase-2.0.0-alpha4/bin/../logs/hbase-hao-regionserver-Xiaohao.out > : As this is a development environment, we need > /home/hao/open_source/hbase_release/hbase-2.0.0-alpha4/ > bin/../target/cached_classpath.txt to be generated from maven (command: > mvn install -DskipTests) > ``` > > And I try mvn install -DskipTests, and found the cached_classpath.txt > in hbase-build-configuration/target/cached_classpath.txt. The path is > wrong in bin/hbase. So I update f="${HBASE_HOME}/hbase- > build-configuration/target/cached_classpath.txt" in bin/hbase, then start > master success. File a jira for this? > > 2017-11-02 14:02 GMT+08:00 Stack <[email protected]>: > >> On Wed, Nov 1, 2017 at 9:41 PM, Josh Elser <[email protected]> wrote: >> >> > +1 (binding) >> > >> > * UT's mostly ok. Exceptions being: TestNamespacesInstanceResource, >> > TestReplicaWithCluster, TestReplicationAdmin, and >> TestRegionServerHostname >> > consistently fail for me locally (commented on HBASE-19147) >> > * xsum+sigs OK >> > * can build from source >> > * src archive contents looks OK (exception below) >> > * Built, deployed locally, ran PE without issue >> > >> > >> Excellent. Thanks Josh. >> >> >> >> > I stumbled across src/main/site/resources/repo/o >> > rg/apache/maven/skins/maven-fluido-skin/1.5-HBASE/maven-flui >> do-skin-1.5-HBASE.jar >> > in the source archive which was introduced via >> > https://issues.apache.org/jira/browse/HBASE-14785. Best as I can tell, >> > this was a hack to work around a fluido-skin bug and we should be able >> to >> > remove it now. Not sure if we've already discussed the >> > binary-file-in-src-release concerns of this previously or not... >> > >> > >> Sean noted this in an alpha-3 VOTE. >> >> I came across it yesterday. >> >> What you reckon Misty (if you looking at this?) If you remember, what >> would >> I look for? >> >> Thanks, >> St.Ack >> >> >> >> >> >> > - Josh >> > >> > >> > On 11/1/17 10:17 AM, Stack wrote: >> > >> >> The first release candidate for HBase 2.0.0-alpha4 is up at: >> >> >> >> https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0-alpha4RC0/ >> >> >> >> Maven artifacts are available from a staging directory here: >> >> >> >> https://repository.apache.org/content/repositories/orgapache >> hbase-1178 >> >> >> >> All was signed with my key at 8ACC93D2 [1] >> >> >> >> I tagged the RC as 2.0.0-alpha4RC0 >> >> (5c4b985f89c99cc8b0f8515a4097c811a0848835) >> >> >> >> hbase-2.0.0-alpha4 is our fourth alpha release along our march toward >> >> hbase-2.0.0. It includes all that was in previous alphas (new >> assignment >> >> manager, offheap read/write path, in-memory compactions, etc.), but >> had a >> >> focus on "Coprocessor Fixup": We no longer pass Coprocessors >> >> InterfaceAudience.Private parameters and we cut down on the access and >> >> ability to influence hbase core processing (See [2] on why the radical >> >> changes in Coprocessor Interface). If you are a Coprocessor developer >> or >> >> have Coprocessors to deploy on hbase-2.0.0, we need to hear about your >> >> experience now before we make an hbase-2.0.0 beta. >> >> >> >> hbase-2.0.0-alpha4 is a rough cut ('alpha'), not-for-production >> preview of >> >> what hbase-2.0.0 will look like. It is meant for devs and >> downstreamers to >> >> test drive and flag us early if we messed up anything ahead of our >> rolling >> >> GAs. >> >> >> >> The list of features addressed in 2.0.0 so far can be found here [3]. >> >> There >> >> are thousands. The list of ~2k+ fixes in 2.0.0 exclusively can be found >> >> here [4] (My JIRA JQL foo is a bit dodgy -- forgive me if mistakes). >> >> >> >> I've updated our overview doc. on the state of 2.0.0 [6]. 2.0.0-beta-1 >> >> will >> >> be our next release. Its theme is the "Finishing up 2.0.0" release. >> Here >> >> is >> >> the list of what we have targeted for beta-1 [5]. Check it out. Shout >> if >> >> there is anything missing. We may do a 2.0.0-beta-2 if a need. We'll >> see. >> >> >> >> Please take this alpha for a spin especially if you are a Coprocessor >> >> developer or have a Coprocessor you want to deploy on hbase-2.0.0. >> Please >> >> vote on whether it ok to put out this RC as our first alpha (bar is low >> >> for >> >> an 'alpha' -- e.g. CHANGES.txt has not been updated). Let the VOTE be >> open >> >> for 72 hours (Saturday) >> >> >> >> Thanks, >> >> Your 2.0.0 Release Manager >> >> >> >> 1. http://pgp.mit.edu/pks/lookup?op=get&search=0x9816C7FC8ACC93D2 >> >> 2. Why CPs are Incompatible: >> >> https://docs.google.com/document/d/1WCsVlnHjJeKUcl7wHwqb4z9i >> >> Eu_ktczrlKHK8N4SZzs/edit#heading=h.9k7mjbauv0wj >> >> 3. https://goo.gl/scYjJr >> >> 4. https://goo.gl/tMHkYS >> >> 5. https://issues.apache.org/jira/projects/HBASE/versions/12340861 >> >> 6. >> >> https://docs.google.com/document/d/1WCsVlnHjJeKUcl7wHwqb4z9i >> >> Eu_ktczrlKHK8N4SZzs/ >> >> >> >> >> > >
