frank-montyne edited a comment on issue #10263:
URL: https://github.com/apache/pulsar/issues/10263#issuecomment-853728798


   Example error:
   I have a namespace with one topic. All Producers/consumers are closed. I 
delete the topic (no problem). Then I delete the namespace. When looking in the 
logs from Pulsar 2.7.2 I constantly get the following error while deleting the 
namespace:
   
   10:41:34  PULSAR >08:41:34.550 [pulsar-30-2] ERROR 
org.apache.bookkeeper.mledger.impl.ManagedLedgerImpl - Deleting cursor
   10:41:34  PULSAR 
>org.apache.bookkeeper.mledger.ManagedLedgerException$CursorNotFoundException: 
ManagedCursor not found: reader-8d468b1abe
   10:41:34  PULSAR >08:41:34.550 [pulsar-30-2] WARN  
org.apache.pulsar.broker.service.persistent.PersistentSubscription - 
[persistent://upDownDisk/disk/__change_events] [reader-8d468b1abe] Failed to 
remove non durable cursor
   10:41:34  PULSAR 
>org.apache.bookkeeper.mledger.ManagedLedgerException$CursorNotFoundException: 
ManagedCursor not found: reader-8d468b1abe
   10:41:34  PULSAR >08:41:34.558 [AsyncHttpClient-104-1] WARN  
org.apache.pulsar.client.admin.internal.BaseResource - 
[http://localhost:7650/admin/v2/namespaces/upDownDisk/disk/0x00000000_0x40000000?force=false]
 Failed to perform http delete request: javax.ws.rs.ClientErrorException: HTTP 
409 Conflict
   
   There seems to be a connection internally in 
Pulsar(persistent://upDownDisk/disk/__change_events) to that prevents the 
delete from succeeding.
   When I run the test locally on my MacBook Pro using the Pulsar docker image 
eventually the namespace is deleted after a number of retries. When I run the 
test on Jenkins the delte keeps failing for 90 seconds (=max wait time in the 
back-off strategy) and 91 tries (the delete is retried every second). I already 
tried to use longer wait times between retries it does not help.
   


-- 
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:
[email protected]


Reply via email to