Hey Mujtaba,
I was able to get it working. I think the addition of HBASE_HOME and
changing the way my entrypoint scripts in my docker container were being
called helped solved the issue.
Thanks again!
On 31/03/2016 11:38 PM, Mujtaba Chohan wrote:
Shouldn't be a bug there as it has been
Shouldn't be a bug there as it has been working in our environment. To
verify can you please try this? Copy only tephra and tephra-env.sh files
supplied with Phoenix in a new directory with HBASE_HOME env variable set
and then run tephra.
Thanks,
Mujtaba
On Wed, Mar 30, 2016 at 9:59 PM, F21
I just downloaded the tephra 0.7.0 from github and extracted it into the
container.
Using the same setup as before, I ran:
export HBASE_CP=/opt/hbase/lib
export HBASE_HOME=/opt/hbase
Running the standalone tephra using ./tephra start worked correctly and
it was able to become the leader.
Do
I think that might be from the tephra start up script.
The folder /opt/hbase/phoenix-assembly/ does not exist on my system.
On 31/03/2016 11:53 AM, Mujtaba Chohan wrote:
I still see you have the following on classpath:
opt/hbase/phoenix-assembly/target/*
On Wed, Mar 30, 2016 at 5:42 PM, F21
I still see you have the following on classpath:
opt/hbase/phoenix-assembly/target/*
On Wed, Mar 30, 2016 at 5:42 PM, F21 wrote:
> Thanks for the hints.
>
> If I remove the client jar, it complains about a missing class:
> 2016-03-31 00:38:25,929 INFO [main]
You definitely need hbase.zookeeper.quorum set to be able to
connect. I think what's happening is since you have phoenix client jar on
classpath (which is not needed as hbase/lib/* + phoenix-server.jar on
classpath should contain all the necessary libraries) contains guava v13
classes bundled
I removed the following from hbase-site.xml and tephra started correctly:
hbase.zookeeper.quorum
f826338-zookeeper.f826338
However, it now keeps trying to connect to zookeeper on localhost, which
wouldn't work, because my zookeeper is on another host:
2016-03-31 00:06:21,972
Hey Mujtaba,
Thanks for the hints. I noticed that I still needed the client jar for
the phoenix server in order to get it to run.
I also checked out the tephra log and this is what I have:
Wed Mar 30 23:50:38 UTC 2016 Starting tephra service on
f826338-hmaster1.f826338
time(seconds)
Few pointers:
- phoenix-core-*.jar is a subset of phoenix-*-server.jar so just
phoenix-*-server.jar in hbase/lib is enough for region servers and master.
- phoenix-server-*-runnable.jar and phoenix-*-server.jar should be enough
for query server. Client jar would only duplicate HBase classes in