[GitHub] [incubator-inlong] dockerzhang opened a new issue #941: [INLONG-345] Optimize the call logic of getMessage() in Pull mode

[GitBox <gi...@apache.org>]

dockerzhang opened a new issue #941:
URL: https://github.com/apache/incubator-inlong/issues/941


   <p>When the business thread calls getMessage() in the pull mode, if the current client does not have a free partition, the function will return immediately. At this time, the thread needs to control the sleep time by itself to avoid frequent calls to the function but no free partition consumption, causing the CPU to surge. This call logic can be optimized, that is, we can check in getMessage and let the business control check how long it has not met the requirements before returning, reducing the complexity of the business use.</p>
   <i>JIRA link - <a href="https://issues.apache.org/jira/browse/INLONG-345">[INLONG-345]</a> created by gosonzhang</i>


-- 
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@inlong.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [incubator-inlong] dockerzhang closed issue #941: [INLONG-345] Optimize the call logic of getMessage() in Pull mode

[GitBox <gi...@apache.org>]

dockerzhang closed issue #941:
URL: https://github.com/apache/incubator-inlong/issues/941


   


-- 
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@inlong.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org