morningman opened a new issue #6828:
URL: https://github.com/apache/incubator-doris/issues/6828


   ### Search before asking
   
   - [X] I had searched in the 
[issues](https://github.com/apache/incubator-doris/issues?q=is%3Aissue) and 
found no similar issues.
   
   
   ### Version
   
   trunk 80c4007
   
   ### What's Wrong?
   
   create a table and using stream load to load data every 1 second.
   You will see the memory usage of BE like this:
   
![9ccc3abd8f2c5fbb51720d4eb1f34f6f](https://user-images.githubusercontent.com/2899462/137094223-ead2b657-eb69-4f14-8c3a-98c2609f50d2.png)
   
   
   ### What You Expected?
   
   The data loaded is every small(Dozens of MB), so the memory usage should be 
in a low level
   
   ### How to Reproduce?
   
   _No response_
   
   ### Anything Else?
   
   The reason is that most of the memory is occupied by `opened segments`. 
These segments belong to rowsets.
   If rowsets are not cleaned up, these opened segments will always occupy 
memory.
   
   This is a potential memory leak problem. But because in most cases, the 
rowset will be cleaned up within a period of
    time after compaction, so in most cases, the memory will rise to a certain 
stage and it will be stable.
   But if some rowsets have not been compacted, or there are tablets that 
continue to increase,
   the memory will continue to increase.
   
   ### Are you willing to submit PR?
   
   - [X] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)
   


-- 
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]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to