You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "alkismavridis (via GitHub)" <gi...@apache.org> on 2026/02/20 11:51:31 UTC
[I] Celery Worker does not respect JWA expiration times - kills tasks prematurely [airflow]
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: commits-unsubscribe@airflow.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Celery Worker does not respect JWA expiration times - kills tasks prematurely [airflow]
Posted by "vincbeck (via GitHub)" <gi...@apache.org>.
vincbeck commented on issue #62218:
URL: https://github.com/apache/airflow/issues/62218#issuecomment-3935271549
I do not think this is an issue. The executor does not use the config section `api_auth` but `execution_api`. So please update this config: https://airflow.apache.org/docs/apache-airflow/stable/configurations-ref.html#config-execution-api-jwt-expiration-time. If you think the documentation is misleading about it, could you please create a PR to update the doc?
--
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
Re: [I] Celery Worker does not respect JWA expiration times - kills tasks prematurely [airflow]
Posted by "alkismavridis (via GitHub)" <gi...@apache.org>.
alkismavridis commented on issue #62218:
URL: https://github.com/apache/airflow/issues/62218#issuecomment-3949457734
@amog I mean that the tasks runs fine for 24h and gets killed precisely at the 24th hour (plus some seconds). So whatever the “kill switch” is, it happens exactly at 24h(plus some seconds) after the task start. When this happens, the logs look like the ones I posted above.
--
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
Re: [I] Celery Worker does not respect JWA expiration times - kills tasks prematurely [airflow]
Posted by "alkismavridis (via GitHub)" <gi...@apache.org>.
alkismavridis commented on issue #62218:
URL: https://github.com/apache/airflow/issues/62218#issuecomment-3943147252
@ashb sorry I forgot to add them. Here they are. This is the moment that the task dies. This happens consistently at exactly 24h after starting.
```
[2026-02-19T12:10:34.423556Z] {celery_executor_utils.py:154} INFO - [a6915c74-3b86-46df-a0f2-2bd3848a98f4] Executing workload in Celery: token='eyJ***' ti=TaskInstance(id=UUID('019c70a7-fb7c-7480-84d0-7232151770ed'), dag_version_id=UUID('019c4721-09cb-7d79-8402-e3925d3ab5b2'), task_id='mt68-gbr-crawler', dag_id='selbstaendige-gbr-crawler', run_id='manual__2026-02-18T12:09:40+00:00', try_number=1, map_index=-1, pool_slots=1, queue='default', priority_weight=1, executor_config=None, parent_context_carrier={}, context_carrier={}) dag_rel_path=PurePosixPath('selbstaendige/gbr_crawler.py') bundle_info=BundleInfo(name='dags-folder', version=None) log_path='dag_id=selbstaendige-gbr-crawler/run_id=manual__2026-02-18T12:09:40+00:00/task_id=mt68-gbr-crawler/attempt=1.log' type='ExecuteTask'
[2026-02-19T12:10:34.425926Z] {supervisor.py:1975} INFO - Secrets backends loaded for worker count=1 backend_classes=['EnvironmentVariablesBackend']
[2026-02-19T12:10:34.448869Z] {supervisor.py:710} INFO - Process exited pid=123088 exit_code=-9 signal_sent=SIGKILL
[2026-02-19T12:10:34.462386Z] {trace.py:285} ERROR - Task execute_workload[a6915c74-3b86-46df-a0f2-2bd3848a98f4] raised unexpected: ServerResponseError('Invalid auth token: Signature has expired')
Traceback (most recent call last):
File "/home/airflow/.local/lib/python3.12/site-packages/celery/app/trace.py", line 479, in trace_task
R = retval = fun(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^
File "/home/airflow/.local/lib/python3.12/site-packages/celery/app/trace.py", line 779, in __protected_call__
return self.run(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/airflow/.local/lib/python3.12/site-packages/airflow/providers/celery/executors/celery_executor_utils.py", line 162, in execute_workload
supervise(
File "/home/airflow/.local/lib/python3.12/site-packages/airflow/sdk/execution_time/supervisor.py", line 1984, in supervise
process = ActivitySubprocess.start(
^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/airflow/.local/lib/python3.12/site-packages/airflow/sdk/execution_time/supervisor.py", line 955, in start
proc._on_child_started(ti=what, dag_rel_path=dag_rel_path, bundle_info=bundle_info)
File "/home/airflow/.local/lib/python3.12/site-packages/airflow/sdk/execution_time/supervisor.py", line 966, in _on_child_started
ti_context = self.client.task_instances.start(ti.id, self.pid, start_date)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/airflow/.local/lib/python3.12/site-packages/airflow/sdk/api/client.py", line 215, in start
resp = self.client.patch(f"task-instances/{id}/run", content=body.model_dump_json())
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/airflow/.local/lib/python3.12/site-packages/httpx/_client.py", line 1218, in patch
return self.request(
^^^^^^^^^^^^^
File "/home/airflow/.local/lib/python3.12/site-packages/tenacity/__init__.py", line 338, in wrapped_f
return copy(f, *args, **kw)
^^^^^^^^^^^^^^^^^^^^
File "/home/airflow/.local/lib/python3.12/site-packages/tenacity/__init__.py", line 477, in __call__
do = self.iter(retry_state=retry_state)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/airflow/.local/lib/python3.12/site-packages/tenacity/__init__.py", line 378, in iter
result = action(retry_state)
^^^^^^^^^^^^^^^^^^^
File "/home/airflow/.local/lib/python3.12/site-packages/tenacity/__init__.py", line 400, in <lambda>
self._add_action_func(lambda rs: rs.outcome.result())
^^^^^^^^^^^^^^^^^^^
File "/usr/python/lib/python3.12/concurrent/futures/_base.py", line 449, in result
return self.__get_result()
^^^^^^^^^^^^^^^^^^^
File "/usr/python/lib/python3.12/concurrent/futures/_base.py", line 401, in __get_result
raise self._exception
File "/home/airflow/.local/lib/python3.12/site-packages/tenacity/__init__.py", line 480, in __call__
result = fn(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^
File "/home/airflow/.local/lib/python3.12/site-packages/airflow/sdk/api/client.py", line 887, in request
return super().request(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/airflow/.local/lib/python3.12/site-packages/httpx/_client.py", line 825, in request
return self.send(request, auth=auth, follow_redirects=follow_redirects)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/airflow/.local/lib/python3.12/site-packages/httpx/_client.py", line 914, in send
response = self._send_handling_auth(
^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/airflow/.local/lib/python3.12/site-packages/httpx/_client.py", line 942, in _send_handling_auth
response = self._send_handling_redirects(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/airflow/.local/lib/python3.12/site-packages/httpx/_client.py", line 999, in _send_handling_redirects
raise exc
File "/home/airflow/.local/lib/python3.12/site-packages/httpx/_client.py", line 982, in _send_handling_redirects
hook(response)
File "/home/airflow/.local/lib/python3.12/site-packages/airflow/sdk/api/client.py", line 186, in raise_on_4xx_5xx_with_note
return get_json_error(response) or response.raise_for_status()
^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/airflow/.local/lib/python3.12/site-packages/airflow/sdk/api/client.py", line 176, in get_json_error
raise err
airflow.sdk.api.client.ServerResponseError: Invalid auth token: Signature has expired
Correlation-id=019c75cf-2041-7fc7-a554-970c6a610cb3
INFO: 172.25.0.5:52116 - "GET /log/dag_id%3Dselbstaendige-gbr-crawler/run_id%3Dmanual__2026-02-18T12%3A09%3A40%2B00%3A00/task_id%3Dmt68-gbr-crawler/attempt%3D1.log HTTP/1.1" 200 OK
[2026-02-19T12:10:36.186345Z] {supervisor.py:1115} ERROR - Server indicated the task shouldn't be running anymore detail={'detail': {'reason': 'not_running', 'message': 'TI is no longer in the running state and task should terminate', 'current_state': 'failed'}} status_code=409 ti_id=UUID('019c70a7-fb7c-7480-84d0-7232151770ed')
[2026-02-19T12:10:41.192109Z] {supervisor.py:718} WARNING - Process did not terminate in time; escalating pid=3873 signal=SIGTERM
[2026-02-19T12:10:41.201091Z] {supervisor.py:710} INFO - Process exited pid=3873 exit_code=-9 signal_sent=SIGKILL
```
--
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
Re: [I] Celery Worker does not respect JWA expiration times - kills tasks prematurely [airflow]
Posted by "amoghrajesh (via GitHub)" <gi...@apache.org>.
amoghrajesh commented on issue #62218:
URL: https://github.com/apache/airflow/issues/62218#issuecomment-3949403999
@alkismavridis just to add some more context, Airflow issues a token to a "workload" or a "task" at startup (when it is ready to move to worker) and that validity is 10 mins. If it doesn't go into the worker in that period, it is possible that the token was invalid in the first place when the worker started executing the task.
As per your last comment, when you say it is reproducible in 24h, what. do you mean?
--
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
Re: [I] Celery Worker does not respect JWA expiration times - kills tasks prematurely [airflow]
Posted by "alkismavridis (via GitHub)" <gi...@apache.org>.
alkismavridis commented on issue #62218:
URL: https://github.com/apache/airflow/issues/62218#issuecomment-3984223571
It worked! 🎉
I increased the `celery_broker_transport_options -> visibility_timeout` to 1 Month and the tasks are now not killed.
Open questions ❓
- Still unsure why my tasks were being killed at exactly 24h. According to the docs , the default value of `celery_broker_transport_options -> visibility_timeout` was 1h, not 24h.
- Also, unsure why increasing the value of `execution_api -> jwt_expiration_time ` did not work.
--
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
Re: [I] Celery Worker does not respect JWA expiration times - kills tasks prematurely [airflow]
Posted by "eladkal (via GitHub)" <gi...@apache.org>.
eladkal commented on issue #62218:
URL: https://github.com/apache/airflow/issues/62218#issuecomment-3984329530
> Still unsure why my tasks were being killed at exactly 24h. According to the docs , the default value of celery_broker_transport_options -> visibility_timeout was 1h, not 24h.
I tend to say this is a question for Celery project or at least for thier consult on the issue
https://github.com/celery/celery
cc @auvipy
--
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
Re: [I] Celery Worker does not respect JWA expiration times - kills tasks prematurely [airflow]
Posted by "potiuk (via GitHub)" <gi...@apache.org>.
potiuk closed issue #62218: Celery Worker does not respect JWA expiration times - kills tasks prematurely
URL: https://github.com/apache/airflow/issues/62218
--
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
Re: [I] Celery Worker does not respect JWA expiration times - kills tasks prematurely [airflow]
Posted by "alkismavridis (via GitHub)" <gi...@apache.org>.
alkismavridis commented on issue #62218:
URL: https://github.com/apache/airflow/issues/62218#issuecomment-3952161418
UPDATE:
As mentioned, I tried to increase the `execution_api -> jwt_expiration_time` to one month.
I now get different error message (Progress!!). So the change seem to have worked. Now the message does not speak of expired token but of "server error". It is possible that this is due to our firewall (my long-running is and SSH operator).
```
[2026-02-24T09:55:26.173901Z] {trace.py:285} ERROR - Task execute_workload[8fd73cf1-4e1a-441d-8f4d-156a70e4b85a] raised unexpected: ServerResponseError('Server returned error')
Traceback (most recent call last):
File "/home/airflow/.local/lib/python3.12/site-packages/celery/app/trace.py", line 479, in trace_task
R = retval = fun(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^
File "/home/airflow/.local/lib/python3.12/site-packages/celery/app/trace.py", line 779, in __protected_call__
return self.run(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/airflow/.local/lib/python3.12/site-packages/airflow/providers/celery/executors/celery_executor_utils.py", line 162, in execute_workload
supervise(
File "/home/airflow/.local/lib/python3.12/site-packages/airflow/sdk/execution_time/supervisor.py", line 1984, in supervise
process = ActivitySubprocess.start(
^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/airflow/.local/lib/python3.12/site-packages/airflow/sdk/execution_time/supervisor.py", line 955, in start
proc._on_child_started(ti=what, dag_rel_path=dag_rel_path, bundle_info=bundle_info)
File "/home/airflow/.local/lib/python3.12/site-packages/airflow/sdk/execution_time/supervisor.py", line 966, in _on_child_started
ti_context = self.client.task_instances.start(ti.id, self.pid, start_date)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/airflow/.local/lib/python3.12/site-packages/airflow/sdk/api/client.py", line 215, in start
resp = self.client.patch(f"task-instances/{id}/run", content=body.model_dump_json())
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/airflow/.local/lib/python3.12/site-packages/httpx/_client.py", line 1218, in patch
return self.request(
^^^^^^^^^^^^^
File "/home/airflow/.local/lib/python3.12/site-packages/tenacity/__init__.py", line 338, in wrapped_f
return copy(f, *args, **kw)
^^^^^^^^^^^^^^^^^^^^
File "/home/airflow/.local/lib/python3.12/site-packages/tenacity/__init__.py", line 477, in __call__
do = self.iter(retry_state=retry_state)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/airflow/.local/lib/python3.12/site-packages/tenacity/__init__.py", line 378, in iter
result = action(retry_state)
^^^^^^^^^^^^^^^^^^^
File "/home/airflow/.local/lib/python3.12/site-packages/tenacity/__init__.py", line 400, in <lambda>
self._add_action_func(lambda rs: rs.outcome.result())
^^^^^^^^^^^^^^^^^^^
File "/usr/python/lib/python3.12/concurrent/futures/_base.py", line 449, in result
return self.__get_result()
^^^^^^^^^^^^^^^^^^^
File "/usr/python/lib/python3.12/concurrent/futures/_base.py", line 401, in __get_result
raise self._exception
File "/home/airflow/.local/lib/python3.12/site-packages/tenacity/__init__.py", line 480, in __call__
result = fn(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^
File "/home/airflow/.local/lib/python3.12/site-packages/airflow/sdk/api/client.py", line 887, in request
return super().request(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/airflow/.local/lib/python3.12/site-packages/httpx/_client.py", line 825, in request
return self.send(request, auth=auth, follow_redirects=follow_redirects)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/airflow/.local/lib/python3.12/site-packages/httpx/_client.py", line 914, in send
response = self._send_handling_auth(
^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/airflow/.local/lib/python3.12/site-packages/httpx/_client.py", line 942, in _send_handling_auth
response = self._send_handling_redirects(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/airflow/.local/lib/python3.12/site-packages/httpx/_client.py", line 999, in _send_handling_redirects
raise exc
File "/home/airflow/.local/lib/python3.12/site-packages/httpx/_client.py", line 982, in _send_handling_redirects
hook(response)
File "/home/airflow/.local/lib/python3.12/site-packages/airflow/sdk/api/client.py", line 186, in raise_on_4xx_5xx_with_note
return get_json_error(response) or response.raise_for_status()
^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/airflow/.local/lib/python3.12/site-packages/airflow/sdk/api/client.py", line 176, in get_json_error
raise err
airflow.sdk.api.client.ServerResponseError: Server returned error
Correlation-id=019c8f13-333b-7eed-a005-9ad146f79548
[2026-02-24T09:55:29.206431Z] {supervisor.py:1115} ERROR - Server indicated the task shouldn't be running anymore detail={'detail': {'reason': 'not_running', 'message': 'TI is no longer in the running state and task should terminate', 'current_state': 'failed'}} status_code=409 ti_id=UUID('019c89ec-c8f8-7d10-b74c-4afcc071ca46')
[2026-02-24T09:55:34.211829Z] {supervisor.py:718} WARNING - Process did not terminate in time; escalating pid=15965 signal=SIGTERM
[2026-02-24T09:55:34.220909Z] {supervisor.py:710} INFO - Process exited pid=15965 exit_code=-9 signal_sent=SIGKILL
[2026-02-24T09:55:34.221249Z] {supervisor.py:1995} INFO - Task finished task_instance_id=019c89ec-c8f8-7d10-b74c-4afcc071ca46 exit_code=-9 duration=86411.40724210022 final_state=SERVER_TERMINATED
[2026-02-24T09:55:34.225350Z] {trace.py:128} INFO - Task execute_workload[8fd73cf1-4e1a-441d-8f4d-156a70e4b85a] succeeded in 86411.41635726904s: None
[2026-02-24T09:55:47.892614Z] {autoscale.py:125} INFO - Scaling down 1 processes.
```
I will try to confirm asap that this now is an internal infrastructure issue and not an airflow one. To test this, I used the keepalive_interval parameter in the ssh_hook of my SSHOperator:
```python
ssh_hook=SSHHook(
ssh_conn_id="___the_connection_id___",
keepalive_interval=300
),
```
I will post news as soon as I have them. Unfortunatelly every experiment costs 24 hours
--
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
Re: [I] Celery Worker does not respect JWA expiration times - kills tasks prematurely [airflow]
Posted by "ashb (via GitHub)" <gi...@apache.org>.
ashb commented on issue #62218:
URL: https://github.com/apache/airflow/issues/62218#issuecomment-3943014953
Without seeing any logs were just guessing.
Note the default validatity is just 10 mins but tasks heart beat every few seconds and get a refreshed token. They absolutely can run for more than 10minutes
--
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
Re: [I] Celery Worker does not respect JWA expiration times - kills tasks prematurely [airflow]
Posted by "eladkal (via GitHub)" <gi...@apache.org>.
eladkal commented on issue #62218:
URL: https://github.com/apache/airflow/issues/62218#issuecomment-3935215110
cc @vincbeck
--
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
Re: [I] Celery Worker does not respect JWA expiration times - kills tasks prematurely [airflow]
Posted by "alkismavridis (via GitHub)" <gi...@apache.org>.
alkismavridis commented on issue #62218:
URL: https://github.com/apache/airflow/issues/62218#issuecomment-3936166000
So the solution is to increase the value of execution_api -> jwt_expiration_time?
At the moment it is set at 600 (10 minutes).
If this is the issue, would be awesome if you please explain why the task does not die after 600 seconds, but consistently at 24h?
Thank :)
--
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
Re: [I] Celery Worker does not respect JWA expiration times - kills tasks prematurely [airflow]
Posted by "vincbeck (via GitHub)" <gi...@apache.org>.
vincbeck commented on issue #62218:
URL: https://github.com/apache/airflow/issues/62218#issuecomment-3936221254
Maybe @ashb o @amoghrajesh can help us here :)
--
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