-
Notifications
You must be signed in to change notification settings - Fork 16.4k
Remove tenacity on KPO logs inner func consume_logs #35504
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.
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
Remove tenacity on KPO logs inner func consume_logs #35504
Conversation
There are many overlapping layers and strategies of retrying in this area of code. It appears this particular layer may be unnecessary. See discussion starting at apache#31622 (comment).
There are many overlapping layers and strategies of retrying in this area of code. It appears this particular layer may be unnecessary. See discussion starting at apache#31622 (comment).
|
Unfortunately we're seeing periodic failures in our fargate system tests (see the original PR for more explanation here) after this retry was removed. @dstandish are you very opposed to my adding it back in? |
|
Could you share the traceback? |
Sorry this took so long @dstandish! You can see the traceback that we see in the tests (for which Vincent's retry resolved and are now back). There is also some other diagnostic info from the logs included: |
Sorry, which tests? Thanks for posting the traceback i'll have a look |
|
Hmm I see, looking at the traceback, that the error is raised from |
Very good point! Yes I concur, we should try first to increase the number of attempts to see if it solves the issues |
We're still seeing issues in kubernetes based system tests. See context and discussions here: apache#35504
We're still seeing issues in kubernetes based system tests. See context and discussions here: #35504
We're still seeing issues in kubernetes based system tests. See context and discussions here: apache/airflow#35504 GitOrigin-RevId: d78a114aa05bee0e02a09a43056827a03180844a
We're still seeing issues in kubernetes based system tests. See context and discussions here: apache/airflow#35504 GitOrigin-RevId: d78a114aa05bee0e02a09a43056827a03180844a
We're still seeing issues in kubernetes based system tests. See context and discussions here: apache/airflow#35504 GitOrigin-RevId: d78a114aa05bee0e02a09a43056827a03180844a
We're still seeing issues in kubernetes based system tests. See context and discussions here: apache/airflow#35504 GitOrigin-RevId: d78a114aa05bee0e02a09a43056827a03180844a
We're still seeing issues in kubernetes based system tests. See context and discussions here: apache/airflow#35504 GitOrigin-RevId: d78a114aa05bee0e02a09a43056827a03180844a
We're still seeing issues in kubernetes based system tests. See context and discussions here: apache/airflow#35504 GitOrigin-RevId: d78a114aa05bee0e02a09a43056827a03180844a
We're still seeing issues in kubernetes based system tests. See context and discussions here: apache/airflow#35504 GitOrigin-RevId: d78a114aa05bee0e02a09a43056827a03180844a
There are many overlapping layers and strategies of retrying in this area of code. It appears this particular layer may be unnecessary. See discussion starting at #31622 (comment).