Skip to content

Conversation

@spkrka
Copy link
Member

@spkrka spkrka commented Jul 10, 2020

No description provided.

@spkrka spkrka force-pushed the krka/outstanding-per-host branch 2 times, most recently from 03bdf79 to 9d522d6 Compare July 10, 2020 12:46
@spkrka spkrka force-pushed the krka/outstanding-per-host branch from 9d522d6 to 329992a Compare July 10, 2020 13:08
@amirhadadi
Copy link

@spkrka SemanticFolsomMetricsTest::testRegisterOutstandingRequestsGauge is failing with this change.
Here's a gist to fix and improve that test: https://gist.github.com/amirhadadi/6e4580c7e91887e53f0993d30e619674

@amirhadadi
Copy link

@spkrka did you have a chance to review my suggested fix?

@spkrka
Copy link
Member Author

spkrka commented Sep 24, 2020

No, I am still not sure if this change even makes sense on a high level.

@amirhadadi
Copy link

@spkrka the motivation is to have metrics that will allow identifying misbehaving memcached nodes.
There's also another related issue - the disconnect reason in DefaultRawMemcacheClient does not contain the offending node, which can be very helpful in identifying misbehaving nodes.

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.

4 participants