vincbeck commented on code in PR #40468:
URL: https://github.com/apache/airflow/pull/40468#discussion_r1663128264
##########
airflow/executors/base_executor.py:
##########
@@ -284,8 +289,11 @@ def trigger_tasks(self, open_slots: int) -> None:
self.log.info("queued but still running; attempt=%s
task=%s", attempt.total_tries, key)
continue
# Otherwise, we give up and remove the task from the queue.
- self.log.error(
- "could not queue task %s (still running after %d
attempts)", key, attempt.total_tries
+ self.task_context_logger.error(
+ "could not queue task %s (still running after %d
attempts)",
Review Comment:
I like this proposal. @RNHTTR, what do you think? TBH @RNHTTR, I have
nothing against writing a section in
[troubleshooting.rst](https://github.com/apache/airflow/blob/main/docs/apache-airflow/troubleshooting.rst)
about this special use case but since I have never encountered this use case I
dont feel strongly confident describing it (since I am not sure how it
happens). Or maybe you could describe it @RNHTTR? That'd be helpful
--
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
