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

   ## Summary
   
   - Stop WAL replay from advancing past an unavailable search-index range.
   - On the first gap, force a WAL roll and recreate the iterator from the 
missing search index so newly visible entries can be replayed.
   - If the same gap remains unavailable, fail closed: keep the replay cursor 
at the gap, mark progress as stalled, block realtime admission, and return a 
critical subscription error instead of silently reporting caught-up status.
   - Reset the replay-failure state during initialization, seek, deactivation, 
and cleanup.
   
   ## Reproduction
   
   In the RC4 subscription regression, the writer and source-side count both 
reported 3,999 rows, while the consumer received only 3,942 rows. The server 
log showed WAL replay advancing from expected searchIndex 57 to actual 
searchIndex 113, silently skipping the unavailable range [57, 113). The 
consumer reported no error and the region was still considered caught up.
   
   The same signature appeared in four RC4 runs, while the RC3 control consumed 
all 4,000 written rows with no WAL gap.
   
   ## Tests
   
   - Full reactor test compilation, English locale
   - Full reactor test compilation with with-zh-locale
   - ConsensusPrefetchingQueueTest#testWalReplayRetriesGapWithoutSkippingEntries
   - 
ConsensusPrefetchingQueueTest#testWalReplayFailsCriticallyWhenGapRemainsUnavailable
   
   The targeted tests were rerun after rebasing onto the latest origin/master: 
2 tests, 0 failures, 0 errors.


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