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

   ## Description
   
   When an AirGap sink establishes a TCP connection but the application 
handshake fails, one retry cycle can emit multiple WARN logs with duplicate 
stack traces. In a tight reconnect loop, the TCP connection INFO log and 
repeated handshake warnings can dominate log_datanode_all.log.
   
   ### Changes
   
   - Restore LoggerPeriodicalLogReducer as the default PipeLogger 
implementation. The shared-reducer refactor removed the DataNode-side injection 
but left the default implementation formatting logs without rate limiting.
   - Log retryable connection and handshake failures as rate-limited root-cause 
summaries instead of repeated stack traces.
   - Keep the full throwable on the final task-stopping warning for diagnosis.
   - Downgrade the TCP-only connection success message from INFO to DEBUG 
because the application handshake may still fail.
   - Format handshake failures with a stable remote endpoint instead of the 
socket's ephemeral local port, allowing duplicate messages to share a 
rate-limit key.
   - Update both English and Chinese messages and make PipeLoggerTest exercise 
the default logger path.
   
   ### Verification
   
   - mvn -o -pl iotdb-core/node-commons 
-Dtest=PipeLoggerTest,LoggerPeriodicalLogReducerTest test
   - mvn -o -pl iotdb-core/node-commons -P with-zh-locale -DskipTests 
test-compile
   - mvn -o -pl iotdb-core/node-commons spotless:apply
   
   <hr>
   
   This PR has:
   - [x] been self-reviewed.
   - [x] added or updated unit tests for the changed behavior.
   - [x] been compiled with both English and Chinese locales.
   
   <hr>
   
   ##### Key changed classes
   
   - PipeLogger
   - PipeAbstractSinkSubtask
   - IoTDBAirGapSink
   - PipeLoggerTest


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