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.

Sign up for GitHub

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

Jump to bottom

System level Timeout #382

Closed
1 of 12 tasks
migueltol22 opened this issue Jul 8, 2020 · 2 comments
Closed
1 of 12 tasks

System level Timeout #382

migueltol22 opened this issue Jul 8, 2020 · 2 comments
Assignees
@migueltol22
Labels
enhancement New feature or request untriaged This issues has not yet been looked at by the Maintainers

Comments

@migueltol22
Copy link
Contributor

Motivation: Why do you think this is important?
For cases when a pod is stuck in Pending for an extended amount of time it would be useful to have a system level timeout where Propeller kills the job. This would differ from the current node level timeout where both Pending and Running time is taken into account.

Goal: What should the final outcome look like, ideally?
If a pod is Pending for N amount of time the job will be killed and considered a system failure.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

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
If you have ideas about the implementation please propose the change. If inline keep it short, if larger then you link to an external document.

Additional context
Add any other context or screenshots about the feature request here.

Is this a blocker for you to adopt Flyte
Please let us know if this makes it impossible to adopt Flyte
@migueltol22 migueltol22 added enhancement New feature or request untriaged This issues has not yet been looked at by the Maintainers labels Jul 8, 2020
@migueltol22 migueltol22 self-assigned this Aug 5, 2020
@migueltol22 migueltol22 mentioned this issue Aug 5, 2020
Closed
8 tasks
@kumare3
Copy link
Contributor

kumare3 commented Jan 29, 2021

@migueltol22 we have this already

@migueltol22
Copy link
Contributor Author

Closing issue as this already exists.

eapolinario pushed a commit to eapolinario/flyte that referenced this issue Dec 6, 2022
@katrogan
Record IsParent and IsDynamic from propeller events (flyteorg#382)
24ca01f
eapolinario pushed a commit to eapolinario/flyte that referenced this issue Dec 20, 2022
@SandraGH5
Update diabetes.py (flyteorg#382)
a9e2487
eapolinario pushed a commit to eapolinario/flyte that referenced this issue Aug 21, 2023
@katrogan
Record IsParent and IsDynamic from propeller events (flyteorg#382)
1bfb922
eapolinario pushed a commit that referenced this issue Sep 8, 2023
@hamersaw
Add Reasons field to TaskExecutionClosure to track time-series of rea…
695b17a 
…sons (#382)

* added a time-series of reasons to the TaskExecution closure

Signed-off-by: Daniel Rammer <[email protected]>

* added docs

Signed-off-by: Daniel Rammer <[email protected]>

* actually finishing docs too

Signed-off-by: Daniel Rammer <[email protected]>

---------

Signed-off-by: Daniel Rammer <[email protected]>
eapolinario pushed a commit that referenced this issue Sep 13, 2023
@hamersaw @eapolinario
Add Reasons field to TaskExecutionClosure to track time-series of rea…
d6d5d33 
…sons (#382)

* added a time-series of reasons to the TaskExecution closure

Signed-off-by: Daniel Rammer <[email protected]>

* added docs

Signed-off-by: Daniel Rammer <[email protected]>

* actually finishing docs too

Signed-off-by: Daniel Rammer <[email protected]>

---------

Signed-off-by: Daniel Rammer <[email protected]>
Signed-off-by: Eduardo Apolinario <[email protected]>
pvditt pushed a commit that referenced this issue Dec 29, 2023
@hamersaw
Add Reasons field to TaskExecutionClosure to track time-series of rea…
db431a2 
…sons (#382)

* added a time-series of reasons to the TaskExecution closure

Signed-off-by: Daniel Rammer <[email protected]>

* added docs

Signed-off-by: Daniel Rammer <[email protected]>

* actually finishing docs too

Signed-off-by: Daniel Rammer <[email protected]>

---------

Signed-off-by: Daniel Rammer <[email protected]>
eapolinario pushed a commit to eapolinario/flyte that referenced this issue Apr 30, 2024
@pmahindrakar-oss
Upgrade IDL version (flyteorg#382)
50bc5a9
eapolinario pushed a commit to eapolinario/flyte that referenced this issue Apr 30, 2024
@pmahindrakar-oss
Upgrade IDL version (flyteorg#382)
249cd10
austin362667 pushed a commit to austin362667/flyte that referenced this issue May 7, 2024
@pmahindrakar-oss @austin362667
Upgrade IDL version (flyteorg#382)
2ae8158
robert-ulbrich-mercedes-benz pushed a commit to robert-ulbrich-mercedes-benz/flyte that referenced this issue Jul 2, 2024
@pmahindrakar-oss @robert-ulbrich-mercedes-benz
Upgrade IDL version (flyteorg#382)
834bd8e
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@migueltol22 migueltol22

Labels
enhancement New feature or request untriaged This issues has not yet been looked at by the Maintainers
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@kumare3 @migueltol22