You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In one case CLB get node atom is consistently returning feed without any entries that is causing IndexError and group trying to converge forever. Generally get errors are transient and get resolved in subsequent cycles. But what if they are not (like this case) and keep causing the group to converge forever? How to detect such errors? After detecting such errors, I am assuming it makes sense to put the group in ERROR with proper reasons. This will require some thinking on structuring the converger since currently only step executions can cause the group to go into ERROR.
The text was updated successfully, but these errors were encountered:
In one case CLB get node atom is consistently returning feed without any entries that is causing
IndexError
and group trying to converge forever. Generally get errors are transient and get resolved in subsequent cycles. But what if they are not (like this case) and keep causing the group to converge forever? How to detect such errors? After detecting such errors, I am assuming it makes sense to put the group in ERROR with proper reasons. This will require some thinking on structuring the converger since currently only step executions can cause the group to go into ERROR.The text was updated successfully, but these errors were encountered: