You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by GitBox <gi...@apache.org> on 2022/02/10 18:47:02 UTC

[GitHub] [airflow] jedcunningham commented on issue #21087: KubernetesJobWatcher failing on HTTP 410 errors, jobs stuck in scheduled state

jedcunningham commented on issue #21087:
URL: https://github.com/apache/airflow/issues/21087#issuecomment-1035327244


   It's not that there are too many changes, at least like you are thinking. The executor is trying to watch from (history) revision n, which has rolled off of history on the k8s side. n+2 might be the oldest available now.
   
   This really isn't related to our deployments, and there isn't anything we can do in that regard to help here. In fact, you could hit this when running the scheduler outside k8s even.
   
   More context here: https://github.com/apache/airflow/pull/15500#issuecomment-827885109
   
   Bottom line, especially now that we aren't pinned to `kubernetes==11`, we can probably handle this more gracefully now on our side.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org