Open nagarajatantry opened 5 months ago
This is because of the stale messages in the ISB. I am assuming that the error count should have spiked up and alerted the user. We should think of a better user experience?
this was in a nonprod environment with very low tps, so it would have been difficult to catch with an alert. We may need a better way to detect from the platform perspective since the id
field is managed internally by the platform
Update numaflow controller from
rc1
torc4
. I see this error message in the sink vertex. Sink Pods remained in Running State.Error in numa container
error in custom sink container