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

   ## Description
   
   Strictly unidirectional air-gap UDP currently defaults to 60 KiB datagrams, 
which require IP fragmentation on common 1500-byte MTU links. Default this mode 
to 1400-byte datagrams while preserving explicit packet-size overrides, the 60 
KiB acknowledged-UDP default, and the 5 ms send interval. Smaller datagrams at 
the unchanged interval also lower the per-sender throughput ceiling.
   
   Warn at receiver startup when the operating system provides less socket 
receive-buffer capacity than requested, with matching English and Chinese 
messages. Close the UDP socket if startup fails with an IOException. Socket 
tests cover the strict default, both packet-size aliases, and the existing ACK 
requirement with an unsliced 2500-byte request.
   
   Follows #19063. Strictly unidirectional UDP still cannot confirm delivery or 
receiver write success.
   
   ## Validation
   
   - Spotless passed for the affected modules.
   - Clean English DataNode dependency-closure build and selected unit tests 
passed: 34 tests, 0 failures, 0 errors, 0 skipped.
   - Clean Chinese dependency-closure test compilation passed with 
`with-zh-locale`.
   - All newly added tests were run locally. The fresh English and Chinese runs 
executed every build goal without build-cache loads.
   - Validation covers DataNode and its 28-module dependency closure. Full 
repository builds, distribution packaging, integration suites, sustained 
saturation, and packet-loss injection were not run.
   
   This PR has:
   
   - [x] been independently self-reviewed.
   - [x] added unit tests or modified existing tests to cover the changed 
behavior.
   
   Key changed classes: `IoTDBAirGapSink`, `PipeSinkConstant`, 
`IoTDBAirGapReceiverAgent`, and `IoTDBDataRegionAirGapSinkTest`.
   


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