Anton L.
02/21/2024, 5:06 AMMarvin
02/21/2024, 5:06 AM--prefetch-seconds
or PREFECT_WORKER_PREFETCH_SECONDS
with AWS Elastic Container Service and Push work pool type. Therefore, I would not be able to confirm the applicability of these settings in that specific environment based on this documentation excerpt.
To get more suitable information, it might be necessary to perform an additional search or review the Prefect documentation more thoroughly. If the usage of --prefetch-seconds
or PREFECT_WORKER_PREFETCH_SECONDS
with AWS ECS Push Work Pool Type is a feature supported in Prefect, it is expected to be documented, or there might be relevant discussions or use cases mentioned in GitHub issues.
If you need further assistance with this, I can perform additional searches to attempt to find more relevant information. Let me know if you'd like me to continue.Anton L.
02/21/2024, 5:08 AMAnton L.
02/21/2024, 5:15 AMMarvin
02/21/2024, 5:16 AM--prefetch-seconds
or the PREFECT_WORKER_PREFETCH_SECONDS
environment variable in this context. However, it does discuss the ability to submit variables via the job in the deployment step, implying some level of customization is possible in this execution environment (Source).
Since no GitHub issues were found related to this specific question, the best course of action would be to check the official Prefect documentation for ECS push work pool configurations, or consult Prefect support or community forums for guidance on setting prefetch behavior in AWS ECS with push work pools.
If this feature is crucial for your workflow and you cannot find the answer in the documentation or community resources, reaching out directly to Prefect may be the most efficient way to get a definitive answer.