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/04/12 02:18:42 UTC
[GitHub] [rocketmq] cserwen opened a new issue, #4153: [POP] In some cases, the message is considered to have failed to consume.
cserwen opened a new issue, #4153:
URL: https://github.com/apache/rocketmq/issues/4153
## Case 1:
See issue https://github.com/apache/rocketmq/issues/3787
## Case 2:
The delay level of ack&ck msg both are 9(5min) because `invisibleTime` is 5min.
In this case, client will ack the msg after a long time (20~30s) and cause that the ack message was delivered into schedule topic 17s later than the ck message. So this ck will be revived always.
**The above two cases are caused by the inflexibility of delayed messages.**
--
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] cserwen commented on issue #4153: [POP] In some cases, the message is considered to have failed to consume.
Posted by GitBox <gi...@apache.org>.
cserwen commented on issue #4153:
URL: https://github.com/apache/rocketmq/issues/4153#issuecomment-1095860221
@lizhiboo @duhenglucky It looks like implementing seconds delay messages is important for POP
--
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] hill007299 commented on issue #4153: [POP] In some cases, the message is considered to have failed to consume.
Posted by GitBox <gi...@apache.org>.
hill007299 commented on issue #4153:
URL: https://github.com/apache/rocketmq/issues/4153#issuecomment-1096565211
> @lizhiboo @duhenglucky It looks like implementing seconds delay messages is important for POP
Timing messages have become more and more important ļ¼this feature is already planned
--
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 #4153: [POP] In some cases, the message is considered to have failed to consume.
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] closed issue #4153: [POP] In some cases, the message is considered to have failed to consume.
URL: https://github.com/apache/rocketmq/issues/4153
--
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] github-actions[bot] commented on issue #4153: [POP] In some cases, the message is considered to have failed to consume.
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on issue #4153:
URL: https://github.com/apache/rocketmq/issues/4153#issuecomment-1542956551
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
[GitHub] [rocketmq] cserwen commented on issue #4153: [POP] In some cases, the message is considered to have failed to consume.
Posted by GitBox <gi...@apache.org>.
cserwen commented on issue #4153:
URL: https://github.com/apache/rocketmq/issues/4153#issuecomment-1100040392
> rocketmq/broker/src/main/java/org/apache/rocketmq/broker/processor/AckMessageProcessor.java
@pingww Yes, you are right. But we only have 18 delay levels for delay msg. In most scenarios, the real delivery time of ck&ack msg is not the time `popTime + invisibleTime` because of the following code:
https://github.com/apache/rocketmq/blob/a17fa7605cfbd266e4468e6fe2d6cf6711572111/broker/src/main/java/org/apache/rocketmq/broker/util/MsgUtil.java#L27
--
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] pingww commented on issue #4153: [POP] In some cases, the message is considered to have failed to consume.
Posted by GitBox <gi...@apache.org>.
pingww commented on issue #4153:
URL: https://github.com/apache/rocketmq/issues/4153#issuecomment-1099985704
the ck&ak delay timestamp is both popTime + invisibleTimeļ¼
`ExtraInfoUtil.getPopTime(extraInfo) + ExtraInfoUtil.getInvisibleTime(extraInfo))`
ck can always see ak , only client will ack the msg in invisibleTime,
--
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 #4153: [POP] In some cases, the message is considered to have failed to consume.
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on issue #4153:
URL: https://github.com/apache/rocketmq/issues/4153#issuecomment-1537249001
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] pingww commented on issue #4153: [POP] In some cases, the message is considered to have failed to consume.
Posted by GitBox <gi...@apache.org>.
pingww commented on issue #4153:
URL: https://github.com/apache/rocketmq/issues/4153#issuecomment-1100499543
>
look forward to precise second-level timing
--
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] ferrirW commented on issue #4153: [POP] In some cases, the message is considered to have failed to consume.
Posted by GitBox <gi...@apache.org>.
ferrirW commented on issue #4153:
URL: https://github.com/apache/rocketmq/issues/4153#issuecomment-1113006176
> this feature is already planned
Is there have more details and schedule for Timing messages? @hill007299 @duhenglucky
--
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