**BUG REPORT**
1. Please describe the issue you observed:
- What did you do?
upgrade to use bookkeeper 4.7.2 docker image.
- What did you expect to see?
bookie can start on a new environment.
- What did you see instead?
bookie failed to start.
```
2018-09-06 06:53:51,124 - ERROR - [main:Main@221] - Failed to build bookie
server
org.apache.bookkeeper.bookie.BookieException$MetadataStoreException: Failed to
get cluster instance id
at
org.apache.bookkeeper.discover.ZKRegistrationManager.getClusterInstanceId(ZKRegistrationManager.java:387)
at
org.apache.bookkeeper.bookie.Bookie.checkEnvironmentWithStorageExpansion(Bookie.java:412)
at org.apache.bookkeeper.bookie.Bookie.checkEnvironment(Bookie.java:256)
at org.apache.bookkeeper.bookie.Bookie.<init>(Bookie.java:640)
at
org.apache.bookkeeper.proto.BookieServer.newBookie(BookieServer.java:131)
at
org.apache.bookkeeper.proto.BookieServer.<init>(BookieServer.java:100)
at
org.apache.bookkeeper.server.service.BookieService.<init>(BookieService.java:43)
at org.apache.bookkeeper.server.Main.buildBookieServer(Main.java:299)
at org.apache.bookkeeper.server.Main.doMain(Main.java:219)
at org.apache.bookkeeper.server.Main.main(Main.java:201)
Caused by: org.apache.zookeeper.KeeperException$NoNodeException:
KeeperErrorCode = NoNode for BookKeeper metadata
at
org.apache.bookkeeper.discover.ZKRegistrationManager.getClusterInstanceId(ZKRegistrationManager.java:377)
... 9 more
```
[ Full content available at: https://github.com/apache/bookkeeper/issues/1660 ]
This message was relayed via gitbox.apache.org for [email protected]
