Hi,

This is a crucial problem that most of our users may face, and it will
leave them a bad impression of IoTDB.
We need to quickly fix this problem, whether by relaxing the check, giving
more hints, or disabling the parameter by default.

Thanks,
Jialin Qiao

Jialin Qiao (Jira) <[email protected]> 于2019年12月19日周四 下午12:58写道:

> Jialin Qiao created IOTDB-375:
> ---------------------------------
>
>              Summary: Bug in parameter adapter
>                  Key: IOTDB-375
>                  URL: https://issues.apache.org/jira/browse/IOTDB-375
>              Project: Apache IoTDB
>           Issue Type: Bug
>     Affects Versions: 0.9.0, 0.10.0-SNAPSHOT
>             Reporter: Jialin Qiao
>
>
> I set enable_parameter_adapter to true and use the default memory setting.
>
>
>
> After starting IoTDB, I set one storage group root.sg1 and create
> timeseries, the service rejects the creating after 66777 is created.
> However, the log only says that "IoTDB system load is too large to add
> timeseries". We could hint more, such as increase memory or disable the
> enable_parameter_adapter in iotdb-engine.properties.
>
>
>
> Then, I execute delete storage group root.sg1 and redo the above
> operations.
>
>
>
> This time, only 34988 was successfully created. (This is the bug, we
> should be able to create 66777 timeseries again)
>
>
>
> After restart IoTDB, it recalculates the timeseries one-by-one and prints
> a lot of debug logs. I suggest accepting the register without checking
> parameters because it is already checked before.
>
>
>
> --
> This message was sent by Atlassian Jira
> (v8.3.4#803005)
>


-- 
—————————————————
Jialin Qiao
School of Software, Tsinghua University

乔嘉林
清华大学 软件学院

Reply via email to