Skip to content

Fix RPC buffer memory control activation#18194

Merged
jt2594838 merged 1 commit into
apache:masterfrom
Caideyipi:fix-cn-rpc-memory-control
Jul 14, 2026
Merged

Fix RPC buffer memory control activation#18194
jt2594838 merged 1 commit into
apache:masterfrom
Caideyipi:fix-cn-rpc-memory-control

Conversation

@Caideyipi

Copy link
Copy Markdown
Collaborator

Summary

  • Defer DataNode RPC buffer memory control activation until DataNode startup so ConfigNode-side config loading does not install the DataNode RPC quota.
  • Bind each auto-resizing buffer lifecycle to the memory account used for allocation, avoiding over-release when the global controller changes later.
  • Add regression coverage for no-op/real controller transitions and explicit DataNode activation.

Tests

  • mvn test -pl iotdb-client/service-rpc -Dtest=AutoResizingBufferTest
  • mvn test -pl iotdb-core/datanode -am -Dtest=DataNodeMemoryConfigTest -DfailIfNoTests=false -Dsurefire.failIfNoSpecifiedTests=false
  • git diff --check

Avoid activating DataNode RPC buffer memory control during configuration loading, and bind auto-resizing buffers to the memory account used for their allocation.
@jt2594838 jt2594838 merged commit 0d3304a into apache:master Jul 14, 2026
41 checks passed
@jt2594838 jt2594838 deleted the fix-cn-rpc-memory-control branch July 14, 2026 01:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants