You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by GitBox <gi...@apache.org> on 2022/06/02 07:10:55 UTC

[GitHub] [pulsar] lhotari commented on issue #15885: PIP-163: Pulsar client : Connect Command add `keep_alive_interval`

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

   > What I want to discuss is whether we can optimize this, configure this value only on the client-side, and pass it to the broker through the connect command. The advantage is that the server can cancel this configuration, and multiple clients can configure different values.
   
   I think that this is unnecessary complexity. The broker side keep alive should be kept short enough and that should be independent of the client setting.
   
   There were some bugs that caused the connection to stay open for longs durations. 
   #15382 Closes the connection if a ping or pong message cannot be sent .
   #15366 Fixes a proxy connection leak when inbound connection closes while connecting is in progress
   Both of the above fixes address issues where the symptom is "Producer with name xxx is already connect to topic".
   
   I don't think that we need this PIP at all.
   
   
   
   
   
   


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