wolfstudy opened a new issue #2998:
URL: https://github.com/apache/bookkeeper/issues/2998


   **BUG REPORT**
   
   ***Describe the bug***
   
   When we execute the offline command to log off a bookie node from the bookie 
cluster, and execute the command `bookkeeper shell listbookies -all`, the 
following error will be reported:
   
   ```
   11:43:22.453 [main] INFO  
org.apache.bookkeeper.tools.cli.commands.bookies.ListBookiesCommand - All 
Bookies :
   11:43:22.807 [main] INFO  
org.apache.bookkeeper.tools.cli.commands.bookies.ListBookiesCommand - 
BookieID:111.1.7.6:3181, IP:11.1.7.6, Port:3181, Hostname:11.1.7.6
   11:43:23.163 [main] INFO  
org.apache.bookkeeper.tools.cli.commands.bookies.ListBookiesCommand - 
BookieID:11.1.7.6:3181, IP:11.1.7.6, Port:3181, Hostname:11.1.7.6
   11:43:23.275 [main] INFO  org.apache.zookeeper.ZooKeeper - Session: 
0x4047d76054841b5 closed
   11:43:23.275 [main-EventThread] INFO  org.apache.zookeeper.ClientCnxn - 
EventThread shut down for session: 0x4047d76054841b5
   11:43:23.275 [main] ERROR 
org.apache.bookkeeper.tools.cli.helpers.DiscoveryCommand - Fail to process 
command 'list'
   
org.apache.bookkeeper.proto.BookieAddressResolver$BookieIdNotResolvedException: 
Cannot resolve bookieId 2.2.2.8:3181, bookie does not exist or it is not running
           at 
org.apache.bookkeeper.client.DefaultBookieAddressResolver.resolve(DefaultBookieAddressResolver.java:63)
 ~[org.apache.bookkeeper-bookkeeper-server-4.12.0.jar:4.12.0]
           at 
org.apache.bookkeeper.tools.cli.helpers.CommandHelpers.getBookieSocketAddrStringRepresentation(CommandHelpers.java:45)
 ~[org.apache.bookkeeper-bookkeeper-server-4.12.0.jar:4.12.0]
           at 
org.apache.bookkeeper.tools.cli.commands.bookies.ListBookiesCommand.printBookies(ListBookiesCommand.java:124)
 ~[org.apache.bookkeeper-bookkeeper-server-4.12.0.jar:4.12.0]
           at 
org.apache.bookkeeper.tools.cli.commands.bookies.ListBookiesCommand.run(ListBookiesCommand.java:113)
 ~[org.apache.bookkeeper-bookkeeper-server-4.12.0.jar:4.12.0]
           at 
org.apache.bookkeeper.tools.cli.commands.bookies.ListBookiesCommand.run(ListBookiesCommand.java:43)
 ~[org.apache.bookkeeper-bookkeeper-server-4.12.0.jar:4.12.0]
           at 
org.apache.bookkeeper.tools.cli.helpers.DiscoveryCommand.apply(DiscoveryCommand.java:57)
 [org.apache.bookkeeper-bookkeeper-server-4.12.0.jar:4.12.0]
           at 
org.apache.bookkeeper.tools.cli.helpers.ClientCommand.apply(ClientCommand.java:60)
 [org.apache.bookkeeper-bookkeeper-server-4.12.0.jar:4.12.0]
           at 
org.apache.bookkeeper.bookie.BookieShell$ListBookiesCmd.runCmd(BookieShell.java:1202)
 [org.apache.bookkeeper-bookkeeper-server-4.12.0.jar:4.12.0]
           at 
org.apache.bookkeeper.bookie.BookieShell$MyCommand.runCmd(BookieShell.java:236) 
[org.apache.bookkeeper-bookkeeper-server-4.12.0.jar:4.12.0]
           at 
org.apache.bookkeeper.bookie.BookieShell.run(BookieShell.java:2235) 
[org.apache.bookkeeper-bookkeeper-server-4.12.0.jar:4.12.0]
           at 
org.apache.bookkeeper.bookie.BookieShell.main(BookieShell.java:2326) 
[org.apache.bookkeeper-bookkeeper-server-4.12.0.jar:4.12.0]
   Caused by: 
org.apache.bookkeeper.client.BKException$BKBookieHandleNotAvailableException: 
Bookie handle is not available
           at 
org.apache.bookkeeper.discover.ZKRegistrationClient.getBookieServiceInfo(ZKRegistrationClient.java:248)
 ~[org.apache.bookkeeper-bookkeeper-server-4.12.0.jar:4.12.0]
           at 
org.apache.bookkeeper.client.DefaultBookieAddressResolver.resolve(DefaultBookieAddressResolver.java:43)
 ~[org.apache.bookkeeper-bookkeeper-server-4.12.0.jar:4.12.0]
           ... 10 more
   ```
   
   But executing `bookkeeper shell listbookies -rw` and `bookkeeper shell 
listbookies -ro` can output normally, and can also correspond to the list of 
bookie nodes stored in zookeeper.
   
   


-- 
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.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to