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

Gateway timeout (504) when trying to retrieve /api/v0/pins #2500

Open
giliomeejg opened this issue Oct 18, 2022 · 1 comment
Open

Gateway timeout (504) when trying to retrieve /api/v0/pins #2500

giliomeejg opened this issue Oct 18, 2022 · 1 comment

Comments

@giliomeejg
Copy link

Description

On our production server, with around 60k streams, I'm getting a gateway timeout when POSTing to /api/v0/pins. My intention is to get a list of streams, so that I can continue inspecting individual streams.

The lack of pagination when returning the result set is surely going to create problems down the line.

Technical Information

Change /api/v0/pins, or any other endpoint that potentially returns long lists of data to return a paginated set, instead of the entire dataset.

@stbrody
Copy link
Contributor

stbrody commented Oct 18, 2022

Yep, this is a known issue. Listing the set of pinned streams returns the entire result set in a single HTTP response, which can be quite slow and unweildy when the pinset is large. It's on our backlog to address, but isn't a high priority at the moment.

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

No branches or pull requests

2 participants