You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tubemq.apache.org by "Guocheng Zhang (Jira)" <ji...@apache.org> on 2020/05/12 06:35:00 UTC

[jira] [Commented] (TUBEMQ-99) 400 - All partition in waiting, retry later!

    [ https://issues.apache.org/jira/browse/TUBEMQ-99?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17105134#comment-17105134 ] 

Guocheng Zhang commented on TUBEMQ-99:
--------------------------------------

Thanks [~tiyeliyameng]

This error indicates that when the current pull thread is consumed, all partitions are in use, thereby telling the caller that there is no free partition to consume.

This situation generally occurs when there are more pull threads than the currently allocated partitions, such as load balancing, expansion and contraction, and the actual number of threads created is greater than the maximum number of allocable partitions. This is a normal operating state. It is recommended to pull threads Sleep 200 ~ 400 hundred milliseconds when receiving such error return.

>  400 - All partition in waiting, retry later!
> ---------------------------------------------
>
>                 Key: TUBEMQ-99
>                 URL: https://issues.apache.org/jira/browse/TUBEMQ-99
>             Project: Apache TubeMQ
>          Issue Type: Bug
>            Reporter: tiyeliyameng
>            Priority: Major
>
> we checked logs and found these infos,but data seemed ok



--
This message was sent by Atlassian Jira
(v8.3.4#803005)