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/05/06 09:38:20 UTC
[GitHub] [rocketmq] Chasun-fhd opened a new issue, #4249: Retrying policy may caused the data skew while failing to consume message?
Chasun-fhd opened a new issue, #4249:
URL: https://github.com/apache/rocketmq/issues/4249
Hey, i'm trying to use retrying policy when i failed to consume message. But i found that almost all retrying messages are wrote to one of broker in the cluster. maybe data skew occurred.
After digging into the source code, i found the default value of retryQueueNums in SubscriptionGroupConfig is 1 。is it reason which causing the data skew ? And it seems like only in the Admin Client can modify this parameter. but worried about the consequence if i did so。
wish for replying ... ^.^
--
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] ni-ze commented on issue #4249: Retrying policy may caused the data skew while failing to consume message?
Posted by GitBox <gi...@apache.org>.
ni-ze commented on issue #4249:
URL: https://github.com/apache/rocketmq/issues/4249#issuecomment-1120563484
which version is the broker? Maybe some error is appeared in your client log. Broker log also need to check.
--
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] Chasun-fhd closed issue #4249: Retrying policy may caused the data skew while failing to consume message?
Posted by "Chasun-fhd (via GitHub)" <gi...@apache.org>.
Chasun-fhd closed issue #4249: Retrying policy may caused the data skew while failing to consume message?
URL: https://github.com/apache/rocketmq/issues/4249
--
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] Chasun-fhd commented on issue #4249: Retrying policy may caused the data skew while failing to consume message?
Posted by GitBox <gi...@apache.org>.
Chasun-fhd commented on issue #4249:
URL: https://github.com/apache/rocketmq/issues/4249#issuecomment-1121774971
ok, thks， i will check.
And i also want to ask another question, they two problem seems to cause the same behavior。 when some of pods crashes down for a while in k8s cluster due to vm problem。then recovered, application worked fine, but the message in this broker become more and more, cost a very long time to catch up the offset as other broker. Event increasing quantities of pods , it just cannot solve the message accumulation. Is there any possible or better solutions about this . We already encountered this problem several times.
--
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] Chasun-fhd commented on issue #4249: Retrying policy may caused the data skew while failing to consume message?
Posted by GitBox <gi...@apache.org>.
Chasun-fhd commented on issue #4249:
URL: https://github.com/apache/rocketmq/issues/4249#issuecomment-1120403971
well, it seems like they are all delivered to the same broker. i don't know why this happened, And recently i found another problem, some of brokers in the cluster, queue bound to it cannot be consumed by client, event if add new consumer or reboot my service while connecting to the brokers. Any possible reasons or directions for me to figure it out.. more detail, event restart these problem brokers. the problem is still there.
--
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] ni-ze commented on issue #4249: Retrying policy may caused the data skew while failing to consume message?
Posted by GitBox <gi...@apache.org>.
ni-ze commented on issue #4249:
URL: https://github.com/apache/rocketmq/issues/4249#issuecomment-1129600358
>
I can not answer your question directly, it need deeper analyze base on more details.
--
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] ni-ze commented on issue #4249: Retrying policy may caused the data skew while failing to consume message?
Posted by GitBox <gi...@apache.org>.
ni-ze commented on issue #4249:
URL: https://github.com/apache/rocketmq/issues/4249#issuecomment-1120107927
Which broker received retry message is decided by brokerName of retry message. Usually, message may come from different broker, so retry message send to different broker, not just only one broker.
--
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