Caideyipi opened a new pull request, #17947: URL: https://github.com/apache/iotdb/pull/17947
## Description This PR fixes an active load test cleanup issue that can leave or recreate \\ext/load\\ during unit test teardown, especially on Windows. The issue is already present on \\origin/master\\: \\LoadTsFileManager\\ starts the active load background scanner from its constructor, and the pipe active-load listening directory is not configurable from \\iotdb-system.properties\\. Tests configure pending/failed active-load directories under \\ arget/ext/load\\, but the pipe listening directory remains at the default \\ext/load/pipe\\, so common test cleanup can fail deleting \\ext/load\\. Changes: - Add \\load_active_listening_pipe_dir\\ config loading and template documentation. - Move the unit-test pipe active-load directory to \\ arget/ext/load/pipe\\. - Make active load start/stop follow \\StorageEngine\\ lifecycle instead of starting from \\LoadTsFileManager\\ construction. - Stop active load scanner/metrics/loader executors cleanly and keep them restartable. - Hot-reload the pipe active-load directory without keeping the previous directory in the scan set. ## Verification - \\mvn -DskipTests spotless:check -pl iotdb-core/datanode\\ - \\git diff --check\\ Tried \\mvn -pl iotdb-core/datanode -Dtest=NewSizeTieredCompactionSelectorTest '-Dcheckstyle.skip=true' test\\, but it did not reach test execution because the current datanode module compile fails on unrelated generated/parser/fill symbols such as \\AlterTopicContext\\, \\IFill\\, and \\Accumulator\\. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
