Large Topics Getting Failed to Close Fetcher and "Something went wrong, an error occurred" interrupting UI

[seyonv]

Issue submitter TODO list

• I've looked up my issue in FAQ
• I've searched for an already existing issues here
• I've tried running main-labeled docker image and the issue still persists there
• I'm running a supported version of the application which is listed here

Describe the bug (actual behavior)

Deploying KafBat to Staging environment and viewing on smaller topics has no issue but loading and searching in larger topics results in the below error.

Attempts to bump KAFKA_ADMIN-CLIENT-TIMEOUT as described in docs don't seem to help or actually bump the timeout with kafbat UI still failing after 30 seconds

2025-02-14 13:00:48.865 | 2025-02-14 18:00:48,864 ERROR [boundedElastic-3] o.a.k.c.c.i.LegacyKafkaConsumer: [Consumer clientId=kafbat-ui-consumer-1739556035154, groupId=null] Failed to close fetcher with a timeout(ms)=30000
-- | --

Expected behavior

Timeouts last longer than 30 seconds and upon failure to search it handles this instead of persisting "Something went wrong, an error occurred" (which occurs very frequently)

Your installation details

4cf17a0
v1.1.0

Relevant helmfile lines:

` image:
repository: '{{ env "IMAGE_NAME" | default "ghcr.io/kafbat/kafka-ui" }}'

staging:
values:
- LOGGING_LEVEL_ROOT: "WARN"
- LOGGING_LEVEL_IO_KAFBAT_UI: "WARN"

`

Steps to reproduce

This is a deployment that connects to our private MSK (not publicly accessible) Kafka clusters so not reproducible on same cluster.

Screenshots

No response

Logs

No response

Additional context

No response

[github-actions]

Hi seyonv! 👋

Welcome, and thank you for opening your first issue in the repo!

Please wait for triaging by our maintainers.

As development is carried out in our spare time, you can support us by sponsoring our activities or even funding the development of specific issues.
Sponsorship link

If you plan to raise a PR for this issue, please take a look at our contributing guide.

[Haarolean]

dupe of #527, please follow #527