Skip to content

Support AWS Fargate execution #134

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

Open
wants to merge 14 commits into
base: develop
Choose a base branch
from
Open

Conversation

szczeles
Copy link
Contributor

@szczeles szczeles commented Mar 30, 2022

This PR adds support of executing Kedro pipeline steps in AWS Fargate. No tests added yet 🙈


Keep in mind:

  • Documentation updates
  • Changelog updates
  • Tests added

@@ -4,7 +4,7 @@ repos:
hooks:
- id: isort
- repo: https://github.com/psf/black
rev: stable
rev: 22.3.0
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor

@mwiewior mwiewior left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I will try to run it on my own to verify both code and documentation prior approvint this PR.

@szczeles
Copy link
Contributor Author

@mwiewior That's fine! Also, please keep in mind that unit tests are still missing, I'm going to add some in the day or two.

@szczeles
Copy link
Contributor Author

@mwiewior Tests are ready

@sonarqubecloud
Copy link

sonarqubecloud bot commented Sep 1, 2022

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 2 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

@marcelopio
Copy link

Hi!

What is missing so this can be merged?

@szczeles
Copy link
Contributor Author

@marcelopio This execution method turned out to be terribly slow in Fargate - there is like 5 minutes overhead for every single Kedro node due to slow download/extraction of big images (and apparently no images caching). With very "linear" pipelines, it takes hours to execute...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants