airflow
airflow copied to clipboard
Reduce log verbosity in KubernetesExecutor.
- Don't log entire executor_config unless it fail. Today, it occupies close to 100 lines on each log entry every time a pod is launched.
- Only log Pending events as debug. The events on Added + Completed should be enough for info level.
- Only log addition to local result_queue on debug level, it is already logged again once the queue is processed which should be enough for operators, assuming the internal state of code is running fine.
- Move log of run_next so that it can include pod name.