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

Monovertex pod terminates with connection error when UDF is in a bad state #2282

Open
yhl25 opened this issue Dec 13, 2024 · 0 comments
Open

Monovertex pod terminates with connection error when UDF is in a bad state #2282

yhl25 opened this issue Dec 13, 2024 · 0 comments
Assignees
@adarsh0728
Labels
bug Something isn't working debuggability
Milestone
1.5

Comments

@yhl25
Copy link
Contributor

yhl25 commented Dec 13, 2024 

ERROR numaflow_core: Application error running monovertex: Connection("Failed to connect: tonic::transport::Error(Transport, ConnectError(Os { code: 2, kind: NotFound, message: \"No such file or directory\" }))")

Numa container should always terminate with the appropriate error message showcasing the reason for the udf crash.
@yhl25 yhl25 added the bug Something isn't working label Dec 13, 2024
@yhl25 yhl25 added this to the 1.5 milestone Dec 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@adarsh0728 adarsh0728

Labels
bug Something isn't working debuggability
Projects
None yet
Milestone
1.5
Development

No branches or pull requests
2 participants
@adarsh0728 @yhl25