potiuk commented on issue #16025: URL: https://github.com/apache/airflow/issues/16025#issuecomment-855249332
Yeah. I understand that - but I would expect to have some logs generated by the celery failures. They might be either in the logs of airflow - explaining what happened, or in case the celery commands failed at some "resource exhaustion" (memory, disk, sockets .... you name it) celery might simply not be able to print out the reasons (often because of this resource exhaution) that will be seen in airflow logs - but then there might be some indication of problems in container logs or metrics. You do mention some memory issues - which is most likely. I wonder what indication of memory problems you mention? Unfortunately. sometimes you will not see the resource starvation in the container. For example If a process requests big chunk of memory that the container does not have, you will not see the starvation at all - you will simply see the process failing. But then maybe you will see some indication of that in some of the container logs (like information that memory request could not be satisfied or something like that). And memory is just one - most likely - reason. -- 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. For queries about this service, please contact Infrastructure at: [email protected]
