CRZbulabula opened a new pull request, #18514:
URL: https://github.com/apache/iotdb/pull/18514

   ## Description
   
   Cherry-pick the upstream fix from merge commit 
23201f223caf29f648c484edc0f10d7714fb3a26 (TimechoDB source: 519946c1a0).
   
   When wal_throttle_threshold_in_byte is hot-reloaded from a positive value to 
a negative value, resolve the negative value to the configured default before 
updating IoTConsensus. Also expose the effective threshold through SHOW 
CONFIGURATION.
   
   The cherry-pick conflicted in PropertiesTest because rc/2.0.11 has a 
different test history. The conflict was resolved by retaining the branch 
existing tests and adding the WAL regression test, plus the required 
ConfigurationFileUtils import.
   
   ## Tests
   
   - mvn spotless:apply -pl iotdb-core/datanode
   - mvn test -pl iotdb-core/datanode -am -Dtest=PropertiesTest 
-DfailIfNoTests=false -Dsurefire.failIfNoSpecifiedTests=false
     - Tests run: 4, Failures: 0, Errors: 0, Skipped: 0


-- 
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]

Reply via email to