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

[jira] [Commented] (TUBEMQ-119) Independent optimization features

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

Guo Jiwei commented on TUBEMQ-119:
----------------------------------

For Log optimization, we should remove StringBuilder from the codes everywhere.

> Independent optimization features
> ---------------------------------
>
>                 Key: TUBEMQ-119
>                 URL: https://issues.apache.org/jira/browse/TUBEMQ-119
>             Project: Apache TubeMQ
>          Issue Type: Task
>            Reporter: Guocheng Zhang
>            Priority: Major
>              Labels: features
>
> 	
> 1. Support the cleaning of consumer group information: including zk information, broker memory information, etc .;
> 	
> 2. Support topics to specify different data disk requirements: for the consideration of subsequent single disk storage, provision of space is required for the mapping of different topics to different disks.
> 	
> 3. HTTP API interface request parameters: In the current Master and Broker http requests, the parameter check is too complicated, if there is a better way to implement the parameter check, it is better
> 	
> 4. Index statistics: Index output should be necessary, but it should be index statistics on key information;
> 	
> 5. Log optimization: The log output should be redesigned. For some content, it should be possible to carry the necessary information through a keyword, print less, and locate the problem at the same time
> 	
> 6. Unit testing: functional modification should be forced to have the construction and verification of unit test cases, so that the built system can introduce as few problems as possible
> 	
> 7. Resource monitoring: monitoring and flow control of key resources such as memory, cpu, and disk capacity
> 	
> 8. Separation of system attributes and business attributes: the newly added attributes of the message should not be added to the attributes of the service for the increase of the system attributes
> 	
> 9. Consider that this feature will affect the overall performance of the system, and there are cases of repetitive wheels. This separate branch is expanded according to external needs.
> 	
> 10. Add unit test cases, new features need to increase unit testing, this omission in the previous improvement



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