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

[Serve] Expose detailed replica failure reason and rename service failure to crash loop #3403

Closed
wants to merge 14 commits into from

Conversation

Michaelvll
Copy link
Collaborator

@Michaelvll Michaelvll commented Apr 1, 2024

This makes the failure reason for serving more visible and aligns with Kubernetes behavior when the underlying replicas fail.

Tested (run the relevant ones):

  • Code formatting: bash format.sh
  • Any manual or new tests for this PR (please specify below)
  • All smoke tests: pytest tests/test_smoke.py
    • pytest tests/test_smoke.py --serve
  • Relevant individual smoke tests: pytest tests/test_smoke.py::test_fill_in_the_name
  • Backward compatibility tests: bash tests/backward_comaptibility_tests.sh

Copy link
Collaborator

@cblmemo cblmemo left a comment

Choose a reason for hiding this comment

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

Could you elaborate on the status CRASH_LOOP..? What does it means?

if self.first_ready_time is None:
# readiness probe is not executed yet, but a scale down is
# triggered.
return serve_state.ReplicaStatus.SHUTTING_DOWN
if self.first_ready_time == -1:
# initial delay seconds exceeded
return serve_state.ReplicaStatus.FAILED
return serve_state.ReplicaStatus.FAILED_PROBE
Copy link
Collaborator

Choose a reason for hiding this comment

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

Should we use sth like FAILED_INITIALIZATION to diff w/ the following

sky/serve/serve_state.py Outdated Show resolved Hide resolved
@Michaelvll
Copy link
Collaborator Author

Moved to #3411

@Michaelvll Michaelvll closed this Apr 2, 2024
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.

2 participants