Well, it turns out that the Dynamic Parameter Adapter thought the memory is insufficient according to the workload and refused to create new time series. But actually when I turned it off, I found that was a misjudge since it is okay using the default parameters.
I think the definition of "workload too heavy" in the Dynamic Parameter Adapter is too strict, which dramatically underestimates the ability of the system. Besides, when it judges the workload to be unacceptable and refuses to create time series, it does not leave enough logs or give enough feedback to the user to indicate the cause. | | Tian Jiang | | [email protected] | 签名由网易邮箱大师定制 On 9/25/2019 11:31，徐毅<[email protected]> wrote： Hi, You can contact liurui directly. I guess there are some error configurations in your file. Thanks XuYi On 09/25/2019 11:04，Tian Jiang<[email protected]> wrote： Hi, When I used IoTDB-benchmark to perform insertions to IoTDB (both are the master branch), I got some really weird phenomenons. 1. This is my settings of the benchmark and I expected to have 14 threads to perform the insertion, while actually I only found 2 threads working. 2. I got a lot of failures when creating new time series, and the error code did not explain it well. Since I started the experiment with a clean IoTDB, I do not think this was caused by creating existing timeseries and I did not find related logs on the server side. 3. This may be related to issue2. In the first attempts of insertions, I got some errors indicating that the time series are not created successfully. These issues have blocked my progress of testing TTL, I hope someone could fix it ASAP. | | Tian Jiang | | [email protected] | 签名由网易邮箱大师定制
