Jiahua Wang e348efa66b [ISSUE #10575] Fix race condition between scanResponseTable and processResponseCommand (#10576) ...

processResponseCommand used get+remove (non-atomic) to retrieve ResponseFuture
from responseTable. scanResponseTable used iterator.remove(). If the response
arrived between scanResponseTable's remove and processResponseCommand's get,
the response would be logged as 'not matched any request' and silently dropped.
The callback would fire with timeout instead of success, even though the broker
had successfully processed the request.

Fix: Use ConcurrentHashMap.remove(key) in both methods. This is atomic:
either processResponseCommand gets the future (and executes success callback),
or scanResponseTable gets it (and executes timeout callback), but never both
and never neither.

Co-authored-by: wangjiahua.wjh <wangjiahua.wjh@alibaba-inc.com>

2026-08-26 15:12:46 +08:00

..

src

[ISSUE #10575] Fix race condition between scanResponseTable and processResponseCommand (#10576)

2026-08-26 15:12:46 +08:00

BUILD.bazel

[ISSUE #10651] bump DLedger to 0.3.3.4 (maintenance line) (#10958)

2026-08-19 14:58:30 +08:00

pom.xml

[ISSUE #9663] Adopt Maven's revision mechanism (requires Maven >= 3.5.0) (#9665)

2025-09-04 09:51:02 +08:00