Random and frequent usePermission timeouts causing 404s #603
Labels
status/triage/completed
Automatic triage completed
status/triage/manual
Manual triage in progress
type/bug
Something isn't working
Issue submitter TODO list
main
-labeled docker image and the issue still persists thereDescribe the bug (actual behavior)
Users are encountering pages refusing to load (spinning) and giving a timeout 404 on waiting. This is during normal browsing through pages like Topics and Messages for a particular cluster. Additionally, some users are seeing timeouts for random frontend assets such as other js or css items.
The usual culprit when this happens is
usePermission.js
which seems to timeout after some time. The full request url for this specific asset from what we've encountered ishttp://kafka-ui.example.io/assets/usePermission-D1xwE96v.js
and if we curl the asset continuously from cli, we can usually reproduce a hanging timeout somewhere after the 3rd or 4th try.In our kafka-ui logs, we see the following printed that correlates with the failure:
However, we've also seen errors like these:
Expected behavior
Expected pages to load on refresh with full content with a few seconds as usually happens after one or more refreshes from encountering the problem. Note the same page may have an issue one time but not another.
Your installation details
Steps to reproduce
Clicking around in UI under any cluster, diving into Topics pages and even Messages usually is where we see the issue most likely happen (although this is biased, other pages might actually exhibit it more often). Note there is no authentication configured in our kafka-ui instance.
Screenshots
No response
Logs
No response
Additional context
Finally, we've encountered other UI weirdness like ERR_EMPTY_RESPONSE with assets like
http://kafka-ui.example.io/assets/Indicator-BUTjfyDu.js
orhttp://kafka-ui.example.io/assets/Input-BPtTPA5k.js
and well as timeouts with other random css or js files which cause the UI to spin. It's about a 50/50 chance on if a single refresh solves the problem or multiple/fullreload is required to even get the UI to load successfully.The text was updated successfully, but these errors were encountered: