JackieTien97 opened a new pull request, #19165: URL: https://github.com/apache/iotdb/pull/19165
## Description Long JVM pauses can exceed Edge's default 20-second metadata lease and trigger DataNode cache fencing and recovery even though ConfigNode and DataNode share the same JVM. Set the Edge default `metadata_lease_fence_ms` to `315360000000` (ten 365-day years) to effectively disable lease expiry for the combined process. The finite value leaves headroom for the ConfigNode's five-second margin and conversion to nanoseconds. It also extends the ConfigNode's cache-invalidation wait when a service is unreachable. The standard deployment default remains 20 seconds. ## Validation - `mvn clean package -DskipTests -pl distribution -am` — passed. - `mvn verify -Drat.skip=true -DskipUTs -Dit.test=IoTDBEdgeBasicIT -DfailIfNoTests=false -Dfailsafe.failIfNoSpecifiedTests=false -pl integration-test -am -P EdgeIT -P with-integration-tests` — 7 tests passed, none failed or skipped; startup, Tree/Table reads and writes, concurrent queries, and shutdown verified using the generated Edge package. - Checked the generated archives and SHA-512 checksums; the long lease is present only in the Edge configuration. - Checked that adding the ConfigNode margin and converting the timeout to nanoseconds fit in a signed `long`. The initial integration-test invocation was blocked by RAT scanning seven pre-existing, untracked local files. The successful run skipped RAT; those files are not included in this PR. This PR has: - [x] been self-reviewed. - [x] added comments explaining the configuration's purpose and finite value. - [x] been tested with a local Edge instance. -- 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]
