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


   
   
   <p>1. Support the cleaning of consumer group information: including zk 
information, broker memory information, etc .;</p>
   
   <p>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.</p>
   
   <p>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</p>
   
   <p>4. Index statistics: Index output should be necessary, but it should be 
index statistics on key information;</p>
   
   <p>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</p>
   
   <p>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</p>
   
   <p>7. Resource monitoring: monitoring and flow control of key resources such 
as memory, cpu, and disk capacity</p>
   
   <p>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</p>
   
   <p>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.</p>
   
   <p>10. Add unit test cases, new features need to increase unit testing, this 
omission in the previous improvement</p>
   <i>JIRA link - <a 
href="https://issues.apache.org/jira/browse/INLONG-119";>[INLONG-119]</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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to