apache / apache/pulsar-client-node
producer times out and closes
- Dominant language
- C++
- Stars
- 164
- Forks
- 98
- PR merge metrics
- No merged PRs in 30d
Description
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
Contributor guide
No contributing guide indexed for this repository
Research direction
No file, test, or entry point is named. Start by reproducing the long-running producer timeout in the NodeJS client and inspect the producer lifecycle and connection handling; done means subsequent event-triggered sends continue working without closing and reopening the connection.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- backend, distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100