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

   ## Problem
   
   When a DataNode lost its subscription broker binding, polling returned 
status 1904 with a "no broker bound to consumer group" message. The client 
treated this as a non-critical poll error, so the provider remained available. 
In a multi-provider consumer, `syncIfUnavailable` also ran only when every 
provider was unavailable, leaving the failed provider unrecovered while other 
providers were still healthy.
   
   ## Changes
   
   - Treat the broker-missing poll status as a provider connection failure and 
mark that provider unavailable.
   - Schedule provider recovery after poll, file-poll, tablet-poll, and commit 
connection failures.
   - Replace unavailable providers during endpoint synchronization even when 
other providers remain available.
   - Add regression coverage for partial multi-provider recovery and the 
distinction between broker-missing and other poll errors.
   
   A commit transport failure still propagates to the caller. The provider is 
recovered asynchronously without replaying the request because a read timeout 
does not establish whether the server accepted the commit.
   
   ## Validation
   
   - `mvn -o -pl iotdb-client/subscription -am -Dtest=... 
-Dsurefire.failIfNoSpecifiedTests=false test` (98 tests passed)
   - `mvn -o -pl iotdb-client/subscription -am -DskipTests -P with-zh-locale 
test-compile` (passed)
   
   


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