o-nikolas commented on issue #43717:
URL: https://github.com/apache/airflow/issues/43717#issuecomment-2704997436

   > Hi [@o-nikolas](https://github.com/o-nikolas) , thank you for taking a 
look at this.
   > 
   > > Before which logger.info calls did you add sleeps? Was it here?
   > 
   > Sorry, to clarify: I added the sleep to the beginning of my ECS tasks, 
before any of the `logger.info` calls in the task, to confirm that the info 
logs that were not showing up in the Airflow UI were in fact not showing up 
because of how early they were in the task, rather than due to some other 
confounding factor.
   > 
   > > Did you do any testing regarding how long of a sleep was required? Was 
10s the minimum?
   > 
   > I did not -- I was just trying to confirm what I described above, and when 
I saw that a 10 second sleep caused all logs to appear, I took that as 
sufficient evidence of a correlation between a message being logged early in 
the task, and that message not showing up in the Airflow UI, and did not 
experiment further.
   > 
   > > Was this an experiment only, or did you leave this change in place? I.e. 
were you happy to wait longer for full logs?
   > 
   > This was just an experiment; I reverted the sleep addition after 
confirming the connection between logs being early on in the task, and not 
appearing in the UI.
   
   
   Thanks for the info @mjordyn! Can you share a snippet of where you're 
putting the sleep in your ECS task? It sounds like you're putting it at the 
beginning of your task, then your task does it's actual work, then you see the 
logs? Or did you replace the actual work with only a sleep? If you have an 
actual code snipped (or if you could reproduce what change you made) and share 
it, that would be tremendous :)


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

Reply via email to