-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
backport (query: fix deadlock in endpointset (#4795)) #4926
Conversation
Thx, let's add the DCO 👍 cc @squat |
Sounds good to me. I can cut the next patch release for 0.23 and add this to the change log |
@GiedriusS I cannot pass the DCO step because it is your commit. |
Ofc you can, just add your DCO on top with the suggested commands ;P |
Avoid RLock()ing twice as described here: thanos-io#4766 (comment) (due to https://stackoverflow.com/questions/30547916/goroutine-blocks-when-calling-rwmutex-rlock-twice-after-an-rwmutex-unlock/30549188). Fix it by removing HasClients() and simply changing it with `er.clients != nil`. Signed-off-by: Giedrius Statkevičius <[email protected]> Signed-off-by: Aymeric <[email protected]>
b3aa489
to
5b82a33
Compare
My bad 😇 My DCO is added to the commit |
Thanks @aymericDD (: WDYT @GiedriusS? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Makes sense, thanks!
@squat do you know when the fix release will be published? It is very painful for us to maintain Thanos in production. Our queries are stuck or restart after a long time and we have high latency.... |
Today 👍 |
Thanks @squat 👍 |
Here's the new PR to cut 0.23.2: #4936 |
Avoid RLock()ing twice as described here:
#4766 (comment)
(due to
https://stackoverflow.com/questions/30547916/goroutine-blocks-when-calling-rwmutex-rlock-twice-after-an-rwmutex-unlock/30549188).
Fix it by removing HasClients() and simply changing it with
er.clients != nil
.Signed-off-by: Giedrius Statkevičius [email protected]
Changes
Verification