Skip to content

[IT] Pin the DataRegions per DataNode in IoTDBMultiTAGsWithAttributesTableIT #19086

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
JackieTien97 merged 1 commit into from
Nov 5, 2026
+6 −0
Merged

[IT] Pin the DataRegions per DataNode in IoTDBMultiTAGsWithAttributesTableIT #19086

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions ...c/test/java/org/apache/iotdb/relational/it/db/it/IoTDBMultiTAGsWithAttributesTableIT.java
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -185,6 +185,12 @@ public class IoTDBMultiTAGsWithAttributesTableIT {
@BeforeClass
public static void setUp() throws Exception {
EnvFactory.getEnv().getConfig().getDataNodeCommonConfig().setSortBufferSize(1024 * 1024L);
// Under the default PROACTIVE extension policy, the number of DataRegionGroups follows the
// CPU cores of the DataNodes, and with it the number of FragmentInstances of
// fourTableJoinTest, many of which reserve up to the 1 MB sort buffer. Pin the DataRegions per
// DataNode so that the region layout matches a 4-core CI runner on every machine and the
// instances fit into the operator memory of the default DataNode heap.
EnvFactory.getEnv().getConfig().getCommonConfig().setDataRegionPerDataNode(2);
EnvFactory.getEnv().initClusterEnvironment();

@JackieTien97 JackieTien97 Nov 4, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pre-existing, and not caused by this PR, but since this setUp is being touched anyway: the setMaxTsBlockLineNumber(2).setMaxNumberOfPointsInPage(5) call just below runs after initClusterEnvironment(). The node configuration is only written when the nodes are created, so these two settings never reach the running cluster, and the test has always run with the defaults. Moving them before initClusterEnvironment() would apply them, but it changes the effective configuration (and possibly the memory numbers above), so it may be better as a separate change.

EnvFactory.getEnv()
.getConfig()
Expand Down
Loading