[Feature] 移除不必要的info日志打印

[john1337]

Is Your Feature Request Related to a Problem?

移除不必要的info日志打印，现在broker节点打印了太多info级别的日志，这样就会增加磁盘的负担，关键很多info级别的日志确实没啥用，建议关闭

Describe the Solution You'd Like

关闭类似PopReviveService类中POP_LOGGER的日志，现在pop.log文件里面一堆info级别的日志：
2025-11-19 04:08:56 INFO PopReviveService_0 - start revive topic=rmq_sys_REVIVE_LOG_rocketmq-cluster, reviveQueueId=0
2025-11-19 04:08:56 INFO PopReviveService_2 - start revive topic=rmq_sys_REVIVE_LOG_rocketmq-cluster, reviveQueueId=2
2025-11-19 04:08:56 INFO PopReviveService_0 - reviveQueueId=0, old offset is 11456771
2025-11-19 04:08:56 INFO PopReviveService_2 - reviveQueueId=2, old offset is 11475989
2025-11-19 04:08:56 INFO PopReviveService_0 - reviveQueueId=0, ck listSize=15
2025-11-19 04:08:56 INFO PopReviveService_0 - reviveQueueId=0, 1st ck, startOffset=35867262, reviveOffset=11456783; last ck, startOffset=67199, reviveOffset=11456806
2025-11-19 04:08:56 INFO PopReviveService_5 - start revive topic=rmq_sys_REVIVE_LOG_rocketmq-cluster, reviveQueueId=5
2025-11-19 04:08:56 INFO PopReviveService_5 - reviveQueueId=5, old offset is 11475123
2025-11-19 04:08:56 INFO PopReviveService_5 - reviveQueueId=5, ck listSize=25
2025-11-19 04:08:56 INFO PopReviveService_5 - reviveQueueId=5, 1st ck, startOffset=67242, reviveOffset=11475143; last ck, startOffset=67278, reviveOffset=11475178
2025-11-19 04:08:56 INFO PopReviveService_7 - start revive topic=rmq_sys_REVIVE_LOG_rocketmq-cluster, reviveQueueId=7
2025-11-19 04:08:56 INFO PopReviveService_7 - reviveQueueId=7, old offset is 11464451
2025-11-19 04:08:56 INFO PopReviveService_3 - start revive topic=rmq_sys_REVIVE_LOG_rocketmq-cluster, reviveQueueId=3
2025-11-19 04:08:56 INFO PopReviveService_3 - reviveQueueId=3, old offset is 11489186
2025-11-19 04:08:56 INFO PopReviveService_4 - start revive topic=rmq_sys_REVIVE_LOG_rocketmq-cluster, reviveQueueId=4
2025-11-19 04:08:56 INFO PopReviveService_4 - reviveQueueId=4, old offset is 11473009

Describe Alternatives You've Considered

默认关闭这些日志，减少对磁盘的写入压力

Additional Context

No response

[john1337]

protected void mergeAndRevive(ConsumeReviveObj consumeReviveObj) throws Throwable {
    ArrayList<PopCheckPoint> sortList = consumeReviveObj.genSortList();
    POP_LOGGER.info("reviveQueueId={}, ck listSize={}", queueId, sortList.size());
    if (sortList.size() != 0) {
        POP_LOGGER.info("reviveQueueId={}, 1st ck, startOffset={}, reviveOffset={}; last ck, startOffset={}, reviveOffset={}", queueId, sortList.get(0).getStartOffset(),
            sortList.get(0).getReviveOffset(), sortList.get(sortList.size() - 1).getStartOffset(), sortList.get(sortList.size() - 1).getReviveOffset());
    }  应该是一些漏网之鱼，该类好多方法都增加了this.brokerController.getBrokerConfig().isEnablePopLog()条件判断

protected List getReviveMessage(long offset, int queueId) {
PullResult pullResult = getMessage(PopAckConstants.REVIVE_GROUP, reviveTopic, queueId, offset, 32, true);
if (pullResult == null) {
return null;
}
if (reachTail(pullResult, offset)) {
if (this.brokerController.getBrokerConfig().isEnablePopLog()) {
POP_LOGGER.info("reviveQueueId={}, reach tail,offset {}", queueId, offset);
}
} else if (pullResult.getPullStatus() == PullStatus.OFFSET_ILLEGAL || pullResult.getPullStatus() == PullStatus.NO_MATCHED_MSG) {
POP_LOGGER.error("reviveQueueId={}, OFFSET_ILLEGAL {}, result is {}", queueId, offset, pullResult);
if (!shouldRunPopRevive) {
POP_LOGGER.info("slave skip offset correct topic={}, reviveQueueId={}", reviveTopic, queueId);
return null;
}
this.brokerController.getConsumerOffsetManager().commitOffset(PopAckConstants.LOCAL_HOST, PopAckConstants.REVIVE_GROUP, reviveTopic, queueId, pullResult.getNextBeginOffset() - 1);
}
return pullResult.getMsgFoundList();
}