Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

[Bug] BanyanDB stream scans run out of query memory even with a small limit

Aperta
  • Qualcosa non va?
#14,165 3 commenti 0 reazioni 2 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@hanahmily ci sta già lavorando.

Dal 23/10/2026.

  • #1428 di @snowhiteohno — chiusa senza merge
  • #1433 di @hanahmily — aperta

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

bug database
Search before asking
  • I had searched in the issues and found no similar issues.
Apache SkyWalking Component

BanyanDB (apache/skywalking-banyandb)

What happened

The nightly Slow Test has been red since about Sept 14. The 3-day load test fails while scanning all data with query memory pool exhausted on stream sw, with the default limit of 20.

From reading the code, the stream query charges every block it loads and every batch the sorted merge takes in, and nothing is given back until the query ends, even though the merge only keeps a few rows. So a plain scan fails once it reads enough data, however small the limit. This lines up with #1334 landing on Sept 14. On the runner the cgroup limit is max, so the pool falls back to 64 MiB and 8 MiB per query, which is why CI hits it first.

What you expected to happen

A limited scan should only be charged for what it holds, and pass.

How to reproduce

Run the Slow Test workflow, or the "3 days with 1 day segment and 3 days ttl" spec in test/integration/load with LOAD_TEST_MINUTES=4320.

Anything else

The client also gets a generic internal error instead of resource exhausted, since the error turns into a string on the way out.

One thing I can't explain yet: the 10-day spec reads about as much data and passes, so how the parts are laid out probably matters too.

I think the fix is to refund blocks once their cursor is released and the rows the merge drops. Happy to work on it if that's the direction you want, or if you'd rather bump the test budget for now.

Are you willing to submit a pull request to fix on your own?
  • Yes I am willing to submit a pull request on my own!
Code of Conduct
Lingua principale
Java
Stelle
25k
Fork
6.6k
Merge medio
15h 4m
PR unite (30g)
32

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di apache/skywalking

Tutte le issue di apache/skywalking

Issue simili

Altre issue su Java

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.