Thank you for your suggestion to propose a RIP .

This denotes a significant transformation that mandates a more meticulous
appraisal. The pair of concerns expounded within RIP-67 do harbor a measure
of jeopardy, albeit insufficient to impede the overarching steadiness. It
is imperative for us to plunge further into the indispensability of RIP-67.

王海涛-浙江大学 <wanghaitao0...@qq.com.invalid> 于2023年9月14日周四 10:25写道:

> Hi RocketMQ Community:&nbsp;
>
>
> We re implemented the Controller using JRaft, fixed the issue of linear
> inconsistency, and relied on JRaft's snapshot function to achieve log
> truncation, avoiding infinite growth of Raft logs.&nbsp; &nbsp; In the
> scenario of millions of topics, frequent persistence generates the large
> memory object jsonString of the topicConfigTable. When the memory is tight,
> the large memory object jsonString will be directly allocated to the old
> generation, resulting in frequent Full GC.
>
>
> We have already done part of the work. Our proposals are provided at the
> links below:
>
>
>
> https://docs.google.com/document/d/1mpzTv1vnWxQwPGsHj6Ng2fK9aL9f6MZFw7ZgvW5284o/edit?usp=sharing
>
>
>
> Please welcome to reply to this email or comment on the proposal if you
> have any questions or suggestions.&nbsp; &nbsp;
>
>
>
>
> Thanks,
> HaitaoWang



-- 
   =============================================

  fuyou001
Best Regards

Reply via email to