sodonnel opened a new pull request, #6148: URL: https://github.com/apache/ozone/pull/6148
## What changes were proposed in this pull request? After SCM is started or after a failover, all the numbers in the replication manager report will be zero, which can lead to confusion. While it may be an idea to throw an error if the report isn't ready yet, that could be an incompatible change, as some monitoring tools to QA scripts could depend on the output to some extent. Therefore it makes sense to print a warning to stderr indicating the report has zero values until replication manager runs for the first time. Same output after this PR: ``` bash-4.2$ ozone admin container report The Container Report is not available until Replication Manager completes its first run after startup or fail over. All values will be zero until that time. Container Summary Report generated at 1970-01-01T00:00:00Z ========================================================== Container State Summary ======================= OPEN: 0 CLOSING: 0 QUASI_CLOSED: 0 CLOSED: 0 DELETING: 0 DELETED: 0 RECOVERING: 0 Container Health Summary ======================== UNDER_REPLICATED: 0 MIS_REPLICATED: 0 OVER_REPLICATED: 0 MISSING: 0 UNHEALTHY: 0 EMPTY: 0 OPEN_UNHEALTHY: 0 QUASI_CLOSED_STUCK: 0 OPEN_WITHOUT_PIPELINE: 0 ``` ## What is the link to the Apache JIRA https://issues.apache.org/jira/browse/HDDS-10272 ## How was this patch tested? Unit tests adjusted and checked the output in docker compose. -- 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]
