[jira] [Commented] (IOTDB-1698) Record data set, data set query verification execution efficiency is slow
[ https://issues.apache.org/jira/browse/IOTDB-1698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17709600#comment-17709600 ] xiaozhihong commented on IOTDB-1698: If the large data volume performs correctness point-to-point verification, the current change is to use two databases to compare directly. > Record data set, data set query verification execution efficiency is slow > - > > Key: IOTDB-1698 > URL: https://issues.apache.org/jira/browse/IOTDB-1698 > Project: Apache IoTDB > Issue Type: Improvement > Components: Benchmark >Reporter: xiaozhihong >Assignee: Hongyin Zhang >Priority: Minor > > Execute steps:Take the record data set (locally generated TEXT file) as an > example > Step1: > Generate a certain amount of data using the function of generating data sets > (using out-of-order mode): it will take about half an hour to complete. > The configuration is as follows: > sg=20 > device=200 > sensor=300 > LOOP=8640 > BATCH_SIZE_PER_WRITE=100 > Use out-of-order mode 1, out-of-order 50% > The data points written by each sensor under each device are: 864000 > Step2: > Write the data set generated in the first step to IoTDB: it will take about > 1.5 hours to complete. > Step3: > Use the query mode to verify whether the data in IoTDB is consistent with the > records in the local TEXT. > Start query time: 2021-09-14 17:26:18,693 > Deadline: 2021-09-15 16:21:01,378-nearly 23 hours of execution, and the > progress is only 0.01% > Issue: > It is estimated that it will take nearly 10,000 days to complete the query, > which is time-consuming and serious > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Reopened] (IOTDB-5756) NPE when where predicate is NotEqualExpression and one of subExpression is not exist
[ https://issues.apache.org/jira/browse/IOTDB-5756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] 李伟豪 reopened IOTDB-5756: > NPE when where predicate is NotEqualExpression and one of subExpression is > not exist > > > Key: IOTDB-5756 > URL: https://issues.apache.org/jira/browse/IOTDB-5756 > Project: Apache IoTDB > Issue Type: Bug > Components: Core/Query >Reporter: 李伟豪 >Assignee: 李伟豪 >Priority: Major > Labels: pull-request-available > Attachments: image-2023-04-06-10-27-27-599.png, > image-2023-04-06-10-27-51-277.png > > > 复现sql: > insert into root.test.d1(time, s1) values (1, 1); > select s1 from root.test.d1 where s2!=0 > > !image-2023-04-06-10-27-27-599.png! > !image-2023-04-06-10-27-51-277.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-5735) The result of adding the distinct function to the align by device is incorrect.
[ https://issues.apache.org/jira/browse/IOTDB-5735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chao Wang reassigned IOTDB-5735: Assignee: 李伟豪 (was: Chao Wang) > The result of adding the distinct function to the align by device is > incorrect. > --- > > Key: IOTDB-5735 > URL: https://issues.apache.org/jira/browse/IOTDB-5735 > Project: Apache IoTDB > Issue Type: Bug > Components: mpp-cluster >Affects Versions: 1.0.0 >Reporter: Chao Wang >Assignee: 李伟豪 >Priority: Major > Attachments: image-2023-03-28-15-04-19-381.png, > image-2023-03-28-15-04-40-437.png, image-2023-04-07-09-58-52-009.png > > > Currently, a storage group can contain a maximum of five RegionGroups. Data > in different time periods of the same sequence is allocated to different > RegionGroups using hash algorithm. In this case, data of the same sequence is > stored in different Region Groups. > According to the execution plan of the distinct + align by device syntax, > distinct data is delivered to multiple region groups for execution and then > summarized and returned. During the summarization, distinct processing is not > performed. As a result, duplicate data exists between multiple region groups. > !image-2023-03-28-15-04-19-381.png! > !image-2023-03-28-15-04-40-437.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IOTDB-5735) The result of adding the distinct function to the align by device is incorrect.
[ https://issues.apache.org/jira/browse/IOTDB-5735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17709544#comment-17709544 ] Chao Wang commented on IOTDB-5735: -- !image-2023-04-07-09-58-52-009.png! > The result of adding the distinct function to the align by device is > incorrect. > --- > > Key: IOTDB-5735 > URL: https://issues.apache.org/jira/browse/IOTDB-5735 > Project: Apache IoTDB > Issue Type: Bug > Components: mpp-cluster >Affects Versions: 1.0.0 >Reporter: Chao Wang >Assignee: Chao Wang >Priority: Major > Attachments: image-2023-03-28-15-04-19-381.png, > image-2023-03-28-15-04-40-437.png, image-2023-04-07-09-58-52-009.png > > > Currently, a storage group can contain a maximum of five RegionGroups. Data > in different time periods of the same sequence is allocated to different > RegionGroups using hash algorithm. In this case, data of the same sequence is > stored in different Region Groups. > According to the execution plan of the distinct + align by device syntax, > distinct data is delivered to multiple region groups for execution and then > summarized and returned. During the summarization, distinct processing is not > performed. As a result, duplicate data exists between multiple region groups. > !image-2023-03-28-15-04-19-381.png! > !image-2023-03-28-15-04-40-437.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IOTDB-3804) When template turns on, mixing read and write, read takes precedence over write
[ https://issues.apache.org/jira/browse/IOTDB-3804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17709293#comment-17709293 ] xiaozhihong commented on IOTDB-3804: [https://github.com/thulab/iot-benchmark] commit cef5faa759512aa8545a46beb02cc33d88f5d010 I verified. > When template turns on, mixing read and write, read takes precedence over > write > --- > > Key: IOTDB-3804 > URL: https://issues.apache.org/jira/browse/IOTDB-3804 > Project: Apache IoTDB > Issue Type: Bug > Components: Benchmark >Reporter: xiaozhihong >Assignee: Hongyin Zhang >Priority: Major > Attachments: config.properties, image-2022-07-12-12-47-56-387.png, > image-2022-07-12-12-48-37-196.png > > > V0.13.X，after the template function is enabled, when reading and writing are > mixed, the program executes the read first and then executes the write, > resulting in ERROR. > !image-2022-07-12-12-48-37-196.png|width=756,height=383! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5761) Open channel of ShuffleSinkHandle after the drivertask begins
liaolanyu created IOTDB-5761: Summary: Open channel of ShuffleSinkHandle after the drivertask begins Key: IOTDB-5761 URL: https://issues.apache.org/jira/browse/IOTDB-5761 Project: Apache IoTDB Issue Type: Improvement Reporter: liaolanyu Assignee: liaolanyu Before this pr, if we meet Exceptions after construcing an Operator Tree, the memory reserved by ISinkChannel can not be properly freed, which may lead to failure of coming queries. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5760) Query is blocked because of no memory
Alima777 created IOTDB-5760: --- Summary: Query is blocked because of no memory Key: IOTDB-5760 URL: https://issues.apache.org/jira/browse/IOTDB-5760 Project: Apache IoTDB Issue Type: Bug Reporter: Alima777 Assignee: Alima777 When the task is finished, all dependency tasks are submitted. However, the data that finished task produces may not be consumed up. Therefore, we should only submit dependency tasks when the data is consumed up. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-5759) fix erratum of Spark-IoTDB's doc
[ https://issues.apache.org/jira/browse/IOTDB-5759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Ronaldo reassigned IOTDB-5759: --- Assignee: Xuan Ronaldo > fix erratum of Spark-IoTDB's doc > > > Key: IOTDB-5759 > URL: https://issues.apache.org/jira/browse/IOTDB-5759 > Project: Apache IoTDB > Issue Type: Bug > Components: Connectors/Spark-IoTDB >Reporter: Xuan Ronaldo >Assignee: Xuan Ronaldo >Priority: Major > > There are a couple of erratum in Spark-IoTDB's doc. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5759) fix erratum of Spark-IoTDB's doc
Xuan Ronaldo created IOTDB-5759: --- Summary: fix erratum of Spark-IoTDB's doc Key: IOTDB-5759 URL: https://issues.apache.org/jira/browse/IOTDB-5759 Project: Apache IoTDB Issue Type: Bug Components: Connectors/Spark-IoTDB Reporter: Xuan Ronaldo There are a couple of erratum in Spark-IoTDB's doc. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IOTDB-5570) [iotdb-metric] add a new metric of FULLGC
[ https://issues.apache.org/jira/browse/IOTDB-5570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17709248#comment-17709248 ] Qingxin Feng commented on IOTDB-5570: - 把所有发生的GC操作都找到，之后按照发生时间在监控图表中展示出来， 查看GC发生的间隔是在增加还是在缩短，来辅助分析。 > [iotdb-metric] add a new metric of FULLGC > - > > Key: IOTDB-5570 > URL: https://issues.apache.org/jira/browse/IOTDB-5570 > Project: Apache IoTDB > Issue Type: New Feature > Components: Others >Reporter: Qingxin Feng >Assignee: Hongyin Zhang >Priority: Minor > > > add a new metric of FULLGC > > 性能逐渐下降，这里面有一个因素是可能相关的，而且对于用户应该是长时间使用IoTDB以后会可能出现的问题，就是FullGC的频度。 > 能不能： > # grep日志拿出FullGC的记录； > # 计算出FullGC的间隔时间； > # 把#2中的间隔时间画出曲线，看看是不是有什么趋势（主要针对长测）； > # 如果有明显趋势，和测试性能对比看有没有相关性 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5758) Add missed check of node name in ClientRpcServiceImpl
liaolanyu created IOTDB-5758: Summary: Add missed check of node name in ClientRpcServiceImpl Key: IOTDB-5758 URL: https://issues.apache.org/jira/browse/IOTDB-5758 Project: Apache IoTDB Issue Type: Bug Reporter: liaolanyu Assignee: liaolanyu We missed the check of nodeName in Session interfaces when node name contains some special characters like "#". For example, node name like d#1 should be illegal. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-5552) No permissions when a non-root user inserts data into a timeseries with illegal path
[ https://issues.apache.org/jira/browse/IOTDB-5552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yuan Tian reassigned IOTDB-5552: Assignee: 李伟豪 (was: Hongyin Zhang) > No permissions when a non-root user inserts data into a timeseries with > illegal path > > > Key: IOTDB-5552 > URL: https://issues.apache.org/jira/browse/IOTDB-5552 > Project: Apache IoTDB > Issue Type: Bug >Affects Versions: 1.0.0 >Reporter: Haonan Hou >Assignee: 李伟豪 >Priority: Major > Attachments: image-2023-02-17-18-21-36-717.png, > image-2023-02-17-18-48-41-530.png > > > !image-2023-02-17-18-21-36-717.png|width=556,height=422! -- This message was sent by Atlassian Jira (v8.20.10#820010)
