Skip to content
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

[Feature] Propagate whether a task ran on spot #520

Closed
3 of 13 tasks
katrogan opened this issue Sep 23, 2020 · 1 comment
Closed
3 of 13 tasks

[Feature] Propagate whether a task ran on spot #520

katrogan opened this issue Sep 23, 2020 · 1 comment
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@katrogan
Copy link
Contributor

Motivation: Why do you think this is important?
As users onboard onto interruptible tasks, spot interruptions pose the risk of lengthening overall node execution time. Debugging the source of this latency will be easier if execution code propagates whether a task attempt is scheduled or running on a spot instance

Goal: What should the final outcome look like, ideally?
It should be apparent to end users whether their tasks ran on spot nodes.

Describe alternatives you've considered
The current method of relying on implicit behavior and observing a system retry due to timeout. This is confusing and not very apparent and this assumption is liable to break if back-end changes get implemented to update spot retry logic.

Flyte component

  • Overall
  • Flyte Setup and Installation scripts
  • Flyte Documentation
  • Flyte communication (slack/email etc)
  • FlytePropeller
  • FlyteIDL (Flyte specification language)
  • Flytekit (Python SDK)
  • FlyteAdmin (Control Plane service)
  • FlytePlugins
  • DataCatalog
  • FlyteStdlib (common libraries)
  • FlyteConsole (UI)
  • Other

[Optional] Propose: Link/Inline
N/A

Additional context
N/A

Is this a blocker for you to adopt Flyte
N/A

@katrogan katrogan added enhancement New feature or request untriaged This issues has not yet been looked at by the Maintainers labels Sep 23, 2020
@katrogan katrogan self-assigned this Sep 23, 2020
@katrogan katrogan removed the untriaged This issues has not yet been looked at by the Maintainers label Sep 23, 2020
@katrogan
Copy link
Contributor Author

cc @migueltol22 @EngHabu

@katrogan katrogan added this to the 0.8.0 milestone Sep 29, 2020
eapolinario added a commit to eapolinario/flyte that referenced this issue Dec 20, 2022
Signed-off-by: Eduardo Apolinario <[email protected]>

Co-authored-by: Eduardo Apolinario <[email protected]>
eapolinario pushed a commit to eapolinario/flyte that referenced this issue Dec 20, 2022
eapolinario pushed a commit to eapolinario/flyte that referenced this issue Jul 24, 2023
Bumps [github.com/emicklei/go-restful](https://github.com/emicklei/go-restful) from 2.9.6+incompatible to 2.16.0+incompatible.
- [Release notes](https://github.com/emicklei/go-restful/releases)
- [Changelog](https://github.com/emicklei/go-restful/blob/v3/CHANGES.md)
- [Commits](emicklei/go-restful@v2.9.6...v2.16.0)

---
updated-dependencies:
- dependency-name: github.com/emicklei/go-restful
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
eapolinario pushed a commit to eapolinario/flyte that referenced this issue Aug 21, 2023
Bumps [github.com/emicklei/go-restful](https://github.com/emicklei/go-restful) from 2.9.6+incompatible to 2.16.0+incompatible.
- [Release notes](https://github.com/emicklei/go-restful/releases)
- [Changelog](https://github.com/emicklei/go-restful/blob/v3/CHANGES.md)
- [Commits](emicklei/go-restful@v2.9.6...v2.16.0)

---
updated-dependencies:
- dependency-name: github.com/emicklei/go-restful
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant