New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for Amazon Elastic Container Service? #17
Comments
I need to talk to people in the data infrastructure team at Airbnb as to how we are planning on going about our array of workers. Clearly Celery was a first stab at it that works pretty great, and having the CeleryExecutor is an asset, but moving forward we need containment, and to reuse existing infrastructure. I don't know much about Yarn and its APIs, but I thought that would be the way to go. Seems like ECS is another option. Airbnb will build and share a solution that works for us and hopefully for others, if your stack is different or take a different path (say we go Yarn and you want to go ECS), we'll collaborate to make sure we build an interface that works for both, but you'll have to implement that interface. If you want to be part of the conversation on how to distribute tasks to workers I can reach out when the time comes. |
Definitely. Thanks! |
* adding Json-Schema for OpenLineage * update OpenLineage open api spec to refer to JSON Schema Signed-off-by: Julien Le Dem <julien@apache.org>
Just wondering if there's any plan to support Amazon ECS? I saw some discussion about potentially using docker containers for memory management. ECS would be a nice way to abstract away other details like selecting which server should run a given task.
The text was updated successfully, but these errors were encountered: