xxd763795151 opened a new issue #2656: URL: https://github.com/apache/rocketmq/issues/2656
The issue tracker is **ONLY** used for bug report(feature request need to follow [RIP process](https://github.com/apache/rocketmq/wiki/RocketMQ-Improvement-Proposal)). Keep in mind, please check whether there is an existing same report before your raise a new one. Alternately (especially if your communication is not a bug report), you can send mail to our [mailing lists](http://rocketmq.apache.org/about/contact/). We welcome any friendly suggestions, bug fixes, collaboration and other improvements. Please ensure that your bug report is clear and that it is complete. Otherwise, we may be unable to understand it or to reproduce it, either of which would prevent us from fixing the bug. We strongly recommend the report(bug report or feature request) could include some hints as the following: **BUG REPORT** 1. Please describe the issue you observed: - What did you do (The steps to reproduce)? io.openmessaging.storage.dledger.DLedgerEntryPusher >>> inner class: QuorumAckChecker#doWork, logging as following: ``` if (DLedgerUtils.elapsed(lastPrintWatermarkTimeMs) > 3000) { logger.info("[{}][{}] term={} ledgerBegin={} ledgerEnd={} committed={} watermarks={}", memberState.getSelfId(), memberState.getRole(), memberState.currTerm(), dLedgerStore.getLedgerBeginIndex(), dLedgerStore.getLedgerEndIndex(), dLedgerStore.getCommittedIndex(), JSON.toJSONString(peerWaterMarksByTerm)); lastPrintWatermarkTimeMs = System.currentTimeMillis(); } ``` It is use default appender to log synchronusly. But there are some questions : if log occur rolling and archive, that will cost too time. In my mac , about 400-600ms，different cloud virtual machine：about 600-900ms，physical machine (on our production environment) more than 1000ms. As a result, it may cause the client send timeout(send tps > 1200/broker and master-slave network latency about 0.01 - 0.3 ms in the most time, client`s timeout config is 3s). The log record for this place is between in the client send request-response, so it logging asynchronously . - What did you expect to see? - What did you see instead? 2. Please tell us about your environment: 3. Other information (e.g. detailed explanation, logs, related issues, suggestions how to fix, etc): ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected]
