[ 
https://issues.apache.org/jira/browse/INLONG-586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

ASF GitHub Bot updated INLONG-586:
----------------------------------
    Labels: pull-request-available  (was: )

> Optimize the implementation of the PartitionExt class
> -----------------------------------------------------
>
>                 Key: INLONG-586
>                 URL: https://issues.apache.org/jira/browse/INLONG-586
>             Project: Apache InLong
>          Issue Type: Improvement
>          Components: inlong-tubemq
>            Reporter: Guocheng Zhang
>            Priority: Normal
>              Labels: pull-request-available
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Optimize the implementation of the PartitionExt class
> This class is an extended class based on Partition class, it's mainly used to 
> manage partitions from the perspective of the client. At present, it mainly 
> implements the current limiting logic, accumulates the consumption 
> metrics(mainly size) of the current partition, and according to the current 
> limiting strategy, there is a large scale per minute and a small scale every 
> 5 seconds, statistics and comparison, and do flow control management.
> Although this logic implements the current limiting operation of the client, 
> it is not well readable. If anyone has a better optimized implementation 
> plan, welcome to put forward your ideas and communicate and improve them.



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

Reply via email to