Ash
04/26/2023, 3:48 PMCody
04/27/2023, 12:05 AMPending
before timing out after 120 seconds.
I can see the Flow Run start and hit Pending
and at the same time I see the ECS Task appear in the AWS console (shown in screenshot) -
My Agent logs the following:
17:59:41.311 | INFO | prefect.agent - Submitting flow run 'efc6b670-c269-4a87-ba2f-467e4a2c6e85'
17:59:42.349 | INFO | prefect.infrastructure.ecs-task - ECSTask 'berserk-copperhead': Retrieving task definition 'prefect__ecs-task-flow__ecs-task-deployment'...
17:59:43.619 | INFO | prefect.infrastructure.ecs-task - ECSTask 'berserk-copperhead': Creating task run...
17:59:44.216 | INFO | prefect.infrastructure.ecs-task - ECSTask 'berserk-copperhead': Waiting for task run to start...
17:59:44.299 | INFO | prefect.infrastructure.ecs-task - ECSTask 'berserk-copperhead': Status is PROVISIONING.
17:59:54.508 | INFO | prefect.infrastructure.ecs-task - ECSTask 'berserk-copperhead': Status is PENDING.
18:01:46.542 | ERROR | prefect.agent - Failed to submit flow run 'efc6b670-c269-4a87-ba2f-467e4a2c6e85' to infrastructure.
Traceback (most recent call last):
File "C:\Users\Cody\anaconda3\envs\prefect2\lib\site-packages\prefect\agent.py", line 490, in _submit_run_and_capture_errors
result = await infrastructure.run(task_status=task_status)
File "C:\Users\Cody\anaconda3\envs\prefect2\lib\site-packages\prefect_aws\ecs.py", line 619, in run
) = await run_sync_in_worker_thread(
File "C:\Users\Cody\anaconda3\envs\prefect2\lib\site-packages\prefect\utilities\asyncutils.py", line 91, in run_sync_in_worker_thread
return await anyio.to_thread.run_sync(
File "C:\Users\Cody\anaconda3\envs\prefect2\lib\site-packages\anyio\to_thread.py", line 31, in run_sync
return await get_asynclib().run_sync_in_worker_thread(
File "C:\Users\Cody\anaconda3\envs\prefect2\lib\site-packages\anyio\_backends\_asyncio.py", line 937, in run_sync_in_worker_thread
return await future
File "C:\Users\Cody\anaconda3\envs\prefect2\lib\site-packages\anyio\_backends\_asyncio.py", line 867, in run
result = context.run(func, *args)
File "C:\Users\Cody\anaconda3\envs\prefect2\lib\site-packages\prefect_aws\ecs.py", line 814, in _create_task_and_wait_for_start
self._wait_for_task_start(
File "C:\Users\Cody\anaconda3\envs\prefect2\lib\site-packages\prefect_aws\ecs.py", line 1057, in _wait_for_task_start
for task in self._watch_task_run(
File "C:\Users\Cody\anaconda3\envs\prefect2\lib\site-packages\prefect_aws\ecs.py", line 1042, in _watch_task_run
raise RuntimeError(
RuntimeError: Timed out after 122.3249180316925s while watching task for status {until_status or 'STOPPED'}
18:01:46.561 | INFO | prefect.agent - Completed submission of flow run 'efc6b670-c269-4a87-ba2f-467e4a2c6e85'
Does anyone know what the issue could be? I'm fairly new to ECS, so I'm trying to figure out if the fix I need is in the ECS or Prefect side of things.
My ECS Cluster is brand new, I haven't made any changes - basically its just what you'd get if you hit next at every screen during the creation process.Anthony Finocchiaro
04/27/2023, 5:13 AMÅsmund Østvold
04/28/2023, 8:57 AMnicholasnet
04/28/2023, 3:01 PMEric
04/28/2023, 3:42 PMNicholas Crews
05/01/2023, 4:02 PMIvan
05/01/2023, 9:21 PMS3
and S3 Bucket
blocks?Ofir
05/01/2023, 9:34 PMOfir
05/01/2023, 9:34 PMOfir
05/02/2023, 5:19 PM/prefect
prefix.
Otherwise users will get a blank page when visiting /prefect, because the assets won’t be pointing to the right location.
Does anyone have any experience with that?
Should I set PREFECT_UI_SERVE_BASE
env var?
How should the Dockerfile for the agent change?KEVIN K
05/02/2023, 9:50 PMAlon Barad
05/07/2023, 3:00 PMAlon Barad
05/08/2023, 3:00 PMPat
05/08/2023, 6:05 PMKubernetesJob
- does that sound accurate? This is my first foray into Prefect and kubernetes so I may be conflating several technologies 😂Thomas Moore
05/08/2023, 6:10 PMEmanuel Dumitru
05/08/2023, 11:21 PMYSF
05/09/2023, 3:07 AMAlon Barad
05/09/2023, 12:55 PMS
05/09/2023, 5:29 PMJacob Kerber
05/10/2023, 11:44 AMBernard
05/10/2023, 3:34 PMnicholasnet
05/10/2023, 4:49 PMNick
05/11/2023, 3:49 AMFarhood Etaati
05/13/2023, 6:21 PMdeployment.yaml
achieves in a prefect project, when it lacks many of the infra/resource specific information available when you build a deployment via prefect deployment build
.
Link to the discussion:
https://github.com/PrefectHQ/prefect/discussions/9494
The docs are fairly confusing wrt what exactly a prefect project is and how it relates to lower level definitions.Nimesh Kumar
05/16/2023, 8:03 AMCrash detected! Execution was interrupted by an unexpected exception: httpx.HTTPStatusError: Client error '404 Not Found' for url '<http://orion-platformv2.services.carpl.ai/api/task_runs/24fd3ed1-78e5-49b2-84ab-ea42c385c942/set_state>'
For more information check: <https://httpstatuses.com/404>
I stated inference in 500 inputs, and after sometime it gets crashed.
some of the ques i have is.
1. Why it gets crashed, is it because I gave 500 inputs and prefect server fail to handle it.
2. If it gets crashed, is there any mechanism to handle this.
3. And I am using Kubernetes as infrastructure
Can anyone help me pleaseMarco Barbero Mota
05/16/2023, 5:25 PMmondras
05/17/2023, 12:05 AM--infra-block ecs-task/prefect-project
?Amanuel
05/17/2023, 3:38 PMMarco Barbero Mota
05/17/2023, 4:42 PM.pkl
file. The result is a dictionary with two elements (two arrays).
@task(cache_key_fn=cache_file_based_fn,
persist_result=True, result_storage=LocalFileSystem(basepath=settings.main_dir+'/results'),
result_storage_key=settings.main_task_file,
result_serializer="pickle",
cache_result_in_memory=False)
Json is not supported because narrays cant be encoded with JSON. Pickle is fine with me but when I try to open the pickle file that was generated I get the following error: UnpicklingError: invalid load key, '{'.
Any clue why this is happening?
just FYI:
settings.main_task_file = 'results.pkl'