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

   A transient subscription commit RPC timeout currently escapes from 
`commitSync` after provider recovery is scheduled, causing manual-commit 
consumers to stop even when the connection can recover.
   
   Retry the failed DataNode acknowledgement group up to three times, with a 
five-second interval aligned with provider recovery. Wait outside the provider 
read lock, preserve successful groups and accepted-context cleanup, and stop on 
close, interruption, or fencing. Server rejections and partially accepted 
responses still fail immediately; NACKs retain their existing behavior. 
Explicit asynchronous acknowledgements use the same recovery path.
   
   Validation: ran a clean 11-module dependency reactor with JDK 17, two Maven 
threads, an isolated Maven repository, and sanitized settings on a remote build 
host:
   
   ```text
   mvn -T 2 clean test -pl iotdb-client/subscription -am -P 
with-integration-tests \
     
-Dtest=SubscriptionConsumerMultiProviderPollTest,SubscriptionConsumerLifecycleTest,SubscriptionProviderConnectionTimeoutTest
 \
     -Dsurefire.failIfNoSpecifiedTests=false
   ```
   
   All 41 tests passed, including six new regression methods covering provider 
replacement, unavailable providers, retry exhaustion, server rejection/partial 
acceptance, interruption, and close/fencing. Checkstyle and Spotless passed. 
The original long-running workload has not been rerun.


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