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

Set RemoteReadConcurrencyLimit to fix /api/v1/read #351

Merged
merged 1 commit into from
Oct 6, 2020

Conversation

frebib
Copy link
Contributor

@frebib frebib commented Oct 6, 2020

Previously this value was unset, defaulting to zero. A zero-value
initialised a channel with no buffer, causing all writes to the buffer
to hang, and therefore all remote_read queries to hang until they
timed-out. This is contradictory to the Prometheus documentation, which
claims that a zero value allows infinite concurrent reads.

Related: https://github.com/prometheus/prometheus/pull/4656/files

Fixes: #350
Signed-off-by: Joe Groocock jgroocock@cloudflare.com

Previously this value was unset, defaulting to zero. A zero-value
initialised a channel with no buffer, causing all writes to the buffer
to hang, and therefore all remote_read queries to hang until they
timed-out. This is contradictory to the Prometheus documentation, which
claims that a zero value allows infinite concurrent reads.

Fixes: jacksontj#350
Signed-off-by: Joe Groocock <jgroocock@cloudflare.com>
@jacksontj
Copy link
Owner

Thanks for the contribution!

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.

promxy remote_read api endpoint hangs forever
2 participants