Closed sotojn closed 2 weeks ago
What are the steps to reproduce?
What is the status of the Teraslice job after one of these failures?
I think this is probably pretty important to resolve.
This may have been resolved in a prior PR. #3756 I'll confirm this by running a job with an intentional parsing error. I'm expecting the process to close with an exit code of 1 and be an error.
I also found this, I believe these issues are the same: https://github.com/terascope/teraslice/issues/3755
This is resolved
When running in
kubernetesV2
with a slicer that throws an error, the pod resource will be marked ascompleted
instead of of anerror
state.Here is the execution pod logs in
kubernetesV2
:Here is the execution pod logs in
kubernetes
mode (same job):I need to find out why it's exiting with a zero status code when this happens and ensure I fail with a status code of 1.