Repository navigation
Replies: 1 comment 1 reply
|
Please first share your deployment configuration, including memory limits and the actual In 0.11.1, if no valid cgroup memory limit is detected and Retry with a short time range and small page size. If it still fails, provide the exact query parameters and heap profiles collected before and during the failures using the profiling guide. |
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment




Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Hi,I’ve encountered an issue; I tried adjusting the parameters but couldn't resolve it, so I am seeking help.Ever since I switched SkyWalking to BanyanDB, I frequently fail to retrieve any data.
Adjusting the memory limits had no effect, even though ample memory was actually allocated.
--allowed-percent int: Allowed percentage of total memory usage. If usage exceeds this value, the query services will stop. This takes effect only if allowed-bytes is 0. If usage is too high, it may cause OS page cache eviction. (default 75)
When querying traces via the UI, switching to a direct query using the Trace ID works fine.
Version:
oap-server:11.0.0
banyandb: 0.11.1
ui:1.0.0
All reactions