You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pulsar.apache.org by GitBox <gi...@apache.org> on 2020/07/13 21:42:24 UTC

[GitHub] [pulsar-client-node] dludwig opened a new issue #104: producer times out and closes

dludwig opened a new issue #104:
URL: https://github.com/apache/pulsar-client-node/issues/104


   Hello
   
   My use case is for a long running system that produces messages by event triggers (think something like a web server that produces data for pulsar on HTTP events)
   
   I find this works ok for a brief period of time, but then the producer times out and subsequent events then fail to get sent to pulsar
   
   my work around is to open the connection, use the producer to send the data to pulsar, then close the connection every time -- this seems like a waste of time connecting/disconnecting 
   
   is there a way (or can there be a way) to make the producer connection long lasting? or auto-reconnecting?
   
   thanks
   


----------------------------------------------------------------
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:
users@infra.apache.org

[GitHub] [pulsar-client-node] sijie commented on issue #104: producer times out and closes

Posted by GitBox <gi...@apache.org>.
sijie commented on issue #104:
URL: https://github.com/apache/pulsar-client-node/issues/104#issuecomment-658537375


   It can happen if the publish time increase (broker not ack in time). Also if the volume of traffic produced by your client increases, you need to consider increasing the setting as well.  Since I don't have any visibility in your environment, it is hard for me to tell. I'd recommend you check your cluster to understand if there are any changes related to publishing latency or traffic patterns.


----------------------------------------------------------------
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:
users@infra.apache.org

[GitHub] [pulsar-client-node] sijie commented on issue #104: producer times out and closes

Posted by GitBox <gi...@apache.org>.
sijie commented on issue #104:
URL: https://github.com/apache/pulsar-client-node/issues/104#issuecomment-657914568


   @dludwig Timeout can happen if the maxPendingMessages is set to be too small. You can consider increasing the `maxPendingMessages` value when creating a producer.


----------------------------------------------------------------
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:
users@infra.apache.org

[GitHub] [pulsar-client-node] cavanaug commented on issue #104: producer times out and closes

Posted by GitBox <gi...@apache.org>.
cavanaug commented on issue #104:
URL: https://github.com/apache/pulsar-client-node/issues/104#issuecomment-658501638


   @sijie is this because of a scaling or problem at the broker not ack()ing in time??   Or is this configuration something that needs to be scaled up as the size/volume of data increases?
   
   Im a little nervous to just start growing something like maxPendingMessages without understanding why the max is being reached?


----------------------------------------------------------------
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:
users@infra.apache.org