ptlrs commented on PR #9947: URL: https://github.com/apache/ozone/pull/9947#issuecomment-4166156741
>I think the excerpt from the FAQ I mentioned in [this comment](https://github.com/apache/ozone/pull/9947#issuecomment-4090632802) is sufficient to indicate that secondary is expected to open cleanly while writes are ongoing and read-only is not @errose I would not infer "secondary is expected to open cleanly" based just on that FAQ. The FAQ is more likely to be about reading the latest state of a key-value pair. As per the RocksDb code, the race condition due to Manifest file rotation continues to affect secondary instances just like RO instances. This is a transient error which requires a retry attempt from the end-user. There could be more such errors. @ss77892 In RO/Secondary mode, the SST files are opened and their metadata is checked. Each SST file's footer, metaindex blocks, properties block are read. No data related checks are performed though. So integrity and correctness of the SST files is partially present but not for the main contents of the SST file. The main contents of the SST file are indirectly verified when we attempt to read and verify the blocks and chunks in the data scanner. The aim of this check is to quickly see if a disk is healthy or not. Being able to open the DB is one of the indicators. -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
