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] Ray Dashboard reports HTTP 204 under Error QPS #47895

Closed
chasleslr opened this issue Oct 4, 2024 · 4 comments · Fixed by #47896
Closed

[Serve] Ray Dashboard reports HTTP 204 under Error QPS #47895

chasleslr opened this issue Oct 4, 2024 · 4 comments · Fixed by #47896
Assignees
Labels
bug Something that is supposed to be working; but isn't P1 Issue that should be fixed within a few weeks serve Ray Serve Related Issue

Comments

@chasleslr
Copy link

What happened + What you expected to happen

When a deployment returns an HTTP 204, it is reported as an error in the Ray Dashboard. Specifically, these queries are reported under the "Error QPS" charts. An HTTP 2xx should not be considered as an error.

Screenshot 2024-10-04 at 9 07 06 AM

Versions / Dependencies

macOS 14.3
Python: 3.12
ray[serve] 2.37.0

Reproduction script

from ray import serve
from fastapi import FastAPI, Response


app = FastAPI()


@serve.deployment
@serve.ingress(app)
class Deployment:
    @app.post("/")
    def post(self, text: str) -> str:
        return Response(status_code=204)


deployment_app = Deployment.bind()

Issue Severity

None

@chasleslr chasleslr added bug Something that is supposed to be working; but isn't triage Needs triage (eg: priority, bug/not-bug, and owning component) labels Oct 4, 2024
@Superskyyy
Copy link
Contributor

I will fix that, current check is only checked against status code 200

                            is_error=status_code != "200",

@Superskyyy
Copy link
Contributor

Superskyyy commented Oct 4, 2024

Shall we consider whatever doesn't start with 2xx an error? I guess its more of a business-oriented decision but this sounds a general approach that fit most. wdyt @edoakes

@Superskyyy
Copy link
Contributor

Fix added

@edoakes
Copy link
Contributor

edoakes commented Oct 4, 2024

@Superskyyy yes I think characterizing 2XX as success sounds good to me, let me review the PR

@anyscalesam anyscalesam added the serve Ray Serve Related Issue label Oct 7, 2024
@akshay-anyscale akshay-anyscale added the P1 Issue that should be fixed within a few weeks label Oct 15, 2024
@GeneDer GeneDer removed the triage Needs triage (eg: priority, bug/not-bug, and owning component) label Oct 15, 2024
jecsand838 pushed a commit to jecsand838/ray that referenced this issue Dec 4, 2024
…ject#47896)

Closes: ray-project#47895

---------

Signed-off-by: Superskyyy <yihaochen@apache.org>
Co-authored-by: Edward Oakes <ed.nmi.oakes@gmail.com>
Signed-off-by: Connor Sanders <connor@elastiflow.com>
dentiny pushed a commit to dentiny/ray that referenced this issue Dec 7, 2024
…ject#47896)

Closes: ray-project#47895

---------

Signed-off-by: Superskyyy <yihaochen@apache.org>
Co-authored-by: Edward Oakes <ed.nmi.oakes@gmail.com>
Signed-off-by: hjiang <dentinyhao@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something that is supposed to be working; but isn't P1 Issue that should be fixed within a few weeks serve Ray Serve Related Issue
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants