Browse Source
When agg=NONE (the default), findAllAsyncWithLimit() executed a synchronous JPA query on the calling thread and wrapped the result in Futures.immediateFuture(). Since this runs inside the access-validator single-thread executor callback chain, a slow query blocks all other telemetry and attribute requests. Offload findAllAsyncWithLimit() to the JpaExecutorService work-stealing pool via service.submit(), matching the pattern already used by aggregated queries (findAndAggregateAsync). Closes #15095 Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>pull/15101/head
3 changed files with 6 additions and 6 deletions
Loading…
Reference in new issue