awslabs / awslabs/amazon-kinesis-client-nodejs
How to catch KCL error
- Dominant language
- JavaScript
- Stars
- 304
- Forks
- 198
- Avg merge
- 36m
- Merged PRs (30d)
- 2
Description
Hello,
I'm using KCL in nodeJS to send data from kinesis to some other streams in my app (for example websocket), first thing i do is initialiation of websocket connection, i want to be able to close connection when KCL initialization fails or when some errors occurs. Is it possible to register some handler in child process or listening on some message to be notified about errors?
For now i'm using `uncaughtException` to gracefully disable my connections but maybe it is another way ?
Contributor guide
Research direction
Start by tracing KCL initialization and the child-process error and message paths described in the issue, then compare them with the current uncaughtException approach. Determine whether initialization failures and later errors expose a supported notification or handler path, and document or test the connection-cleanup behavior that should result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, node.js
- Domain
- backend, stream-processing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100