You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@rocketmq.apache.org by GitBox <gi...@apache.org> on 2022/08/04 06:40:54 UTC
[GitHub] [rocketmq] freedom-Li opened a new issue, #4774: topic
freedom-Li opened a new issue, #4774:
URL: https://github.com/apache/rocketmq/issues/4774
The issue tracker is used for bug reporting purposes **ONLY** whereas feature request needs to follow the [RIP process](https://github.com/apache/rocketmq/wiki/RocketMQ-Improvement-Proposal). To avoid unnecessary duplication, please check whether there is a previous issue before filing a new one.
It is recommended to start a discussion thread in the [mailing lists](http://rocketmq.apache.org/about/contact/) in cases of discussing your deployment plan, API clarification, and other non-bug-reporting issues.
We welcome any friendly suggestions, bug fixes, collaboration, and other improvements.
Please ensure that your bug report is clear and self-contained. Otherwise, it would take additional rounds of communication, thus more time, to understand the problem itself.
Generally, fixing an issue goes through the following steps:
1. Understand the issue reported;
1. Reproduce the unexpected behavior locally;
1. Perform root cause analysis to identify the underlying problem;
1. Create test cases to cover the identified problem;
1. Work out a solution to rectify the behavior and make the newly created test cases pass;
1. Make a pull request and go through peer review;
As a result, it would be very helpful yet challenging if you could provide an isolated project reproducing your reported issue. Anyway, please ensure your issue report is informative enough for the community to pick up. At a minimum, include the following hints:
**BUG REPORT**
1. Please describe the issue you observed:
- What did you do (The steps to reproduce)?
- What is expected 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 on how to fix, etc):
**FEATURE REQUEST**
1. Please describe the feature you are requesting.
2. Provide any additional detail on your proposed use case for this feature.
2. Indicate the importance of this issue to you (blocker, must-have, should-have, nice-to-have). Are you currently using any workarounds to address this issue?
4. If there are some sub-tasks involved, use -[] for each sub-task and create a corresponding issue to map to the sub-task:
- [sub-task1-issue-number](example_sub_issue1_link_here): sub-task1 description here,
- [sub-task2-issue-number](example_sub_issue2_link_here): sub-task2 description here,
- ...
--
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: dev-unsubscribe@rocketmq.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [rocketmq] freedom-Li commented on issue #4774: delay offset becomes negative after topic is re-created
Posted by GitBox <gi...@apache.org>.
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: dev-unsubscribe@rocketmq.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [rocketmq] github-actions[bot] commented on issue #4774: delay offset becomes negative after topic is re-created
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on issue #4774:
URL: https://github.com/apache/rocketmq/issues/4774#issuecomment-1674072150
This issue is stale because it has been open for 365 days with no activity. It will be closed in 3 days if no further activity occurs.
--
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: commits-unsubscribe@rocketmq.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [rocketmq] freedom-Li commented on issue #4774: delay offset becomes negative after topic is re-created
Posted by GitBox <gi...@apache.org>.
freedom-Li commented on issue #4774:
URL: https://github.com/apache/rocketmq/issues/4774#issuecomment-1206185241
If the offset is negative, some data will not be consumed normally. What is the solution to this situation?
--
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: dev-unsubscribe@rocketmq.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [rocketmq] github-actions[bot] closed issue #4774: delay offset becomes negative after topic is re-created
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] closed issue #4774: delay offset becomes negative after topic is re-created
URL: https://github.com/apache/rocketmq/issues/4774
--
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: commits-unsubscribe@rocketmq.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [rocketmq] RongtongJin commented on issue #4774: delay offset becomes negative after topic is re-created
Posted by GitBox <gi...@apache.org>.
RongtongJin commented on issue #4774:
URL: https://github.com/apache/rocketmq/issues/4774#issuecomment-1205932409
In version 4.x, after the topic is deleted, the metadata of consumer offset will not be deleted, which may be the reason why the offset is negative.
--
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: dev-unsubscribe@rocketmq.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [rocketmq] freedom-Li commented on issue #4774: delay offset becomes negative after topic is re-created
Posted by GitBox <gi...@apache.org>.
freedom-Li commented on issue #4774:
URL: https://github.com/apache/rocketmq/issues/4774#issuecomment-1206159375
> In version 4.x, after the topic is deleted, the metadata of consumer offset will not be deleted, which may be why the offset is negative.
I have tried deleting all client rocketmq folders and clearing all data on the broker node, and found that after running for a while, the offset value will be negative, and there is a probability that a very small negative value will appear.
--
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: dev-unsubscribe@rocketmq.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [rocketmq] lizhanhui commented on issue #4774: delay offset becomes negative after topic is re-created
Posted by GitBox <gi...@apache.org>.
lizhanhui commented on issue #4774:
URL: https://github.com/apache/rocketmq/issues/4774#issuecomment-1210210949
@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.
--
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: dev-unsubscribe@rocketmq.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [rocketmq] github-actions[bot] commented on issue #4774: delay offset becomes negative after topic is re-created
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on issue #4774:
URL: https://github.com/apache/rocketmq/issues/4774#issuecomment-1676503608
This issue was closed because it has been inactive for 3 days since being marked as stale.
--
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: commits-unsubscribe@rocketmq.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org