lhotari commented on issue #15630:
URL: https://github.com/apache/pulsar/issues/15630#issuecomment-1129049113

   @gaozhangmin I cannot reproduce the issue.
   
   I do get the `Namespace 'default' is not found` in logs, but the namepsace 
is successfully created.
   ```
   2022-05-17T18:57:56,155+0300 [client-scheduler-OrderedScheduler-23-0] ERROR 
org.apache.bookkeeper.clients.impl.internal.RootRangeClientImplWithRetries - 
Reason for the failure 
   org.apache.bookkeeper.clients.exceptions.NamespaceNotFoundException: 
Namespace 'default' is not found
        at 
org.apache.bookkeeper.clients.impl.internal.ProtocolInternalUtils.createRootRangeException(ProtocolInternalUtils.java:97)
 ~[stream-storage-java-client-base-4.15.0.jar:4.15.0]
        at 
org.apache.bookkeeper.clients.impl.internal.RootRangeClientImpl.processGetNamespaceResponse(RootRangeClientImpl.java:167)
 ~[stream-storage-java-client-base-4.15.0.jar:4.15.0]
        at 
org.apache.bookkeeper.clients.impl.internal.RootRangeClientImpl.lambda$getNamespace$10(RootRangeClientImpl.java:156)
 ~[stream-storage-java-client-base-4.15.0.jar:4.15.0]
        at 
org.apache.bookkeeper.clients.utils.RpcUtils$1.onSuccess(RpcUtils.java:79) 
~[stream-storage-java-client-base-4.15.0.jar:4.15.0]
        at 
com.google.common.util.concurrent.Futures$CallbackListener.run(Futures.java:1139)
 ~[guava-31.0.1-jre.jar:?]
        at 
com.google.common.util.concurrent.DirectExecutor.execute(DirectExecutor.java:31)
 ~[guava-31.0.1-jre.jar:?]
        at 
com.google.common.util.concurrent.AbstractFuture.executeListener(AbstractFuture.java:1277)
 ~[guava-31.0.1-jre.jar:?]
        at 
com.google.common.util.concurrent.AbstractFuture.complete(AbstractFuture.java:1038)
 ~[guava-31.0.1-jre.jar:?]
        at 
com.google.common.util.concurrent.AbstractFuture.set(AbstractFuture.java:783) 
~[guava-31.0.1-jre.jar:?]
        at io.grpc.stub.ClientCalls$GrpcFuture.set(ClientCalls.java:558) 
~[grpc-stub-1.45.1.jar:1.45.1]
        at 
io.grpc.stub.ClientCalls$UnaryStreamToFuture.onClose(ClientCalls.java:531) 
~[grpc-stub-1.45.1.jar:1.45.1]
        at 
io.grpc.internal.ClientCallImpl.closeObserver(ClientCallImpl.java:562) 
~[grpc-core-1.45.1.jar:1.45.1]
        at io.grpc.internal.ClientCallImpl.access$300(ClientCallImpl.java:70) 
~[grpc-core-1.45.1.jar:1.45.1]
        at 
io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl$1StreamClosed.runInternal(ClientCallImpl.java:743)
 ~[grpc-core-1.45.1.jar:1.45.1]
        at 
io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl$1StreamClosed.runInContext(ClientCallImpl.java:722)
 ~[grpc-core-1.45.1.jar:1.45.1]
        at io.grpc.internal.ContextRunnable.run(ContextRunnable.java:37) 
~[grpc-core-1.45.1.jar:1.45.1]
        at 
io.grpc.internal.SerializingExecutor.run(SerializingExecutor.java:133) 
~[grpc-core-1.45.1.jar:1.45.1]
        at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) 
~[?:?]
        at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) 
~[?:?]
        at java.lang.Thread.run(Thread.java:833) [?:?]
   2022-05-17T18:57:56,155+0300 [main] INFO  
org.apache.pulsar.zookeeper.LocalBookkeeperEnsemble - Creating default namespace
   2022-05-17T18:57:56,189+0300 [main] INFO  
org.apache.pulsar.zookeeper.LocalBookkeeperEnsemble - Successfully created 
'default' namespace :
   namespace_name: "default"
   default_stream_conf {
     key_type: HASH
     min_num_ranges: 24
     initial_num_ranges: 24
     split_policy {
       fixed_range_policy {
         num_ranges: 2
       }
     }
     rolling_policy {
       size_policy {
         max_segment_size: 134217728
       }
     }
     retention_policy {
       time_policy {
         retention_minutes: -1
       }
     }
   }
   ```
   
   What are the steps to reproduce in your case? Can you reproduce if you 
remove the `data` directory?


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