Open naveenbussari opened 1 week ago
Hi, the issue may not be directly related to the Bitnami container image/Helm chart, but rather to how the application is being utilized, configured in your specific environment, or tied to a particular scenario that is not easy to reproduce on our side.
If you think that's not the case and want to contribute a solution, we welcome you to create a pull request. The Bitnami team is excited to review your submission and offer feedback. You can find the contributing guidelines here.
Your contribution will greatly benefit the community. Feel free to reach out if you have any questions or need assistance.
Suppose you have any questions about the application, customizing its content, or technology and infrastructure usage. In that case, we highly recommend that you refer to the forums and user guides provided by the project responsible for the application or technology.
With that said, we'll keep this ticket open until the stale bot automatically closes it, in case someone from the community contributes valuable insights.
The issue here seems to be that the webserver doesn't wait long enough before a pod (spark driver pod in this case) changes it's phase from ContainerCreating to Running.
Name and Version
bitnami/airflow:2.6.0
What architecture are you using?
amd64
What steps will reproduce the bug?
What is the expected behavior?
The airflow pod creates a spark application that creates a driver pod. The spark-driver goes through the following stages
pending->ContainerCreating->Running->Completed
. On the airflow UI, the task should fail if the driver pod is in anError
state (or similar states that refer the pod as failed)What do you see instead?
The spark job runs fine. Executor pods are created and spark application is successfully completed. But on the airflow UI, the task is marked as failed. The logs suggest that the driver pod is in 'ContainerCreating' state. But the driver pod state changed from
Pending->ContainerCreating->Running
within a few seconds (around 20).I am attaching the logs.
Additional information
I tried using the configs but it isn't solved.