[GitHub] [pulsar] GBM-tamerm commented on issue #14826: Too many TCP Connections are in CLOSE_WAIT status freeze broker v 2.7.4

[GitBox <gi...@apache.org>]

GBM-tamerm commented on issue #14826:
URL: https://github.com/apache/pulsar/issues/14826#issuecomment-1078832791


   I think i see the potential cause for that , i updated the issue description to reflect more details
   Too many TCP Connections are in CLOSE_WAIT status in a Pulsar broker causing Disconnection Exceptions and Connection Already Close exceptions in pulsar clients
   
   And majority of the close_ wait connections between broker and bookies
   
   Also i can see alof of occurrence of below exception:
   Failed to initialize managed ledger: org.apache.bookkeeper.mledger.ManagedLedgerException$MetadataNotFoundException: Managed ledger not found
   java.util.concurrent.CompletionException: java.util.NoSuchElementException: No value present
           at java.util.concurrent.CompletableFuture.uniExceptionally(CompletableFuture.java:884) ~[?:1.8.0_322]
           at java.util.concurrent.CompletableFuture$UniExceptionally.tryFire(CompletableFuture.java:866) ~[?:1.8.0_322]
           at java.util.concurrent.CompletableFuture.completeExceptionally(CompletableFuture.java:1990) ~[?:1.8.0_322]
   Caused by: java.util.NoSuchElementException: No value present
   


-- 
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: commits-unsubscribe@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org