private void recoveryMetaData(StringBuilder strBuff) {
        ProcessResult result = new ProcessResult();
        logger.info("[Recovery meta-data] begin, start read data from local path");
        // a. read cluster configurations
        if (!recoveryClusterConfig(strBuff, result)) {
            return;
        }
        // b. read broker configurations
        if (!recoveryBrokerConfig(strBuff, result)) {
            return;
        }
        // c. read topic control configurations
        if (!recoveryTopicCtrlConfig(strBuff, result)) {
            return;
        }
        // d. read topic deploy configurations
        if (!recoveryTopicDeployConfig(strBuff, result)) {
            return;
        }
        // e. group control configurations
        if (!recoveryGroupCtrlConfig(strBuff, result)) {
            return;
        }
        // f. group consume control configurations
        if (!recoveryConsumeCtrlConfig(strBuff, result)) {
            return;
        }
        logger.info("[Recovery meta-data] end, recovery finished!");
    }
Recovery meta data to Masters
For each type of metadata, they follow the same set of processing procedures:
read metadata locally, write the data to the Master, read the written data from the Master,
and then compare the data read from the Master and the  locally stored data,
determine whether the two are consistent

@param strBuff  the string buffer
inlong-tubemq/tubemq-server/src/main/java/org/apache/inlong/tubemq/server/tools/cli/CliMetaDataBRU.java