[GitHub] [airflow] potiuk commented on pull request #22588: Print configuration on scheduler startup.

[GitBox <gi...@apache.org>]

potiuk commented on PR #22588:
URL: https://github.com/apache/airflow/pull/22588#issuecomment-1146439534

   Just as further "real life" example (yes I know I am pretty stubborn and persisten)
   
   From https://apache-airflow.slack.com/archives/CCQ7EGB1P/p1654267866780949
   
   I literally wildely guessed that the user has wrongly set their config. They did not even used systemd but their own helm chart. And despite all the evidence (config variables were OK) I based my assumptions on "16" being default value for the "max_tasks_per_dagrun" value that the configuration is wrongly applied.
   
   <img width="880" alt="Screenshot 2022-06-04 at 00 58 11" src="https://user-images.githubusercontent.com/595491/171964605-d50ef4f6-a4e6-4ec1-a5bf-86df1877e3a4.png">
   
   This was a wild guess and a leap of faith. If we print configuration in Airflow logs, I would not have to guess and make very bold statements, I would just have to ask the user to send me the logs.
   
   The "You are right! Thank you" is a bitter-sweet for me. On one hand feels good I could help our user on the other I feel bad that I know we have no good way to diagnose similar issues and we will have to revert to "leap of faith" rather than real data   multiple times in the future when others will have similar problems.
    
   If that does not convince you @kaxil @ash then I am a bit lost why we are opposing it. This is extremely low effort, extremely low overhead and yet (by opposing it) we managed to make somoene who wanted to contribute it to abandon the idea as they saw "no consensus". 
   
   


-- 
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