Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Canary: System.exit(-1) could cause a dirty close on the aggregator's streams topology if something goes wrong after aggregator initialization #1338

Open
sauljabin opened this issue Feb 25, 2025 · 0 comments
Open

Canary: System.exit(-1) could cause a dirty close on the aggregator's streams topology if something goes wrong after aggregator initialization #1338

sauljabin opened this issue Feb 25, 2025 · 0 comments

Comments

@sauljabin
Copy link
Member 

          I'm wondering why we use `System.exit(-1)` here. It could cause a dirty close on the aggregator streams topology if something goes wrong after aggregator initialization.

Originally posted by @eduwercamacaro in #1324 (comment)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@sauljabin