You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by GitBox <gi...@apache.org> on 2019/06/13 15:59:40 UTC
[GitHub] [pulsar] raulnegrean edited a comment on issue #4162: kubectl
appply -f bookie.yaml andthen Error
raulnegrean edited a comment on issue #4162: kubectl appply -f bookie.yaml andthen Error
URL: https://github.com/apache/pulsar/issues/4162#issuecomment-501762876
@sijie I'm having the exact same issue. As mentioned in the documentation, I'm deploying the zookeeper stateful set first and then, as soon as the pods are up and running, I'm deploying the cluster metadata job. Next, I'm deploying the bookie daemon set, and that's when I'm getting the aforementioned exception:
```
$ kubectl logs bookie-zg92v
...
15:31:12.873 [main-EventThread] INFO org.apache.bookkeeper.zookeeper.ZooKeeperWatcherBase - ZooKeeper client is connected now.
15:31:12.996 [main] INFO org.apache.bookkeeper.proto.BookieNettyServer - Shutting down BookieNettyServer
15:31:13.012 [main] ERROR org.apache.bookkeeper.server.Main - Failed to build bookie server
org.apache.bookkeeper.bookie.BookieException$InvalidCookieException: instanceId 23ba2d60-6136-4300-960f-af622a870ec4 is not matching with c36550e6-a701-4b05-be49-709b0d2654c5
at org.apache.bookkeeper.bookie.Cookie.verifyInternal(Cookie.java:142) ~[org.apache.bookkeeper-bookkeeper-server-4.9.2.jar:4.9.2]
at org.apache.bookkeeper.bookie.Cookie.verify(Cookie.java:147) ~[org.apache.bookkeeper-bookkeeper-server-4.9.2.jar:4.9.2]
at org.apache.bookkeeper.bookie.Bookie.verifyAndGetMissingDirs(Bookie.java:371) ~[org.apache.bookkeeper-bookkeeper-server-4.9.2.jar:4.9.2]
at org.apache.bookkeeper.bookie.Bookie.checkEnvironmentWithStorageExpansion(Bookie.java:434) ~[org.apache.bookkeeper-bookkeeper-server-4.9.2.jar:4.9.2]
at org.apache.bookkeeper.bookie.Bookie.checkEnvironment(Bookie.java:252) ~[org.apache.bookkeeper-bookkeeper-server-4.9.2.jar:4.9.2]
at org.apache.bookkeeper.bookie.Bookie.<init>(Bookie.java:691) ~[org.apache.bookkeeper-bookkeeper-server-4.9.2.jar:4.9.2]
at org.apache.bookkeeper.proto.BookieServer.newBookie(BookieServer.java:137) ~[org.apache.bookkeeper-bookkeeper-server-4.9.2.jar:4.9.2]
at org.apache.bookkeeper.proto.BookieServer.<init>(BookieServer.java:106) ~[org.apache.bookkeeper-bookkeeper-server-4.9.2.jar:4.9.2]
at org.apache.bookkeeper.server.service.BookieService.<init>(BookieService.java:43) ~[org.apache.bookkeeper-bookkeeper-server-4.9.2.jar:4.9.2]
at org.apache.bookkeeper.server.Main.buildBookieServer(Main.java:301) ~[org.apache.bookkeeper-bookkeeper-server-4.9.2.jar:4.9.2]
at org.apache.bookkeeper.server.Main.doMain(Main.java:221) [org.apache.bookkeeper-bookkeeper-server-4.9.2.jar:4.9.2]
at org.apache.bookkeeper.server.Main.main(Main.java:203) [org.apache.bookkeeper-bookkeeper-server-4.9.2.jar:4.9.2]
at org.apache.bookkeeper.proto.BookieServer.main(BookieServer.java:314) [org.apache.bookkeeper-bookkeeper-server-4.9.2.jar:4.9.2]
```
Also, here's a list of all the available resources:
```
$ kubectl get all
NAME READY STATUS RESTARTS AGE
pod/bookie-zg92v 0/1 CrashLoopBackOff 6 8m31s
pod/pulsar-cluster-metadata-init-4ptvl 0/1 Completed 0 8m45s
pod/zk-0 1/1 Running 0 9m20s
pod/zk-1 1/1 Running 0 9m5s
pod/zk-2 1/1 Running 0 8m56s
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
service/bookkeeper ClusterIP None <none> 3181/TCP 8m31s
service/kubernetes ClusterIP 10.96.0.1 <none> 443/TCP 10m
service/zookeeper ClusterIP None <none> 2888/TCP,3888/TCP 9m20s
NAME DESIRED CURRENT READY UP-TO-DATE AVAILABLE NODE SELECTOR AGE
daemonset.apps/bookie 1 1 0 1 0 <none> 8m31s
NAME READY AGE
statefulset.apps/zk 3/3 9m20s
```
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services