freedom-Li commented on issue #4774: URL: https://github.com/apache/rocketmq/issues/4774#issuecomment-1210351790
> @freedom-Li Could you provide the exact operational steps performed? RocketMQ uses an eventual-consistency strategy when managing resources to achieve better performance. Specific and detailed operation steps are necessary for a reliable analysis. 1. Pause all java applications (nodes involving mq operations) 2. Pause all mq nodes (including namserver), console 3. Delete the rocketmq store directory, rocketmqlogs directory, and data directory (specified by the storePathRootDir property) 4. Delete all rocketmq directories in the consumer 5. Restart the rocketmq node and start the console 6. Log in to the console, rely on the add/update button in the topic menu item, and manually create a topic, as shown in the following figure:  7. After creating all topics in turn, start all applications. 8. Manually test a small amount of data to send and consume offsets are normal. A few days after the business is put into use normally, when the production and consumption of a topic increases to 5-6 times the daily amount, one or more broker consumption queues will have negative offset values. -- 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]
