alkismavridis opened a new issue, #62218:
URL: https://github.com/apache/airflow/issues/62218

   ### Apache Airflow version
   
   Other Airflow 3 version (please specify below)
   
   ### If "Other Airflow 3 version" selected, which one?
   
   3.1.6
   
   ### What happened?
   
   When a task runs for more than 24 hours, celery worker immediately kills it, 
even though the configures JWA token lifetime is a month
   
   ### What you think should happen instead?
   
   The task should continue to run until token is expired. Ideally, a refresh 
procudure should take place.
   
   ### How to reproduce
   
   Use celery executor. Configure api_auth -> jwt_expiration_time to something 
big, such as one month. Run a long running task. The task will be killed at 
exactlz 24 hours.
   
   ### Operating System
   
   Linux via the standard docker-compose file
   
   ### Versions of Apache Airflow Providers
   
   apache-airflow-providers-amazon==9.19.0
   apache-airflow-providers-celery==3.15.0
   apache-airflow-providers-cncf-kubernetes==10.12.0
   apache-airflow-providers-common-compat==1.11.0
   apache-airflow-providers-common-io==1.7.0
   apache-airflow-providers-common-messaging==2.0.1
   apache-airflow-providers-common-sql==1.30.2
   apache-airflow-providers-docker==4.5.1
   apache-airflow-providers-elasticsearch==6.4.2
   apache-airflow-providers-fab==3.1.1
   apache-airflow-providers-ftp==3.14.0
   apache-airflow-providers-git==0.2.0
   apache-airflow-providers-google==19.3.0
   apache-airflow-providers-grpc==3.9.1
   apache-airflow-providers-hashicorp==4.4.1
   apache-airflow-providers-http==5.6.2
   apache-airflow-providers-microsoft-azure==12.10.1
   apache-airflow-providers-mysql==6.4.0
   apache-airflow-providers-odbc==4.11.0
   apache-airflow-providers-openlineage==2.9.2
   apache-airflow-providers-postgres==6.5.1
   apache-airflow-providers-redis==4.4.1
   apache-airflow-providers-sendgrid==4.2.0
   apache-airflow-providers-sftp==5.5.1
   apache-airflow-providers-slack==9.6.1
   apache-airflow-providers-smtp==2.4.1
   apache-airflow-providers-snowflake==6.8.1
   apache-airflow-providers-ssh==4.2.1
   apache-airflow-providers-standard==1.10.2
   
   ### Deployment
   
   Docker-Compose
   
   ### Deployment details
   
   Airflow 3.1.6 (running in docker)
   Celery executor (worker_concurrency=16, worker_autoscale="2,32")
   auth_manager = 
airflow.providers.fab.auth_manager.fab_auth_manager.FabAuthManager
   fab -> auth_backends = 
airflow.providers.fab.auth_manager.api.auth.backend.basic_auth,airflow.providers.fab.auth_manager.api.auth.backend.session
   api_auth -> jwt_expiration_time = 2628000 (1 month)
   api_auth -> jwt_cli_expiration_time = 3600 (1 hour)
   api_auth -> jwt_leeway = 10
   execution_api -> jwt_expiration_time = 600 (10 minutes)
   
   ### Anything else?
   
   Please note I also opened a question on 
[StackOverflow](https://stackoverflow.com/questions/79892224/airflow-task-dies-exactly-24h-after-starting),
 but after second thought, I think it is more appropriate as bug report here. 
Sorry if I am wrong on that one.
   
   ### Are you willing to submit PR?
   
   - [ ] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [x] I agree to follow this project's [Code of 
Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
   


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