Thanks everyone for the replies, I have deployed 0.11.3 RC3. I will try that 
before I try altering the level compaction.


Thanks 

Trevor Hart








---- On Fri, 09 Apr 2021 23:29:07 +1200 Xiangdong Huang <[email protected]> 
wrote ----



And remember to set the strategy back after diagnosis... 
 
----------------------------------- 
Xiangdong Huang 
School of Software, Tsinghua University 
 
 黄向东 
清华大学 软件学院 
 
 
Jialin Qiao <mailto:[email protected]> 于2021年4月9日周五 下午7:24写道: 
 
> Hi, 
> 
> This may due to the Compaction. To verify the problem, change the 
> compaction_strategy 
> to NO_COMPACTION. 
> 
> This is fixed in the 0.11.3 RC3[1]. you could try this version :) 
> 
> [1] https://dist.apache.org/repos/dist/dev/iotdb/0.11.3/rc3 
> 
> Thanks, 
> ————————————————— 
> Jialin Qiao 
> School of Software, Tsinghua University 
> 
> 乔嘉林 
> 清华大学 软件学院 
> 
> 
> Trevor Hart <mailto:[email protected]> 于2021年4月9日周五 上午10:29写道: 
> 
>> Hi Team, 
>> 
>> I am still struggling with high CPU usage on V11.2. My CPU usage creeps 
>> up after a few days and basically got to 100% today and was unusable. 
>> 
>> If I restart the iotDB server then its fine for a few days. This Linux 
>> server has 2 cores and 4Gb RAM. The database is running 24x7. 
>> 
>> The data ingestion is typically small. Maybe a 500 points per minute. I 
>> can never see any data ingestion backing up unless the CPU is over 90%. 
>> 
>> Questions; 
>> 
>> 1. Does anyone else see this behaviour? 
>> 2. Are there any maintenance tasks I should call daily? Should I be 
>> calling Flush daily? 
>> 3. Should I reduce the WAL threshold? 
>> 4. I am using compaction_strategy=LEVEL_COMPACTION 
>> 5. And have set enable_unseq_compaction=false 
>> 
>> Is there anything else I can try or do I just need bigger hardware? 
>> 
>> 
>> 
>> 
>> 
>> Thanks 
>> Trevor 
>> 
>> 
>>

Reply via email to