hongzhi-gao opened a new pull request, #19065: URL: https://github.com/apache/iotdb/pull/19065
## Description Backport #18803 to `dev/1.3`. During restart recovery, a DataRegion with no asynchronous TsFile resource recovery tasks already initializes compaction scheduling in synchronous recovery. The subsequent asynchronous recovery flow initializes it again, creating duplicate entries shared by TTL and compaction scheduling. Skip that flow for empty task lists, make registration atomic and idempotent under the existing Vector monitor, and remove every occurrence of the same DataRegion on unregistration. Preserve dev/1.3's existing compaction-disable behavior when resolving the cherry-pick conflict; the `setAllowCompaction(false)` context line in master was not part of #18803's change. ## Validation - Passed scoped `mvn spotless:apply -o -pl iotdb-core/datanode '-DspotlessFiles=.*(StorageEngine|CompactionScheduleTaskManager)\.java' -Dscan.skip=true -Ddevelocity.off=true`. - Passed `mvn test -pl iotdb-core/datanode -am -Dtest=StorageEngineTest -Dsurefire.failIfNoSpecifiedTests=false -DfailIfNoTests=false -Dscan.skip=true -Ddevelocity.off=true -Dmaven.wagon.http.retryHandler.count=1 -Dmaven.wagon.rto=15000` (2 tests, no failures/errors). - A temporary Java harness extracted the changed production methods and verified sequential/concurrent duplicate registration, cleanup of legacy duplicate entries, repeated unregistration, and null/empty/nonempty recovery task handling. The same harness fails on the dev/1.3 baseline for duplicate registration and duplicate scheduling initialization. This uses stand-ins for surrounding services and is not a node restart integration test. - Independent source review and `git diff --check` passed. No node restart IT was run for this backport. -- 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]
