sijie opened a new issue #1459: unsubscribe doesn't work if bookkeeper is outage
URL: https://github.com/apache/incubator-pulsar/issues/1459
 
 
   #### Expected behavior
   
   if bookkeeper is outage due to disk fillup, admins want to unsubscribe a 
subscription to clear backlog. the unsubscribe should work.
   
   #### Actual behavior
   
   unsubscribe at ptn level fail with 404.
   unsubscribe at topic level fail with 404.
   unsubscribe at namespace level fail with 500.
   
   NPE is found when unsubscribing a subscription from a namespace.
   
   ```
   Mar 28 01:56:03 ip-10-0-0-19.ec2.internal pulsar[28836]: 01:56:02.961 
[pulsar-web-25-1] INFO  org.apache.pulsar.broker.web.PulsarWebResource - 
Successfully validated clusters on property [benchmark]
   Mar 28 01:56:03 ip-10-0-0-19.ec2.internal pulsar[28836]: 01:56:02.961 
[pulsar-web-25-1] ERROR org.apache.pulsar.broker.admin.impl.NamespacesBase - 
[null] Failed to unsubscribe sub-000 for namespace 
benchmark/local/ns-JQGPJ5A/0xac000000_0xb0000000
   Mar 28 01:56:03 ip-10-0-0-19.ec2.internal pulsar[28836]: 
java.lang.NullPointerException: null
   Mar 28 01:56:03 ip-10-0-0-19.ec2.internal pulsar[28836]: at 
org.apache.pulsar.broker.service.BrokerService.getAllTopicsFromNamespaceBundle(BrokerService.java:1025)
 
~[org.apache.pulsar-pulsar-broker-2.0.0-incubating-SNAPSHOT.jar:2.0.0-incubating-SNAPSHOT]
   Mar 28 01:56:03 ip-10-0-0-19.ec2.internal pulsar[28836]: at 
org.apache.pulsar.broker.admin.impl.NamespacesBase.unsubscribe(NamespacesBase.java:1123)
 
[org.apache.pulsar-pulsar-broker-2.0.0-incubating-SNAPSHOT.jar:2.0.0-incubating-SNAPSHOT]
   Mar 28 01:56:03 ip-10-0-0-19.ec2.internal pulsar[28836]: at 
org.apache.pulsar.broker.admin.impl.NamespacesBase.internalUnsubscribeNamespaceBundle(NamespacesBase.java:965)
 
[org.apache.pulsar-pulsar-broker-2.0.0-incubating-SNAPSHOT.jar:2.0.0-incubating-SNAPSHOT]
   Mar 28 01:56:03 ip-10-0-0-19.ec2.internal pulsar[28836]: at 
org.apache.pulsar.broker.admin.v1.Namespaces.unsubscribeNamespaceBundle(Namespaces.java:684)
 
[org.apache.pulsar-pulsar-broker-2.0.0-incubating-SNAPSHOT.jar:2.0.0-incubating-SNAPSHOT]
   Mar 28 01:56:03 ip-10-0-0-19.ec2.internal pulsar[28836]: at 
sun.reflect.GeneratedMethodAccessor54.invoke(Unknown Source) ~[?:?]
   Mar 28 01:56:03 ip-10-0-0-19.ec2.internal pulsar[28836]: at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 ~[?:1.8.0_161]
   Mar 28 01:56:03 ip-10-0-0-19.ec2.internal pulsar[28836]: at 
java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_161]
   Mar 28 01:56:03 ip-10-0-0-19.ec2.internal pulsar[28836]: at 
org.glassfish.jersey.server.model.internal.ResourceMethodInvocationHandlerFactory$1.invoke(ResourceMethodInvocationHandlerFactory.java:81)
 [org.glassfish.jersey.core-jersey-server-2.25.jar:?]
   Mar 28 01:56:03 ip-10-0-0-19.ec2.internal pulsar[28836]: at 
org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher$1.run(AbstractJavaResourceMethodDispatcher.java:144)
 [org.glassfish.jersey.core-jersey-server-2.25.jar:?]
   Mar 28 01:56:03 ip-10-0-0-19.ec2.internal pulsar[28836]: at 
org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.invoke(AbstractJavaResourceMethodDispatcher.java:161)
 [org.glassfish.jersey.core-jersey-server-2.25.jar:?]
   Mar 28 01:56:03 ip-10-0-0-19.ec2.internal pulsar[28836]: at 
org.glassfish.jersey.server.model.internal.JavaResourceMethodDispatcherProvider$VoidOutInvoker.doDispatch(JavaResourceMethodDispatcherProvider.java:143)
 [org.glassfish.jersey.core-jersey-server-2.25.jar:?]
   Mar 28 01:56:03 ip-10-0-0-19.ec2.internal pulsar[28836]: at 
org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.dispatch(AbstractJavaResourceMethodDispatcher.java:99)
 [org.glassfish.jersey.core-jersey-server-2.25.jar:?]
   Mar 28 01:56:03 ip-10-0-0-19.ec2.internal pulsar[28836]: at 
org.glassfish.jersey.server.model.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:389)
 [org.glassfish.jersey.core-jersey-server-2.25.jar:?]
   Mar 28 01:56:03 ip-10-0-0-19.ec2.internal pulsar[28836]: at 
org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:347)
 [org.glassfish.jersey.core-jersey-server-2.25.jar:?]
   Mar 28 01:56:03 ip-10-0-0-19.ec2.internal pulsar[28836]: at 
org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:102)
 [org.glassfish.jersey.core-jersey-server-2.25.jar:?]
   Mar 28 01:56:03 ip-10-0-0-19.ec2.internal pulsar[28836]: at 
org.glassfish.jersey.server.ServerRuntime$2.run(ServerRuntime.java:326) 
[org.glassfish.jersey.core-jersey-server-2.25.jar:?]
   Mar 28 01:56:03 ip-10-0-0-19.ec2.internal pulsar[28836]: at 
org.glassfish.jersey.internal.Errors$1.call(Errors.java:271) 
[org.glassfish.jersey.core-jersey-common-2.25.jar:?]
   Mar 28 01:56:03 ip-10-0-0-19.ec2.internal pulsar[28836]: at 
org.glassfish.jersey.internal.Errors$1.call(Errors.java:267) 
[org.glassfish.jersey.core-jersey-common-2.25.jar:?]
   Mar 28 01:56:03 ip-10-0-0-19.ec2.internal pulsar[28836]: at 
org.glassfish.jersey.internal.Errors.process(Errors.java:315) 
[org.glassfish.jersey.core-jersey-common-2.25.jar:?]
   Mar 28 01:56:03 ip-10-0-0-19.ec2.internal pulsar[28836]: at 
org.glassfish.jersey.internal.Errors.process(Errors.java:297) 
[org.glassfish.jersey.core-jersey-common-2.25.jar:?]
   Mar 28 01:56:03 ip-10-0-0-19.ec2.internal pulsar[28836]: at 
org.glassfish.jersey.internal.Errors.process(Errors.java:267) 
[org.glassfish.jersey.core-jersey-common-2.25.jar:?]
   Mar 28 01:56:03 ip-10-0-0-19.ec2.internal pulsar[28836]: at 
org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:317)
 [org.glassfish.jersey.core-jersey-common-2.25.jar:?]
   ```
   
   
   #### Steps to reproduce
   
   fill-up the disks to cause bookkeeper outage, and run unsubscribe.
   
   #### System configuration
   **Pulsar version**: master

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


With regards,
Apache Git Services

Reply via email to