Presto: Unable to retrieve cluster stats via API non-interactively

[tooptoop4]

Previously could do a curl to v1/cluster and get a response like:

{"runningQueries":0,"blockedQueries":0,"queuedQueries":0,"activeCoordinators":1,"activeWorkers":1,"runningDrivers":0,"totalAvailableProcessors":2,"reservedMemory":0.0,"totalInputRows":9563,"totalInputBytes":6249754,"totalCpuTimeSecs":0}

Now the endpoint has changed to ui/api/stats, it works fine for interactive user in the browser (after going via form login page), but non-interactive commands by generic user (with valid credentials) are blocked :(

curl -s -k -L -u "user:pass" https://domain:4039/ui/api/stats -vvv


> GET /ui/api/stats HTTP/1.1
> Host: domain:4039
> Authorization: Basic redact
> User-Agent: curl/7.61.1
> Accept: */*
>
< HTTP/1.1 401 Unauthorized
< Date: Thu, 07 May 2020 10:34:55 GMT
< WWW-Authenticate: Presto-Form-Login
< Content-Length: 0

Can below code be removed?
https://github.com/prestosql/presto/blob/master/presto-main/src/main/java/io/prestosql/server/ui/FormWebUiAuthenticationManager.java#L141-L146

        // send 401 to REST api calls and redirect to others
        if (request.getPathInfo().startsWith("/ui/api/")) {
            response.setHeader(WWW_AUTHENTICATE, "Presto-Form-Login");
            response.setStatus(SC_UNAUTHORIZED);
            return;
        }

Update: even commenting out that block did not solve it :(

[tooptoop4]

cc @dain

[tchunwei]

This config work for me, version 334

web-ui.authentication.type=fixed
web-ui.user=user

[tooptoop4]

@tchunwei I want multiple LDAP users to access the UI not just single user

[tooptoop4]

in v1/jmx/mbean i can see QueuedQueries and RunningQueries but nothing about BlockedQueries

[dain]

Cluster stats were added only for the UI, and are considered a private detail of the web UI. As part of the recent web UI changes all of the internal details of the UI were moved under the /ui prefix. Anything in there should not be used by tooling as they will change at any time without concern for backwards compatibility.

I would suggest that a new interface be designed for what is needed instead of starting with the stuff we added to make the UI look good :)

[vijay-balakrishnan]

We had some automation to bring down the cluster , based on the information available in /v1/cluster. Seems/v1/cluster end point is moved to /ui/api/stat and we are unable to access the /ui/api/stat from any automation jobs due to 401.

[tooptoop4]

right, would be nice to have a 'breaking changes' section in the release notes!

[grantatspothero]

+1 on a breaking changes section of the release notes, this is a problem for anyone using the open source Presto helm chart which uses the /v1/cluster/ endpoint as a healthcheck:
https://github.com/helm/charts/blob/master/stable/presto/templates/deployment-coordinator.yaml#L44-L51

Do any presto devs have a suggested endpoint to use as a healtcheck instead? @dain Preferably something that would not require auth.

edit: asked in slack, and /v1/status works for my use case of a k8s health check

[findepi]

edit: asked in slack, and /v1/status works for my use case of a k8s health check

Exactly. And since https://github.com/prestosql/presto/pull/3428
this can be consumed with HEAD requests too, specifically for
health check purposes.