shuwenwei opened a new pull request, #18554: URL: https://github.com/apache/iotdb/pull/18554
## Description Add a unified DataNode disk exception monitoring metric using a Counter that tracks suspicious disk exceptions across the DataNode write path. ## Design - New `DataNodeExceptionMetrics` class with a Counter named `suspected_disk_exception_count` - Uses exact type matching (`getClass() ==`) instead of `instanceof` for `java.nio.file.FileSystemException` because subclasses (e.g. `NoSuchFileException`, `NotDirectoryException`) typically indicate logical file-state errors rather than real disk failures - Walks the cause chain of the provided throwable to find the exact exception type ## Integration points **Write path:** - `TsFileProcessor` (flush, fsync, close, mod file write, truncate) - `MemTableFlushTask` (writePlanIndices, writeToFileWriter) - `WALBuffer` (roll, force/fsync, close, read) - `CheckpointManager` (write, fsync, roll, close) - `DataRegion` (recovery) **Compaction:** - `AbstractCompactionTask`, `CompactionScheduler` **WAL recovery:** - `WALNodeRecoverTask`, `UnsealedTsFileRecoverPerformer`, `SealedTsFileRecoverPerformer` **Schema engine:** - `SchemaRegionPBTreeImpl` (writeToMLog — single point covering all mlog writes) - `SchemaRegionMemoryImpl`, `MemMTreeSnapshotUtil`, `PBTreeFlushExecutor`, `SchemaFile` **Load:** - `LoadTsFileManager`, `FileLoaderUtils` **Disk management:** - `TierManager` -- 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]
