Guocheng Zhang created TUBEMQ-119:
-------------------------------------

             Summary: Independent optimization features
                 Key: TUBEMQ-119
                 URL: https://issues.apache.org/jira/browse/TUBEMQ-119
             Project: Apache TubeMQ
          Issue Type: Task
            Reporter: Guocheng Zhang


        

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: the parameters are too complicated, 
it would be better if you could check and return the specific meaning with a 
concise scheme
        
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)

Reply via email to