[ 
https://issues.apache.org/jira/browse/BOOKKEEPER-974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15748671#comment-15748671
 ] 

Enrico Olivelli commented on BOOKKEEPER-974:
--------------------------------------------

I'm trying your image 
{code}
make build
docker run --network host --name some-zookeeper --restart always -d zookeeper
docker run  --network host -e ZK_SERVERS=$(hostname):2181 -it 
caiok/bookkeeper:4.4.0
{code}

I get this error:
{code}
2016-12-14 15:43:41,854 - INFO  - [main:ZooKeeper@438] - Initiating client 
connection, connectString=DNA101PC193.diennea.lan:2181 sessionTimeout=10000 
watcher=org.apache.bookkeeper.zookeeper.ZooKeeperWatcherBase@6aaa5eb0
2016-12-14 15:43:41,872 - INFO  - 
[main-SendThread(dna101pc193.diennea.lan:2181):ClientCnxn$SendThread@975] - 
Opening socket connection to server 
dna101pc193.diennea.lan/10.168.101.193:2181. Will not attempt to authenticate 
using SASL (unknown error)
2016-12-14 15:43:41,913 - INFO  - 
[main-SendThread(dna101pc193.diennea.lan:2181):ClientCnxn$SendThread@852] - 
Socket connection established to dna101pc193.diennea.lan/10.168.101.193:2181, 
initiating session
2016-12-14 15:43:41,929 - INFO  - 
[main-SendThread(dna101pc193.diennea.lan:2181):ClientCnxn$SendThread@1235] - 
Session establishment complete on server 
dna101pc193.diennea.lan/10.168.101.193:2181, sessionid = 0x158fdff2b450000, 
negotiated timeout = 10000
2016-12-14 15:43:41,931 - INFO  - [main-EventThread:ZooKeeperWatcherBase@127] - 
ZooKeeper client is connected now.
2016-12-14 15:43:41,941 - ERROR - [main:Bookie@434] - BookKeeper metadata 
doesn't exist in zookeeper. Has the cluster been initialized? Try running 
bin/bookkeeper shell metaformat
2016-12-14 15:43:41,945 - ERROR - [main:Bookie@391] - Couldn't access cookie in 
zookeeper
org.apache.zookeeper.KeeperException$NoNodeException: KeeperErrorCode = NoNode 
for BookKeeper metadata
        at org.apache.bookkeeper.bookie.Bookie.getInstanceId(Bookie.java:437)
        at org.apache.bookkeeper.bookie.Bookie.checkEnvironment(Bookie.java:346)
        at org.apache.bookkeeper.bookie.Bookie.<init>(Bookie.java:494)
        at 
org.apache.bookkeeper.proto.BookieServer.newBookie(BookieServer.java:110)
        at org.apache.bookkeeper.proto.BookieServer.<init>(BookieServer.java:96)
        at org.apache.bookkeeper.proto.BookieServer.main(BookieServer.java:386)
2016-12-14 15:43:41,947 - ERROR - [main:BookieServer@403] - Exception running 
bookie server : 
org.apache.bookkeeper.bookie.BookieException$InvalidCookieException: 
org.apache.zookeeper.KeeperException$NoNodeException: KeeperErrorCode = NoNode 
for BookKeeper metadata
        at org.apache.bookkeeper.bookie.Bookie.checkEnvironment(Bookie.java:392)
        at org.apache.bookkeeper.bookie.Bookie.<init>(Bookie.java:494)
        at 
org.apache.bookkeeper.proto.BookieServer.newBookie(BookieServer.java:110)
        at org.apache.bookkeeper.proto.BookieServer.<init>(BookieServer.java:96)
        at org.apache.bookkeeper.proto.BookieServer.main(BookieServer.java:386)
Caused by: org.apache.zookeeper.KeeperException$NoNodeException: 
KeeperErrorCode = NoNode for BookKeeper metadata
        at org.apache.bookkeeper.bookie.Bookie.getInstanceId(Bookie.java:437)
        at org.apache.bookkeeper.bookie.Bookie.checkEnvironment(Bookie.java:346)
        ... 4 more

{code}

Some ideas:
- maybe we should mount separate volumes for data/index/journal by default
- maybe we should have a way to pass the configuration file or single 
configuration options
- maybe we should have a way to run the bookkeeper shell


> make pushing a docker image as part of the release procedure
> ------------------------------------------------------------
>
>                 Key: BOOKKEEPER-974
>                 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-974
>             Project: Bookkeeper
>          Issue Type: Improvement
>            Reporter: Jia Zhai
>
> make pushing a docker image as part of the release procedure.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to