The MW Platform dashboard gets around half million Expected key {key} not found due to timeout. errors per week (next largest is 2000 per week). It's not necessarily a problem, e.g. trying to use an expired centralauthtoken is common; but a lot of different mechanisms use the token store, and for some (e.g. central login) a miss would be more unusal, so it would be better to move the logging up the call chain (and downgrade severity where a miss is actually not very surprising).
Description
Description
Details
Details
Related Changes in Gerrit:
Customize query in gerrit
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | DAlangi_WMF | T394402 Reduce noisy auth logs | |||
| Resolved | Krinkle | T379505 "Expected key {key} not found due to timeout" CentralAuth error is spammy |
Event Timeline
Comment Actions
Change #1105046 had a related patch set uploaded (by Jforrester; author: Jforrester):
[mediawiki/extensions/CentralAuth@master] CentralAuthTokenManager::getKeyValueUponExistence: Downgrade very spammy timeout error to info
Comment Actions
Change #1105046 merged by jenkins-bot:
[mediawiki/extensions/CentralAuth@master] CentralAuthTokenManager::getKeyValueUponExistence: Downgrade very spammy timeout error to info
Comment Actions
Change #1146727 had a related patch set uploaded (by Paladox; author: Jforrester):
[mediawiki/extensions/CentralAuth@REL1_43] CentralAuthTokenManager::getKeyValueUponExistence: Downgrade very spammy timeout error to info
Comment Actions
Change #1146727 merged by jenkins-bot:
[mediawiki/extensions/CentralAuth@REL1_43] CentralAuthTokenManager::getKeyValueUponExistence: Downgrade very spammy timeout error to info
Comment Actions
This code was removed completely in https://gerrit.wikimedia.org/r/c/mediawiki/extensions/CentralAuth/+/1130751, there are no more errors logged since then.