[jira] [Commented] (IOTDB-1866) [Benchmark] Expanding read-write mixed scenarios
[ https://issues.apache.org/jira/browse/IOTDB-1866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17432158#comment-17432158 ] 张洪胤 commented on IOTDB-1866: I support this feature in [https://github.com/thulab/iotdb-benchmark/pull/212.] Just use IS_RECENT_QUERY to open. > [Benchmark] Expanding read-write mixed scenarios > > > Key: IOTDB-1866 > URL: https://issues.apache.org/jira/browse/IOTDB-1866 > Project: Apache IoTDB > Issue Type: Improvement > Components: Benchmark >Reporter: 张洪胤 >Assignee: 张洪胤 >Priority: Major > Original Estimate: 3h > Remaining Estimate: 3h > > Because of the requirements, benchmark need to support query recent data in > read-write mixed scenarios. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IOTDB-1864) Record the output result selection in CSV, but it does not take effect after serverMODE is started.
[ https://issues.apache.org/jira/browse/IOTDB-1864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17432157#comment-17432157 ] 张洪胤 commented on IOTDB-1864: I fix this problems in https://github.com/thulab/iotdb-benchmark/pull/210 > Record the output result selection in CSV, but it does not take effect after > serverMODE is started. > --- > > Key: IOTDB-1864 > URL: https://issues.apache.org/jira/browse/IOTDB-1864 > Project: Apache IoTDB > Issue Type: Bug > Components: Benchmark >Reporter: xiaozhihong >Assignee: 张洪胤 >Priority: Minor > > In ServerMode of IoTDB-Benchmark, it fails to record the result in csv. > How to recur this problem: > Step 1: > Modify config.properties of Benchmark: > `TEST_DATA_PERSISTENCE=CSV` > Step 2: > Start ser-benchmark.sh -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IOTDB-1867) [Benchmark] Error when set OPERATION_PROPORTION=1:x:x:x:x:x:x:x:x:x:x
[ https://issues.apache.org/jira/browse/IOTDB-1867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17432160#comment-17432160 ] 张洪胤 commented on IOTDB-1867: I fix this bug in master > [Benchmark] Error when set OPERATION_PROPORTION=1:x:x:x:x:x:x:x:x:x:x > - > > Key: IOTDB-1867 > URL: https://issues.apache.org/jira/browse/IOTDB-1867 > Project: Apache IoTDB > Issue Type: Bug > Components: Benchmark >Reporter: 张洪胤 >Assignee: 张洪胤 >Priority: Major > Original Estimate: 3h > Remaining Estimate: 3h > > Error happens when set OPERATION_PROPORTION=1:x:x:x:x:x:x:x:x:x:x, benchmark > will only write and not query -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IOTDB-1805) iotdb-grafana-connector docker image
[ https://issues.apache.org/jira/browse/IOTDB-1805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] 张洪胤 reassigned IOTDB-1805: -- Assignee: 张洪胤 > iotdb-grafana-connector docker image > > > Key: IOTDB-1805 > URL: https://issues.apache.org/jira/browse/IOTDB-1805 > Project: Apache IoTDB > Issue Type: Task >Reporter: Xiangdong Huang >Assignee: 张洪胤 >Priority: Major > Labels: pull-request-available > > From v0.12 on, iotdb-grafana-connector is not in apache/iotdb:-node > and apache/iotdb:-cluster. > Therefore, we need a new docker image, called apache/iotdb:-grafana -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-1843) log
刘珍 created IOTDB-1843: - Summary: log Key: IOTDB-1843 URL: https://issues.apache.org/jira/browse/IOTDB-1843 Project: Apache IoTDB Issue Type: Bug Reporter: 刘珍 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IOTDB-1864) Record the output result selection in CSV, but it does not take effect after serverMODE is started.
[ https://issues.apache.org/jira/browse/IOTDB-1864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] 张洪胤 reassigned IOTDB-1864: -- Assignee: 张洪胤 > Record the output result selection in CSV, but it does not take effect after > serverMODE is started. > --- > > Key: IOTDB-1864 > URL: https://issues.apache.org/jira/browse/IOTDB-1864 > Project: Apache IoTDB > Issue Type: Bug > Components: Benchmark >Reporter: xiaozhihong >Assignee: 张洪胤 >Priority: Minor > > In ServerMode of IoTDB-Benchmark, it fails to record the result in csv. > How to recur this problem: > Step 1: > Modify config.properties of Benchmark: > `TEST_DATA_PERSISTENCE=CSV` > Step 2: > Start ser-benchmark.sh -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IOTDB-1846) Count the total number of devices incorrectly in cluster module
[ https://issues.apache.org/jira/browse/IOTDB-1846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] 张洪胤 reassigned IOTDB-1846: -- Assignee: 张洪胤 > Count the total number of devices incorrectly in cluster module > --- > > Key: IOTDB-1846 > URL: https://issues.apache.org/jira/browse/IOTDB-1846 > Project: Apache IoTDB > Issue Type: Bug >Affects Versions: 0.12.2 >Reporter: Xinyu Tan >Assignee: 张洪胤 >Priority: Major > Attachments: image-2021-10-14-17-10-27-581.png > > > Testing found a bug where counting devices always returns 0 > !image-2021-10-14-17-10-27-581.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-1850) Compaction rate limiter become invalid when use deserialize page compaction
张凌哲 created IOTDB-1850: -- Summary: Compaction rate limiter become invalid when use deserialize page compaction Key: IOTDB-1850 URL: https://issues.apache.org/jira/browse/IOTDB-1850 Project: Apache IoTDB Issue Type: Bug Components: Core/Compaction Reporter: 张凌哲 Fix For: master branch, 0.12.2-SNAPSHOT Compaction rate limiter become invalid when use deserialize page compaction because the rate limiter of deserialize page compaction use wrong file size statistics -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-1750) 增强TsFileRewriteTool
周沛辰 created IOTDB-1750: -- Summary: 增强TsFileRewriteTool Key: IOTDB-1750 URL: https://issues.apache.org/jira/browse/IOTDB-1750 Project: Apache IoTDB Issue Type: Improvement Components: Tools/Others Reporter: 周沛辰 Assignee: 周沛辰 Fix For: 0.12.2-SNAPSHOT 增强TsFileRewriteTool类，实现读取mods文件并过滤掉删除的数据后进行重写，生成新的TsFile。 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Reopened] (IOTDB-1645) benchmark correctness check
[ https://issues.apache.org/jira/browse/IOTDB-1645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] 张洪胤 reopened IOTDB-1645: > benchmark correctness check > --- > > Key: IOTDB-1645 > URL: https://issues.apache.org/jira/browse/IOTDB-1645 > Project: Apache IoTDB > Issue Type: New Feature >Reporter: Hai Liu >Assignee: 张洪胤 >Priority: Major > Original Estimate: 24h > Remaining Estimate: 24h > > In this Problem, I optimize the logic of query generate and support point > verification between two database. The details are as follows. > # I modify the timestamp generate logic of Q1-Q10: timestamp increment for > each operation separately. > # I support point verification between two database: compare between each > other, use IS_POINT_COMPARISON to use this function. > # Add check of config: IS_COMPARISON and IS_POINT_COMPARISON only used in > double write mode and can't be both true > # And fix not aligned sensor for timescaleDB -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Reopened] (IOTDB-1734) [Benchmark]String value error of benchmark in generateMode
[ https://issues.apache.org/jira/browse/IOTDB-1734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] 张洪胤 reopened IOTDB-1734: > [Benchmark]String value error of benchmark in generateMode > -- > > Key: IOTDB-1734 > URL: https://issues.apache.org/jira/browse/IOTDB-1734 > Project: Apache IoTDB > Issue Type: Improvement > Components: Benchmark >Reporter: 张洪胤 >Assignee: 张洪胤 >Priority: Major > Original Estimate: 3h > Remaining Estimate: 3h > > Now I use blank as delimiter in data txt, so error will happen if there is > blank in string value. > I will fix this bug by changing file format from txt to csv. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Reopened] (IOTDB-1735) [Benchmark]Optimize for verificationQuery Mode
[ https://issues.apache.org/jira/browse/IOTDB-1735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] 张洪胤 reopened IOTDB-1735: > [Benchmark]Optimize for verificationQuery Mode > -- > > Key: IOTDB-1735 > URL: https://issues.apache.org/jira/browse/IOTDB-1735 > Project: Apache IoTDB > Issue Type: Improvement > Components: Benchmark >Reporter: 张洪胤 >Assignee: 张洪胤 >Priority: Major > Original Estimate: 3h > Remaining Estimate: 3h > > Because of the speed in VerificationMode is too slow, I optimize this query > which can get all data in one time for a batch. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-1779) The network of one node is unreachable，write blocking problem for three node three replica cluster
刘珍 created IOTDB-1779:
-
Summary: The network of one node is unreachable，write blocking
problem for three node three replica cluster
Key: IOTDB-1779
URL: https://issues.apache.org/jira/browse/IOTDB-1779
Project: Apache IoTDB
Issue Type: Improvement
Components: Core/Cluster
Reporter: 刘珍
Attachments: 3节点3副本_拔网线_测试结果.docx, image-2021-09-29-15-49-33-180.png,
image-2021-09-29-15-49-44-405.png, image-2021-09-29-15-51-24-108.png,
拔网线_v12_config.properties
master 87e1ae444523c07b66b7bde1ec63d6b1924e3fca
Three node three replica cluster，benchmark connects a node to write sequential
data，remove the network cable from one node，Iotdb has the following problems：
（3节点3副本集群，benchmark连接其中1个节点写入顺序数据，拔掉其他节点的网线火停止其他节点的网络服务--每次操作只影响1个节点，iotdb有如下几个问题）：
1. Symptom of pulling out a network cable（拔网线的表现）
问题1：Benchmark got exception (benchmark写入异常）：
org.apache.iotdb.rpc.StatementExecutionException: {color:#DE350B}701: Request
timed out.{color}
org.apache.iotdb.rpc.StatementExecutionException: 702:{color:#DE350B}* Leader
cannot be found.*{color}
cli 执行insert ：
问题2：cli执行select耗时120秒：
!image-2021-09-29-15-49-33-180.png!
问题3：node status 耗时120多秒
!image-2021-09-29-15-49-44-405.png!
问题4：插上网线，网络恢复后
Benchmark依然报错：
org.apache.iotdb.rpc.IoTDBConnectionException: Fail to reconnect to server.
Please check server status
停止网络服务（systemctl stop network）
benchmark写入报同样的错误：
org.apache.iotdb.rpc.IoTDBConnectionException: Fail to reconnect to server.
Please check server status
但是命令行方式停止网络服务期间，cli 执行insert，select正常：
insert into root.net.dev(col) values(now(),3);
insert into root.net.dev(col) values(now(),4);
insert into root.net.dev(col) values(now(),5);
select * from root.net.dev;
!image-2021-09-29-15-51-24-108.png!
详细结果见附件。
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IOTDB-1782) cluster : “DataMemberReport " log information should not be in debug logs & Print only when the node role changes
刘珍 created IOTDB-1782:
-
Summary: cluster : “DataMemberReport " log information should not
be in debug logs & Print only when the node role changes
Key: IOTDB-1782
URL: https://issues.apache.org/jira/browse/IOTDB-1782
Project: Apache IoTDB
Issue Type: Improvement
Components: Core/Cluster
Reporter: 刘珍
cluster : “DataMemberReport " log information should not be in debug logs
Print only when the node role changes
集群版本的“DataMemberReport "日志不应该放到debug日志中，这个信息很重要，需要查看各data节点信息，LEADER 还是FOLLOWER
{color:#DE350B}*信息不要刷屏*{color}，{color:#DE350B}*只需要在节点角色变更的时候打印日志。*{color}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IOTDB-1783) cluster：./sbin/nodetool.sh displays information about nodes in the Data raft group
刘珍 created IOTDB-1783:
-
Summary: cluster：./sbin/nodetool.sh displays information about
nodes in the Data raft group
Key: IOTDB-1783
URL: https://issues.apache.org/jira/browse/IOTDB-1783
Project: Apache IoTDB
Issue Type: Improvement
Components: Core/Cluster
Reporter: 刘珍
./sbin/nodetool.sh displays information about nodes in the data raft group
集群：
./sbin/nodetool.sh{color:#DE350B}*工具需要支持打印所有data raft 组各节点信息*{color}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IOTDB-1784) [Benchmark]No record of config when use csv record mode
[ https://issues.apache.org/jira/browse/IOTDB-1784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17422553#comment-17422553 ] 张洪胤 commented on IOTDB-1784: I Fix this bug in :https://github.com/thulab/iotdb-benchmark/pull/200 > [Benchmark]No record of config when use csv record mode > --- > > Key: IOTDB-1784 > URL: https://issues.apache.org/jira/browse/IOTDB-1784 > Project: Apache IoTDB > Issue Type: Bug > Components: Benchmark >Reporter: 张洪胤 >Assignee: 张洪胤 >Priority: Major > Original Estimate: 3h > Remaining Estimate: 3h > > When use csv record mode, There is nothing in conf.csv file -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-1784) [Benchmark]No record of config when use csv record mode
张洪胤 created IOTDB-1784: -- Summary: [Benchmark]No record of config when use csv record mode Key: IOTDB-1784 URL: https://issues.apache.org/jira/browse/IOTDB-1784 Project: Apache IoTDB Issue Type: Bug Components: Benchmark Reporter: 张洪胤 Assignee: 张洪胤 When use csv record mode, There is nothing in conf.csv file -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-1787) The Implementation of benchmark of influxdb 2.0
张洪胤 created IOTDB-1787: -- Summary: The Implementation of benchmark of influxdb 2.0 Key: IOTDB-1787 URL: https://issues.apache.org/jira/browse/IOTDB-1787 Project: Apache IoTDB Issue Type: Improvement Components: Benchmark Reporter: 张洪胤 There are some users request us to check whether use influxdb client or HTTP or Apache的PoolingHttpClientConnectionManager is better. From my perspective, I think this should have a research and experiment. The issue: https://github.com/thulab/iotdb-benchmark/issues/187 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-1788) There maybe some problem in Q4 in benchmark(opentsdb)
张洪胤 created IOTDB-1788: -- Summary: There maybe some problem in Q4 in benchmark(opentsdb) Key: IOTDB-1788 URL: https://issues.apache.org/jira/browse/IOTDB-1788 Project: Apache IoTDB Issue Type: Bug Components: Benchmark Reporter: 张洪胤 The issue: https://github.com/thulab/iotdb-benchmark/issues/201 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IOTDB-1794) Node.js Client
[ https://issues.apache.org/jira/browse/IOTDB-1794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] 张凌哲 reassigned IOTDB-1794: -- Assignee: 张凌哲 > Node.js Client > -- > > Key: IOTDB-1794 > URL: https://issues.apache.org/jira/browse/IOTDB-1794 > Project: Apache IoTDB > Issue Type: Improvement > Components: Client/Others >Reporter: 张凌哲 >Assignee: 张凌哲 >Priority: Major > > We need node.js client for node.js users -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-1794) Node.js Client
张凌哲 created IOTDB-1794: -- Summary: Node.js Client Key: IOTDB-1794 URL: https://issues.apache.org/jira/browse/IOTDB-1794 Project: Apache IoTDB Issue Type: Improvement Components: Client/Others Reporter: 张凌哲 We need node.js client for node.js users -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-1795) [Benchmark]Errors that may be caused by using http requests
张洪胤 created IOTDB-1795: -- Summary: [Benchmark]Errors that may be caused by using http requests Key: IOTDB-1795 URL: https://issues.apache.org/jira/browse/IOTDB-1795 Project: Apache IoTDB Issue Type: Bug Components: Benchmark Reporter: 张洪胤 The issue: https://github.com/thulab/iotdb-benchmark/issues/203 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IOTDB-1735) [Benchmark]Optimize for verificationQuery Mode
[ https://issues.apache.org/jira/browse/IOTDB-1735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] 张洪胤 reassigned IOTDB-1735: -- Assignee: 张洪胤 > [Benchmark]Optimize for verificationQuery Mode > -- > > Key: IOTDB-1735 > URL: https://issues.apache.org/jira/browse/IOTDB-1735 > Project: Apache IoTDB > Issue Type: Improvement >Reporter: 张洪胤 >Assignee: 张洪胤 >Priority: Major > Original Estimate: 3h > Remaining Estimate: 3h > > Because of the speed in VerificationMode is too slow, I optimize this query > which can get all data in one time for a batch. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-1735) [Benchmark]Optimize for verificationQuery Mode
张洪胤 created IOTDB-1735: -- Summary: [Benchmark]Optimize for verificationQuery Mode Key: IOTDB-1735 URL: https://issues.apache.org/jira/browse/IOTDB-1735 Project: Apache IoTDB Issue Type: Improvement Reporter: 张洪胤 Because of the speed in VerificationMode is too slow, I optimize this query which can get all data in one time for a batch. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-1734) [Benchmark]String value error of benchmark in generateMode
张洪胤 created IOTDB-1734: -- Summary: [Benchmark]String value error of benchmark in generateMode Key: IOTDB-1734 URL: https://issues.apache.org/jira/browse/IOTDB-1734 Project: Apache IoTDB Issue Type: Improvement Components: Benchmark Reporter: 张洪胤 Assignee: 张洪胤 Now I use blank as delimiter in data txt, so error will happen if there is blank in string value. I will fix this bug by changing file format from txt to csv. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IOTDB-1701) The naming rules of the tested database need to be unified (all uppercase is recommended)
[ https://issues.apache.org/jira/browse/IOTDB-1701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] 张洪胤 reassigned IOTDB-1701: -- Assignee: 张洪胤 > The naming rules of the tested database need to be unified (all uppercase is > recommended) > - > > Key: IOTDB-1701 > URL: https://issues.apache.org/jira/browse/IOTDB-1701 > Project: Apache IoTDB > Issue Type: Improvement > Components: Benchmark >Reporter: xiaozhihong >Assignee: 张洪胤 >Priority: Minor > > The current part of the database name has both uppercase and lowercase > letters, which is too cumbersome. > Such as,DB_SWITCH=IoTDB-012-SESSION_BY_TABLET；DB_SWITCH=InfluxDB -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-1876) enable_partition ： higher write latency （14%） than “disable_partition”
刘珍 created IOTDB-1876: - Summary: enable_partition ： higher write latency （14%） than “disable_partition” Key: IOTDB-1876 URL: https://issues.apache.org/jira/browse/IOTDB-1876 Project: Apache IoTDB Issue Type: Improvement Components: Core/Server Reporter: 刘珍 Attachments: image-2021-10-22-16-45-41-437.png, 配置参数.zip rel/0.12 ( 0.12.3 rc1) !image-2021-10-22-16-45-41-437.png! Write only. All written is sequential data. 只有写入操作，写入的数据为顺序数据。 10天1个分区，开分区写入延迟比不使用分区高14%。 配置文件见附件。 benchmark and iotdb's configuration files are attached. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IOTDB-1878) After benchmark reconstruction, the output results are persisted to IoTDB, and the benchmark reports Connection Error
[ https://issues.apache.org/jira/browse/IOTDB-1878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] 张洪胤 reassigned IOTDB-1878: -- Assignee: 张洪胤 > After benchmark reconstruction, the output results are persisted to IoTDB, > and the benchmark reports Connection Error > - > > Key: IOTDB-1878 > URL: https://issues.apache.org/jira/browse/IOTDB-1878 > Project: Apache IoTDB > Issue Type: Bug > Components: Benchmark >Reporter: xiaozhihong >Assignee: 张洪胤 >Priority: Major > Attachments: config.properties > > > The steps to reproduce the problem are as follows: > 1. Start IoTDB server > 2.Modify config in benchmark > 3.Execute benchmark.sh > 4. View log in Benchmark -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-2077) master - Raw data query without value filtering（“limit 1” ） got an error log
刘珍 created IOTDB-2077:
-
Summary: master - Raw data query without value filtering（“limit
1” ） got an error log
Key: IOTDB-2077
URL: https://issues.apache.org/jira/browse/IOTDB-2077
Project: Apache IoTDB
Issue Type: Bug
Components: Core/Query
Affects Versions: master branch
Reporter: 刘珍
Attachments: q.sh
master 521f5626297e834049e8f8af94bac09ede3b8143
1. Run q.sh (See the attachment)
2. ./sbin/start-cli.sh -e "select s_0 from root.ip5.ip50.d_10
{color:#DE350B}*limit 1*{color}"
2021-12-01 14:20:18,743 [pool-15-IoTDB-Query-5] ERROR
o.a.i.d.q.d.RawQueryDataSetWithoutValueFilter$ReadTask:126 - Something gets
wrong while reading from the series reader root.ip5.ip50.d_10.s_0:
java.io.IOException: no next page, neither non-overlapped nor overlapped
at
org.apache.iotdb.db.query.reader.series.SeriesReader.nextPage(SeriesReader.java:701)
at
org.apache.iotdb.db.query.reader.series.SeriesRawDataBatchReader.readPageData(SeriesRawDataBatchReader.java:181)
at
org.apache.iotdb.db.query.reader.series.SeriesRawDataBatchReader.hasNextBatch(SeriesRawDataBatchReader.java:111)
at
org.apache.iotdb.db.query.dataset.RawQueryDataSetWithoutValueFilter$ReadTask.runMayThrow(RawQueryDataSetWithoutValueFilter.java:83)
at
org.apache.iotdb.db.concurrent.WrappedRunnable.run(WrappedRunnable.java:32)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (IOTDB-2236) When read-only occurs, “set system to writable” is executed. No log_all.log file is generated,, and “kill query” does not work
刘珍 created IOTDB-2236: - Summary: When read-only occurs, “set system to writable” is executed. No log_all.log file is generated,, and “kill query” does not work Key: IOTDB-2236 URL: https://issues.apache.org/jira/browse/IOTDB-2236 Project: Apache IoTDB Issue Type: Bug Components: Core/Server Reporter: 刘珍 Attachments: screenshot-1.png 0.12.4 rc1 1. long test：No space left on device，iotdb read-only 2. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (IOTDB-2218) [Benchmark] NPE when in verificationQueryMode
张洪胤 created IOTDB-2218: -- Summary: [Benchmark] NPE when in verificationQueryMode Key: IOTDB-2218 URL: https://issues.apache.org/jira/browse/IOTDB-2218 Project: Apache IoTDB Issue Type: Bug Reporter: 张洪胤 Assignee: 张洪胤 Because of previous modify of session, there are NPE when in verificationQueryMode. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (IOTDB-2242) [Benchmark] Optimize verification mode in big mount data
张洪胤 created IOTDB-2242: -- Summary: [Benchmark] Optimize verification mode in big mount data Key: IOTDB-2242 URL: https://issues.apache.org/jira/browse/IOTDB-2242 Project: Apache IoTDB Issue Type: Improvement Components: Benchmark Reporter: 张洪胤 Assignee: 张洪胤 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (IOTDB-2242) [Benchmark] Optimize verification mode in big mount data
[ https://issues.apache.org/jira/browse/IOTDB-2242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17467540#comment-17467540 ] 张洪胤 commented on IOTDB-2242: I will optimize on PR: https://github.com/thulab/iotdb-benchmark/pull/235 > [Benchmark] Optimize verification mode in big mount data > > > Key: IOTDB-2242 > URL: https://issues.apache.org/jira/browse/IOTDB-2242 > Project: Apache IoTDB > Issue Type: Improvement > Components: Benchmark >Reporter: 张洪胤 >Assignee: 张洪胤 >Priority: Major > Original Estimate: 72h > Remaining Estimate: 72h > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (IOTDB-2262) [Aligned timeseries] select .. into need to support aligned
刘珍 created IOTDB-2262: - Summary: [Aligned timeseries] select .. into need to support aligned Key: IOTDB-2262 URL: https://issues.apache.org/jira/browse/IOTDB-2262 Project: Apache IoTDB Issue Type: Bug Reporter: 刘珍 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (IOTDB-2263) [Aligned timeseries] insert into aligned timeseries without aligned , operation is successful
刘珍 created IOTDB-2263: - Summary: [Aligned timeseries] insert into aligned timeseries without aligned , operation is successful Key: IOTDB-2263 URL: https://issues.apache.org/jira/browse/IOTDB-2263 Project: Apache IoTDB Issue Type: Bug Components: Core/Server Reporter: 刘珍 CREATE ALIGNED TIMESERIES root.ln.wf01.GPS(latitude FLOAT encoding=PLAIN compressor=SNAPPY, longitude FLOAT encoding=PLAIN compressor=SNAPPY); insert into root.ln.wf01.GPS(time,latitude,longitude ) values(1,111.2,222.8); //insert应该报错 select * from root.ln.wf01.GPS Msg: 500: [INTERNAL_SERVER_ERROR(500)] Exception occurred: "select * from root.ln.wf01.GPS". executeStatement failed. org.apache.iotdb.db.exception.query.QueryProcessException: Meet error when init series reader. error 日志： 2022-01-04 11:00:35,969 [pool-17-IoTDB-Query-2] ERROR o.a.i.d.q.e.RawDataQueryExecutor:132 - Meet error when init series reader java.lang.ClassCastException: org.apache.iotdb.db.engine.memtable.WritableMemChunkGroup cannot be cast to org.apache.iotdb.db.engine.memtable.AlignedWritableMemChunkGroup at org.apache.iotdb.db.metadata.path.AlignedPath.getReadOnlyMemChunkFromMemTable(AlignedPath.java:381) at org.apache.iotdb.db.engine.memtable.AbstractMemTable.query(AbstractMemTable.java:409) at org.apache.iotdb.db.engine.storagegroup.TsFileProcessor.query(TsFileProcessor.java:1289) at org.apache.iotdb.db.engine.storagegroup.VirtualStorageGroupProcessor.getFileResourceListForQuery(VirtualStorageGroupProcessor.java:1840) at org.apache.iotdb.db.engine.storagegroup.VirtualStorageGroupProcessor.query(VirtualStorageGroupProcessor.java:1729) at org.apache.iotdb.db.engine.StorageEngine.query(StorageEngine.java:792) at org.apache.iotdb.db.query.control.QueryResourceManager.getQueryDataSource(QueryResourceManager.java:95) at org.apache.iotdb.db.query.executor.RawDataQueryExecutor.initManagedSeriesReader(RawDataQueryExecutor.java:115) at org.apache.iotdb.db.query.executor.RawDataQueryExecutor.executeWithoutValueFilter(RawDataQueryExecutor.java:72) at org.apache.iotdb.db.query.executor.QueryRouter.rawDataQuery(QueryRouter.java:110) at org.apache.iotdb.db.qp.executor.PlanExecutor.processDataQuery(PlanExecutor.java:622) at org.apache.iotdb.db.qp.executor.PlanExecutor.processQuery(PlanExecutor.java:252) at org.apache.iotdb.db.service.basic.BasicServiceProvider.createQueryDataSet(BasicServiceProvider.java:243) at org.apache.iotdb.db.service.thrift.impl.TSServiceImpl.executeQueryPlan(TSServiceImpl.java:725) at org.apache.iotdb.db.service.thrift.impl.TSServiceImpl.access$200(TSServiceImpl.java:152) at org.apache.iotdb.db.service.thrift.impl.TSServiceImpl$QueryTask.call(TSServiceImpl.java:209) at org.apa -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (IOTDB-2271) [Aligned timeseries] Creating an unaligned timeseries under the aligned timeseries owning device succeeded
刘珍 created IOTDB-2271:
-
Summary: [Aligned timeseries] Creating an unaligned timeseries
under the aligned timeseries owning device succeeded
Key: IOTDB-2271
URL: https://issues.apache.org/jira/browse/IOTDB-2271
Project: Apache IoTDB
Issue Type: Bug
Components: Core/Server
Affects Versions: 0.13.0
Reporter: 刘珍
Attachments: image-2022-01-05-16-16-46-143.png
在对齐时序所属设备下创建非对齐时序，期望失败，实际成功。
Delete storage group root.lz;
CREATE ALIGNED TIMESERIES root.lz.dev.GPS(latitude INT32 encoding=PLAIN
compressor=SNAPPY, longitude INT32 encoding=PLAIN compressor=SNAPPY) ;
CREATE TIMESERIES root.lz.dev.GPS.noalign_ts_tag with datatype=INT32
tags(tag1=v1, tag2=v2) attributes(attr1=v1, attr2=v2);
show timeseries root.lz.dev.GPS.*
+--+-+-+++---+-+---+
|timeseries|alias|storage
group|dataType|encoding|compression| tags|
attributes|
+--+-+-+++---+-+---+
|root.lz.dev.GPS.noalign_ts_tag| null| root.lz| INT32| RLE|
SNAPPY|{"tag1":"v1","tag2":"v2"}|{"attr2":"v2","attr1":"v1"}|
| root.lz.dev.GPS.latitude| null| root.lz| INT32| PLAIN|
SNAPPY| null| null|
| root.lz.dev.GPS.longitude| null| root.lz| INT32| PLAIN|
SNAPPY| null| null|
+--+-+-+++---+-+---+
Total line number = 3
https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=181307906
!image-2022-01-05-16-16-46-143.png!
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (IOTDB-2266) [start-cli.sh]"WARNING: Unable to create a system terminal"
刘珍 created IOTDB-2266: - Summary: [start-cli.sh]"WARNING: Unable to create a system terminal" Key: IOTDB-2266 URL: https://issues.apache.org/jira/browse/IOTDB-2266 Project: Apache IoTDB Issue Type: Bug Components: Tools/Others Affects Versions: 0.13.0 Reporter: 刘珍 master 010af34dda85847b249775f7241e06594a740b9f [cluster@i-r0x6sjak db_master_0104]$ ./sbin/start-cli.sh -e "show devices"|grep root Jan 05, 2022 2:02:32 PM org.jline.utils.Log logr WARNING: Unable to create a system terminal, creating a dumb terminal (enable debug logging for more information) WARNING 信息处理去掉？ -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (IOTDB-2264) [Aligned timeseries] load tsfile with aligned timeseries failed
刘珍 created IOTDB-2264: - Summary: [Aligned timeseries] load tsfile with aligned timeseries failed Key: IOTDB-2264 URL: https://issues.apache.org/jira/browse/IOTDB-2264 Project: Apache IoTDB Issue Type: Bug Components: Tools/Others Affects Versions: 0.13.0 Reporter: 刘珍 load包含对齐时序数据的tsfile失败： ./sbin/start-cli.sh -e "load './data_for_load' autoregister=false" Msg: 411: Cannot load file /data/iotdb/db_master_0104/./data_for_load/1641288670353-1-0-0.tsfile because root.lz.dev.person. is not a legal path 日志： 2022-01-05 11:10:04,994 [pool-12-IoTDB-RPC-Client-2] ERROR o.a.i.d.q.e.PlanExecutor:1210 - fail to load file 1641288670353-1-0-0.tsfile org.apache.iotdb.db.exception.metadata.IllegalPathException: root.lz.dev.person. is not a legal path at org.apache.iotdb.db.metadata.utils.MetaUtils.splitPathToDetachedPath(MetaUtils.java:60) at org.apache.iotdb.db.metadata.path.PartialPath.(PartialPath.java:80) at org.apache.iotdb.db.qp.executor.PlanExecutor.loadNewTsFileVerifyMetadata(PlanExecutor.java:1228) at org.apache.iotdb.db.qp.executor.PlanExecutor.loadFile(PlanExecutor.java:1169) at org.apache.iotdb.db.qp.executor.PlanExecutor.loadDir(PlanExecutor.java:1138) at org.apache.iotdb.db.qp.executor.PlanExecutor.operateLoadFiles(PlanExecutor.java:1108) at org.apache.iotdb.db.qp.executor.PlanExecutor.processNonQuery(PlanExecutor.java:322) at org.apache.iotdb.db.service.basic.BasicServiceProvider.executeNonQuery(BasicServiceProvider.java:257) at org.apache.iotdb.db.service.thrift.impl.TSServiceImpl.executeNonQueryPlan(TSServiceImpl.java:1900) at org.apache.iotdb.db.service.thrift.impl.TSServiceImpl.executeNonQueryStatement(TSServiceImpl.java:1049) at org.apache.iotdb.db.service.thrift.impl.TSServiceImpl.executeUpdateStatement(TSServiceImpl.java:1042) at org.apache.iotdb.db.service.thrift.impl.TSServiceImpl.executeStatement(TSServiceImpl.java:552) at org.apache.iotdb.service.rpc.thrift.TSIService$Processor$executeStatement.getResult(TSIService.java:2733) at org.apache.iotdb.service.rpc.thrift.TSIService$Processor$executeStatement.getResult(TSIService.java:2713) at org.apache.thrift.ProcessFunction.process(ProcessFunction.java:38) at org.apache.thrift.TBaseProcessor.process(TBaseProcessor.java:38) at org.apache.thrift.server.TThreadPoolServer$WorkerProcess.run(TThreadPoolServer.java:248) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (IOTDB-2273) [Trigger] Examples in the document：alert-listener-sg1d1s1 ，double quotation marks are required
刘珍 created IOTDB-2273: - Summary: [Trigger] Examples in the document：alert-listener-sg1d1s1 ，double quotation marks are required Key: IOTDB-2273 URL: https://issues.apache.org/jira/browse/IOTDB-2273 Project: Apache IoTDB Issue Type: Bug Components: Document Affects Versions: 0.13.0 Reporter: 刘珍 Attachments: image-2022-01-05-19-21-42-907.png https://iotdb.apache.org/zh/UserGuide/Master/Advanced-Features/Triggers.html alert-listener-sg1d1s1触发器名字包含- ，需要加双引号。 !image-2022-01-05-19-21-42-907.png! -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (IOTDB-2194) [cluster] SHOW TIMESERIES will only display 2000 timeseries
[ https://issues.apache.org/jira/browse/IOTDB-2194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17464419#comment-17464419 ] 张洪胤 commented on IOTDB-2194: Fix this problem on https://github.com/apache/iotdb/pull/4627 > [cluster] SHOW TIMESERIES will only display 2000 timeseries > --- > > Key: IOTDB-2194 > URL: https://issues.apache.org/jira/browse/IOTDB-2194 > Project: Apache IoTDB > Issue Type: Bug >Reporter: 张洪胤 >Assignee: 张洪胤 >Priority: Major > Fix For: 0.12.4 > > Original Estimate: 3h > Remaining Estimate: 3h > > In current cluster version, if we have more than 2,000 timeseries, when we > commend SHOW TIMESERIES, it will only display 2,000 timeseries, the same as > the SHOW DEVICES... > This problem is fixed on master branch, but not cherry-pick to rel/0.12 > > Related PR: https://github.com/apache/iotdb/pull/2958 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (IOTDB-2194) [cluster] SHOW TIMESERIES will only display 2000 timeseries
张洪胤 created IOTDB-2194: -- Summary: [cluster] SHOW TIMESERIES will only display 2000 timeseries Key: IOTDB-2194 URL: https://issues.apache.org/jira/browse/IOTDB-2194 Project: Apache IoTDB Issue Type: Bug Reporter: 张洪胤 Assignee: 张洪胤 Fix For: 0.12.4 In current cluster version, if we have more than 2,000 timeseries, when we commend SHOW TIMESERIES, it will only display 2,000 timeseries, the same as the SHOW DEVICES... This problem is fixed on master branch, but not cherry-pick to rel/0.12 Related PR: https://github.com/apache/iotdb/pull/2958 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (IOTDB-2230) The final result matrix numerical calculations performed by Benchmark need to be annotated in the Readme
[ https://issues.apache.org/jira/browse/IOTDB-2230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] 张洪胤 reassigned IOTDB-2230: -- Assignee: 张洪胤 > The final result matrix numerical calculations performed by Benchmark need to > be annotated in the Readme > > > Key: IOTDB-2230 > URL: https://issues.apache.org/jira/browse/IOTDB-2230 > Project: Apache IoTDB > Issue Type: Improvement > Components: Benchmark >Reporter: xiaozhihong >Assignee: 张洪胤 >Priority: Major > > Currently in readme, there is no detailed description of numerical > calculation of OkOperation and okPoint in the result matrix, which will make > people confused about how to calculate, need to be added -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (IOTDB-2231) Improved the ability of Benchmark to count all data points when performing precise point queries
[ https://issues.apache.org/jira/browse/IOTDB-2231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] 张洪胤 reassigned IOTDB-2231: -- Assignee: 张洪胤 > Improved the ability of Benchmark to count all data points when performing > precise point queries > > > Key: IOTDB-2231 > URL: https://issues.apache.org/jira/browse/IOTDB-2231 > Project: Apache IoTDB > Issue Type: Improvement > Components: Benchmark >Reporter: xiaozhihong >Assignee: 张洪胤 >Priority: Major > > When Benchmark performs precise point-only query, the result matrix only > displays the data points of one sensor under one device, and does not count > all the data points. This function needs to be improved -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (IOTDB-2226) The query function of LIMIT, OFFSET, OFFSET and SOFSET control in the Benchmark configuration file is not implemented
[ https://issues.apache.org/jira/browse/IOTDB-2226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] 张洪胤 reassigned IOTDB-2226: -- Assignee: 张洪胤 > The query function of LIMIT, OFFSET, OFFSET and SOFSET control in the > Benchmark configuration file is not implemented > - > > Key: IOTDB-2226 > URL: https://issues.apache.org/jira/browse/IOTDB-2226 > Project: Apache IoTDB > Issue Type: New Feature > Components: Benchmark >Reporter: xiaozhihong >Assignee: 张洪胤 >Priority: Minor > > In the Benchmark configuration file, the parameter function of the following > configuration is not implemented,such as: > # 条件查询中结果输出项的最大数量 > QUERY_LIMIT_N=5 > # 条件查询中含有Limit子句的偏移量 > QUERY_LIMIT_OFFSET=5 > # 条件查询结果输出序列的最大数量 > QUERY_SLIMIT_N=5 > # 条件查询结果输出序列的偏移量 > QUERY_SLIMIT_OFFSET=5 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (IOTDB-2218) [Benchmark] NPE when in verificationQueryMode
[ https://issues.apache.org/jira/browse/IOTDB-2218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17466710#comment-17466710 ] 张洪胤 commented on IOTDB-2218: This Problem is also fixed > [Benchmark] NPE when in verificationQueryMode > - > > Key: IOTDB-2218 > URL: https://issues.apache.org/jira/browse/IOTDB-2218 > Project: Apache IoTDB > Issue Type: Bug >Reporter: 张洪胤 >Assignee: 张洪胤 >Priority: Major > Original Estimate: 12h > Remaining Estimate: 12h > > Because of previous modify of session, there are NPE when in > verificationQueryMode. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (IOTDB-2251) There are no response for iotdb when use large offset to query
张洪胤 created IOTDB-2251: -- Summary: There are no response for iotdb when use large offset to query Key: IOTDB-2251 URL: https://issues.apache.org/jira/browse/IOTDB-2251 Project: Apache IoTDB Issue Type: Bug Reporter: 张洪胤 Data config: There are 10 devices in 5 storage groups, each has 30 sensors. And there are 1,000,000 timeseries per device. Query SQL: select * from root.test.g_0.d_0 offset 40 limit 500. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (IOTDB-2249) [Aligned timeseries] Delete from “one column of aligned timeseries ，“ select * NPE
刘珍 created IOTDB-2249:
-
Summary: [Aligned timeseries] Delete from “one column of aligned
timeseries ，“ select * NPE
Key: IOTDB-2249
URL: https://issues.apache.org/jira/browse/IOTDB-2249
Project: Apache IoTDB
Issue Type: Bug
Components: Core/Server
Reporter: 刘珍
master ：
1. 测试用例
CREATE ALIGNED TIMESERIES root.lz.dev.GPS(latitude FLOAT encoding=PLAIN
compressor=SNAPPY, longitude FLOAT encoding=PLAIN compressor=SNAPPY)
insert into root.lz.dev.GPS(time,latitude,longitude ) aligned values(9,3.2,9.8);
insert into root.lz.dev.GPS(time,latitude ) aligned values(11,4.5);
insert into root.lz.dev.GPS(time,longitude ) aligned values(11,6.7);
select * from root.lz.dev.GPS
delete from root.lz.dev.GPS.latitude;
IoTDB> select * from root.lz.dev.GPS
{color:#DE350B}Msg: 500: [INTERNAL_SERVER_ERROR(500)] Exception occurred:
"select * from root.lz.dev.GPS". executeStatement failed.
java.lang.NullPointerException{color}
error日志：
2022-01-04 11:51:28,727 [pool-17-IoTDB-Query-4] ERROR
{color:#DE350B}*o.a.i.d.q.d.RawQueryDataSetWithoutValueFilter:558 - exception
happened in producer thread
java.lang.NullPointerException: null*{color}
at
org.apache.iotdb.db.utils.datastructure.AlignedTVList.getAlignedValueByValueIndex(AlignedTVList.java:191)
at
org.apache.iotdb.db.utils.datastructure.AlignedTVList.getAlignedValue(AlignedTVList.java:160)
at
org.apache.iotdb.db.utils.datastructure.AlignedTVList.getTimeValuePairForTimeDuplicatedRows(AlignedTVList.java:712)
at
org.apache.iotdb.db.utils.datastructure.AlignedTVList$AlignedIte.hasNextTimeValuePair(AlignedTVList.java:951)
at
org.apache.iotdb.db.query.reader.chunk.MemAlignedPageReader.getAllSatisfiedPageData(MemAlignedPageReader.java:57)
at
org.apache.iotdb.db.query.reader.series.SeriesReader$VersionPageReader.getAllSatisfiedPageData(SeriesReader.java:1140)
at
org.apache.iotdb.db.query.reader.series.SeriesReader.nextPage(SeriesReader.java:712)
at
org.apache.iotdb.db.query.reader.series.SeriesRawDataBatchReader.readPageData(SeriesRawDataBatchReader.java:180)
at
org.apache.iotdb.db.query.reader.series.SeriesRawDataBatchReader.readChunkData(SeriesRawDataBatchReader.java:171)
at
org.apache.iotdb.db.query.reader.series.SeriesRawDataBatchReader.hasNextBatch(SeriesRawDataBatchReader.java:118)
at
org.apache.iotdb.db.query.dataset.RawQueryDataSetWithoutValueFilter$ReadTask.runMayThrow(RawQueryDataSetWithoutValueFilter.java:96)
at
org.apache.iotdb.db.concurrent.WrappedRunnable.run(WrappedRunnable.java:32)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (IOTDB-2252) There are no response when select * from device by jdbc.
张洪胤 created IOTDB-2252: -- Summary: There are no response when select * from device by jdbc. Key: IOTDB-2252 URL: https://issues.apache.org/jira/browse/IOTDB-2252 Project: Apache IoTDB Issue Type: Bug Reporter: 张洪胤 Data config: There are 10 devices in 5 storage groups, each has 30 sensors. And there are 1,000,000 timeseries per device. When use jdbc connection to query(sql: select * from root.test.g_0.d_0), there will be no response after a short time. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (IOTDB-2259) [Aligned timeseries] insert into：Data type mismatch ，Error information is incorrect
刘珍 created IOTDB-2259: - Summary: [Aligned timeseries] insert into：Data type mismatch ，Error information is incorrect Key: IOTDB-2259 URL: https://issues.apache.org/jira/browse/IOTDB-2259 Project: Apache IoTDB Issue Type: Bug Components: Core/Server Affects Versions: 0.13.0 Reporter: 刘珍 insert into 对齐时间序列，数据类型不匹配，报错信息不正确 CREATE ALIGNED TIMESERIES root.lz.dev.GPS(latitude INT32 encoding=PLAIN compressor=SNAPPY, longitude INT32 encoding=PLAIN compress or=SNAPPY) ; insert into root.lz.dev.GPS(time,latitude,longitude ) aligned values(1,1.3,6.7); Msg: 500: [INTERNAL_SERVER_ERROR(500)] Exception occurred: executeNonQueryPlan failed. Null 错误日志： 2022-01-04 14:40:38,428 [pool-12-IoTDB-RPC-Client-8] ERROR o.a.i.d.u.ErrorHandlingUtils:57 - Status code: INTERNAL_SERVER_ERROR(500), operation: executeNonQueryPlan failed java.lang.NullPointerException: null at org.apache.iotdb.db.utils.datastructure.AlignedTVList.alignedTvListArrayMemCost(AlignedTVList.java:866) at org.apache.iotdb.db.engine.storagegroup.TsFileProcessor.checkAlignedMemCostAndAddToTspInfo(TsFileProcessor.java:406) at org.apache.iotdb.db.engine.storagegroup.TsFileProcessor.insert(TsFileProcessor.java:219) at org.apache.iotdb.db.engine.storagegroup.VirtualStorageGroupProcessor.insertToTsFileProcessor(VirtualStorageGroupProcessor.java:1149) at org.apache.iotdb.db.engine.storagegroup.VirtualStorageGroupProcessor.insert(VirtualStorageGroupProcessor.java:922) at org.apache.iotdb.db.engine.StorageEngine.insert(StorageEngine.java:600) at org.apache.iotdb.db.qp.executor.PlanExecutor.insert(PlanExecutor.java:1482) at org.apache.iotdb.db.qp.executor.PlanExecutor.processNonQuery(PlanExecutor.java:270) at org.apache.iotdb.db.service.basic.BasicServiceProvider.executeNonQuery(BasicServiceProvider.java:257) at org.apache.iotdb.db.service.thrift.impl.TSServiceImpl.executeNonQueryPlan(TSServiceImpl.java:1900) at org.apache.iotdb.db.service.thrift.impl.TSServiceImpl.executeNonQueryStatement(TSServiceImpl.java:1049) at org.apache.iotdb.db.service.thrift.impl.TSServiceImpl.executeUpdateStatement(TSServiceImpl.java:1042) at org.apache.iotdb.db.service.thrift.impl.TSServiceImpl.executeStatement(TSServiceImpl.java:552) at org.apache.iotdb.service.rpc.thrift.TSIService$Processor$executeStatement.getResult(TSIService.java:2733) at org.apache.iotdb.service.rpc.thrift.TSIService$Processor$executeStatement.getResult(TSIService.java:2713) at org.apache.thrift.ProcessFunction.process(ProcessFunction.java:38) at org.apache.thrift.TBaseProcessor.process(TBaseProcessor.java:38) at org.apache.thrift.server.TThreadPoolServer$WorkerProcess.run(TThreadPoolServer.java:248) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (IOTDB-2258) [Aligned timeseries] export-csv.sh & import-csv.sh need to support aligned timeseries
刘珍 created IOTDB-2258: - Summary: [Aligned timeseries] export-csv.sh & import-csv.sh need to support aligned timeseries Key: IOTDB-2258 URL: https://issues.apache.org/jira/browse/IOTDB-2258 Project: Apache IoTDB Issue Type: Bug Components: Tools/Others Reporter: 刘珍 如题。 1. 导出对齐时间序列的数据，再导入到干净的数据库，导入后的时间序列是非对齐的。 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (IOTDB-2183) [Cluster] Fix the config problems in cluster mode
张洪胤 created IOTDB-2183: -- Summary: [Cluster] Fix the config problems in cluster mode Key: IOTDB-2183 URL: https://issues.apache.org/jira/browse/IOTDB-2183 Project: Apache IoTDB Issue Type: Bug Reporter: 张洪胤 Because of the development of iotdb server, there are some problems in cluster/src/resources(for metric framework and influxdb rpc service), it will fail when you use these config to start iotdb cluster. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (IOTDB-2183) [Cluster] Fix the config problems in cluster mode
[ https://issues.apache.org/jira/browse/IOTDB-2183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] 张洪胤 reassigned IOTDB-2183: -- Assignee: 张洪胤 > [Cluster] Fix the config problems in cluster mode > - > > Key: IOTDB-2183 > URL: https://issues.apache.org/jira/browse/IOTDB-2183 > Project: Apache IoTDB > Issue Type: Bug >Reporter: 张洪胤 >Assignee: 张洪胤 >Priority: Major > Original Estimate: 1h > Remaining Estimate: 1h > > Because of the development of iotdb server, there are some problems in > cluster/src/resources(for metric framework and influxdb rpc service), it will > fail when you use these config to start iotdb cluster. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (IOTDB-2182) [Cluster] Fix the config problems in cluster mode
张洪胤 created IOTDB-2182: -- Summary: [Cluster] Fix the config problems in cluster mode Key: IOTDB-2182 URL: https://issues.apache.org/jira/browse/IOTDB-2182 Project: Apache IoTDB Issue Type: Bug Reporter: 张洪胤 Because of the development of iotdb server, there are some problems in cluster/src/resources(for metric framework and influxdb rpc service), it will fail when you use these config to start iotdb cluster. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (IOTDB-2039) Compaction returning more records than expeced after “Too many open files ”
刘珍 created IOTDB-2039:
-
Summary: Compaction returning more records than expeced after
“Too many open files ”
Key: IOTDB-2039
URL: https://issues.apache.org/jira/browse/IOTDB-2039
Project: Apache IoTDB
Issue Type: Bug
Components: Core/Compaction
Affects Versions: 0.12.3
Reporter: 刘珍
h1. rel/0.12 0.12.3 rc2
commit a8c5dc8a13a4b90303fec4b29e40a1b33e6b737d
Author: HTHou
Date: Sun Nov 14 12:46:16 2021 +0800
[maven-release-plugin] prepare release v0.12.3
h1. 1. test data
10 sg / 100dev /100 sensor （DOUBLE）
10 dev/sg
1 sensor/dev
2 points/sensor
h1. 2. execte 100 queries : Too many open files
log_error.log : Too many open files
++
|count(root.ip5.ip54.d_4.s_0)|
++
| {color:#DE350B}*200117000*{color}|
++
Total line number = 1
expected : 2
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (IOTDB-2034) The IOTDB process was killed by the operating system （Query）
刘珍 created IOTDB-2034:
-
Summary: The IOTDB process was killed by the operating system
（Query）
Key: IOTDB-2034
URL: https://issues.apache.org/jira/browse/IOTDB-2034
Project: Apache IoTDB
Issue Type: Bug
Components: Core/Query
Affects Versions: master branch
Reporter: 刘珍
Attachments: config.properties, q_limit.sh
h1. 1. master
commit d63539b7ec78576b12484a731ac3ff2894f922ed
Author: Jackie Tien
Date: Fri Nov 19 10:50:06 2021 +0800
Support RawQueryWithoutValueFilter in aligned timeseries (#4422)
h1. 2. 10sg/100dev/100sensor
10dev/sg
1 sensor/dev
2 points/sensor
h1. 3. Query
h2. cat run_limit.sh
#!/bin/bash
echo " PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+
COMMAND">./virt.txt
*pid_iotdb=29485*
./clear.sh
top -b -n 1 | grep ${pid_iotdb} >>./virt.txt
for i in {1..10}
do
./q_limit.sh
top -b -n 1 | grep ${pid_iotdb} >>./virt.txt
./clear.sh
done
-
cat clear.sh
#!/bin/bash
sudo su root </proc/sys/vm/drop_caches
EOF
-
cat q_limit.sh
./sbin/start-cli.sh -p 6667 -e "select s_0 from root.ip5.ip50.d_0 limit 1
offset 1" >> count_2.out
./sbin/start-cli.sh -p 6667 -e "select s_0 from root.ip5.ip50.d_10 limit 1
offset 1" >> count_2.out
./sbin/start-cli.sh -p 6667 -e "select s_0 from root.ip5.ip50.d_20 limit 1
offset 1" >> count_2.out
./sbin/start-cli.sh -p 6667 -e "select s_0 from root.ip5.ip50.d_30 limit 1
offset 1" >> count_2.out
./sbin/start-cli.sh -p 6667 -e "select s_0 from root.ip5.ip50.d_40 limit 1
offset 1" >> count_2.out
./sbin/start-cli.sh -p 6667 -e "select s_0 from root.ip5.ip50.d_50 limit 1
offset 1" >> count_2.out
./sbin/start-cli.sh -p 6667 -e "select s_0 from root.ip5.ip50.d_60 limit 1
offset 1" >> count_2.out
./sbin/start-cli.sh -p 6667 -e "select s_0 from root.ip5.ip50.d_70 limit 1
offset 1" >> count_2.out
./sbin/start-cli.sh -p 6667 -e "select s_0 from root.ip5.ip50.d_80 limit 1
offset 1" >> count_2.out
./sbin/start-cli.sh -p 6667 -e "select s_0 from root.ip5.ip50.d_90 limit 1
offset 1" >> count_2.out
./sbin/start-cli.sh -p 6667 -e "select s_0 from root.ip5.ip51.d_1 limit 1
offset 1" >> count_2.out
./sbin/start-cli.sh -p 6667 -e "select s_0 from root.ip5.ip51.d_11 limit 1
offset 1" >> count_2.out
.(See the attachment）
{color:#DE350B}*The iotdb pid's VIRT usage keeps increasing gradually until it
is killed by the operating system
*{color}
{color:#DE350B}*iotdb 的VIRT使用一直增加直到被操作系统杀死（iotdb 查询堆外内存没有控制）*{color}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (IOTDB-2035) The log level of config file error information should be "error" and the parameter name should be printed
刘珍 created IOTDB-2035:
-
Summary: The log level of config file error information should be
"error" and the parameter name should be printed
Key: IOTDB-2035
URL: https://issues.apache.org/jira/browse/IOTDB-2035
Project: Apache IoTDB
Issue Type: Bug
Components: Core/Server
Affects Versions: master branch, 0.12.3
Reporter: 刘珍
master & rel/0.12
1. WARN -> ERROR (WARN级别改为ERROR)
2. the parameter name should be printed (参数名称应该打印出来）
2021-11-19 17:17:08,924 [main] {color:#DE350B}*WARN
*{color}o.a.i.d.c.IoTDBDescriptor:781 - Incorrect format in config file, use
default configuration
{color:#DE350B}*java.lang.NumberFormatException: For input string: "a"*{color}
at
java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
at java.lang.Integer.parseInt(Integer.java:580)
at java.lang.Integer.parseInt(Integer.java:615)
at
org.apache.iotdb.db.conf.IoTDBDescriptor.initMemoryAllocate(IoTDBDescriptor.java:1213)
at
org.apache.iotdb.db.conf.IoTDBDescriptor.loadProps(IoTDBDescriptor.java:203)
at
org.apache.iotdb.db.conf.IoTDBDescriptor.(IoTDBDescriptor.java:52)
at
org.apache.iotdb.db.conf.IoTDBDescriptor$IoTDBDescriptorHolder.(IoTDBDescriptor.java:1300)
at
org.apache.iotdb.db.conf.IoTDBDescriptor.getInstance(IoTDBDescriptor.java:56)
at org.apache.iotdb.db.metadata.MManager.(MManager.java:151)
at org.apache.iotdb.db.service.IoTDB.(IoTDB.java:55)
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (IOTDB-1993) [Benchmark] Optimize TEST_DATA_PERSISTENCE
张洪胤 created IOTDB-1993: -- Summary: [Benchmark] Optimize TEST_DATA_PERSISTENCE Key: IOTDB-1993 URL: https://issues.apache.org/jira/browse/IOTDB-1993 Project: Apache IoTDB Issue Type: Improvement Components: Benchmark Reporter: 张洪胤 When test data is larger than 10,000,000, the cost of persistency of test data(such as latency) may influence the write of benchmark, so there is need to do some optimize, such as split into few tables or files. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (IOTDB-1987) [Benchmark] Add DOUBLE_LENGTH and other meta config for IoTDB in benchmark
张洪胤 created IOTDB-1987: -- Summary: [Benchmark] Add DOUBLE_LENGTH and other meta config for IoTDB in benchmark Key: IOTDB-1987 URL: https://issues.apache.org/jira/browse/IOTDB-1987 Project: Apache IoTDB Issue Type: Improvement Components: Benchmark Reporter: 张洪胤 Assignee: 张洪胤 I think we need to use benchmark to control the double point number decimal places. And when use to benchmark to register schema, I think there are needs to add some related config. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (IOTDB-1995) master ：" compaction_submission_interval " parameter is invalid
刘珍 created IOTDB-1995:
-
Summary: master ：" compaction_submission_interval " parameter is
invalid
Key: IOTDB-1995
URL: https://issues.apache.org/jira/browse/IOTDB-1995
Project: Apache IoTDB
Issue Type: Bug
Components: Core/Compaction
Reporter: 刘珍
Attachments: iotdb-engine.properties
master (1105) 0073a28384cdb84e9469dbf98705ab158dd43a31
1.
{color:#DE350B}*compaction_submission_interval=36000*{color}
2. Start iotdb
The compaction thread continues to execute .
启动数据库，合并线程一直在执行。
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (IOTDB-2012) [Benchmark] There are ClassCastExceptions when set IS_SENSOR_TS_ALIGNMENT and IS_CLIENT_BIND both false
张洪胤 created IOTDB-2012: -- Summary: [Benchmark] There are ClassCastExceptions when set IS_SENSOR_TS_ALIGNMENT and IS_CLIENT_BIND both false Key: IOTDB-2012 URL: https://issues.apache.org/jira/browse/IOTDB-2012 Project: Apache IoTDB Issue Type: Bug Components: Benchmark Reporter: 张洪胤 Assignee: 张洪胤 Attachments: image-2021-11-16-10-23-14-375.png When set IS_SENSOR_TS_ALIGNMENT and IS_CLIENT_BIND both false, there are ClassCastException. !image-2021-11-16-10-23-14-375.png! -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (IOTDB-2069) cluster : Internal error processing fetchMultSeries
刘珍 created IOTDB-2069: - Summary: cluster : Internal error processing fetchMultSeries Key: IOTDB-2069 URL: https://issues.apache.org/jira/browse/IOTDB-2069 Project: Apache IoTDB Issue Type: Bug Components: Core/Cluster Reporter: 刘珍 Attachments: config.properties, image-2021-11-27-09-41-21-879.png, image-2021-11-27-09-41-28-576.png, iotdb-engine.properties, iotdb-env.sh, q.sh, q_limit.sh, run_limit.sh, run_q.sh 0.12.3 rc2 a8c5dc8a13a4b90303fec4b29e40a1b33e6b737d 1. iotdb conf 3 node 1 rep See the attachment 2. run benchmark (see the attach : config.properties) 3. 192.168.130.13 nohup ./run_q.sh & nohup ./run_limit.sh & 4.192.168.130.10 nohup ./run_q.sh & 5. 192.168.130.4 nohup ./run_q.sh & 6. log error: !image-2021-11-27-09-41-21-879.png|thumbnail! !image-2021-11-27-09-41-28-576.png|thumbnail! -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (IOTDB-2046) [Benchmark] support to run on windows using bat.
[ https://issues.apache.org/jira/browse/IOTDB-2046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] 张洪胤 reassigned IOTDB-2046: -- Assignee: 张洪胤 > [Benchmark] support to run on windows using bat. > > > Key: IOTDB-2046 > URL: https://issues.apache.org/jira/browse/IOTDB-2046 > Project: Apache IoTDB > Issue Type: Improvement > Components: Benchmark >Reporter: 张洪胤 >Assignee: 张洪胤 >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (IOTDB-2046) [Benchmark] support to run on windows using bat.
张洪胤 created IOTDB-2046: -- Summary: [Benchmark] support to run on windows using bat. Key: IOTDB-2046 URL: https://issues.apache.org/jira/browse/IOTDB-2046 Project: Apache IoTDB Issue Type: Improvement Components: Benchmark Reporter: 张洪胤 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (IOTDB-2037) [Benchmark] NPE when set IS_SENSOR_TS_ALIGNMENT = false and IS_CLIENT_BIND = false
张洪胤 created IOTDB-2037: -- Summary: [Benchmark] NPE when set IS_SENSOR_TS_ALIGNMENT = false and IS_CLIENT_BIND = false Key: IOTDB-2037 URL: https://issues.apache.org/jira/browse/IOTDB-2037 Project: Apache IoTDB Issue Type: Bug Components: Benchmark Reporter: 张洪胤 Attachments: image-2021-11-20-10-56-37-680.png !image-2021-11-20-10-56-37-680.png! -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (IOTDB-2037) [Benchmark] NPE when set IS_SENSOR_TS_ALIGNMENT = false and IS_CLIENT_BIND = false
[ https://issues.apache.org/jira/browse/IOTDB-2037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] 张洪胤 reassigned IOTDB-2037: -- Assignee: 张洪胤 > [Benchmark] NPE when set IS_SENSOR_TS_ALIGNMENT = false and IS_CLIENT_BIND = > false > -- > > Key: IOTDB-2037 > URL: https://issues.apache.org/jira/browse/IOTDB-2037 > Project: Apache IoTDB > Issue Type: Bug > Components: Benchmark >Reporter: 张洪胤 >Assignee: 张洪胤 >Priority: Major > Attachments: image-2021-11-20-10-56-37-680.png > > Original Estimate: 12h > Remaining Estimate: 12h > > !image-2021-11-20-10-56-37-680.png! -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (IOTDB-2028) The file handle is not released immediately after query
刘珍 created IOTDB-2028: - Summary: The file handle is not released immediately after query Key: IOTDB-2028 URL: https://issues.apache.org/jira/browse/IOTDB-2028 Project: Apache IoTDB Issue Type: Bug Components: Core/Query Affects Versions: 0.12.3 Reporter: 刘珍 Attachments: image-2021-11-18-10-27-28-502.png rel/0.12 0.12.3 rc2 commit 0ee47a59d898cca7deb32fee35505b98022ab53b Author: HTHou Date: Sun Nov 14 12:46:27 2021 +0800 [maven-release-plugin] prepare for next development iteration 1. 10 sg / 100dev /100 sensor 10 dev/sg 1 sensor/dev 2 points/sensor 2. The test results !image-2021-11-18-10-27-28-502.png! 3. Test steps 3.1 echo 3 >/proc/sys/vm/drop_caches 3.2 start iotdb. Get the pid of iotdb. 3.3 Run the test script with sleep : lsof -p 10604|wc -l >> a.out ./sbin/start-cli.sh -p 6667 -e "select count(*) from root.ip5.ip50.d_0 " >> count_1.out sleep 120 lsof -p 10604|wc -l >> a.out ./sbin/start-cli.sh -p 6667 -e "select count(*) from root.ip5.ip51.d_1 " >> count_1.out sleep 120 lsof -p 10604|wc -l >> a.out ./sbin/start-cli.sh -p 6667 -e "select count(*) from root.ip5.ip52.d_2 " >> count_1.out sleep 120 lsof -p 10604|wc -l >> a.out ./sbin/start-cli.sh -p 6667 -e "select count(*) from root.ip5.ip53.d_3 " >> count_1.out sleep 120 lsof -p 10604|wc -l >> a.out ./sbin/start-cli.sh -p 6667 -e "select count(*) from root.ip5.ip54.d_4 " >> count_1.out sleep 120 lsof -p 10604|wc -l >> a.out ./sbin/start-cli.sh -p 6667 -e "select count(*) from root.ip5.ip55.d_5 " >> count_1.out sleep 120 lsof -p 10604|wc -l >> a.out ./sbin/start-cli.sh -p 6667 -e "select count(*) from root.ip5.ip56.d_6 " >> count_1.out sleep 120 lsof -p 10604|wc -l >> a.out ./sbin/start-cli.sh -p 6667 -e "select count(*) from root.ip5.ip57.d_7 " >> count_1.out sleep 120 lsof -p 10604|wc -l >> a.out ./sbin/start-cli.sh -p 6667 -e "select count(*) from root.ip5.ip58.d_8 " >> count_1.out sleep 120 lsof -p 10604|wc -l >> a.out ./sbin/start-cli.sh -p 6667 -e "select count(*) from root.ip5.ip59.d_9 " >> count_1.out sleep 120 lsof -p 10604|wc -l >> a.out without sleep The script above , deletes “sleep 120” -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (IOTDB-2021) BloomFilterCache does not take effect
[
https://issues.apache.org/jira/browse/IOTDB-2021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17444984#comment-17444984
]
刘珍 commented on IOTDB-2021:
---
PR#4410 test results :
!screenshot-1.png!
!screenshot-2.png!
> BloomFilterCache does not take effect
> -
>
> Key: IOTDB-2021
> URL: https://issues.apache.org/jira/browse/IOTDB-2021
> Project: Apache IoTDB
> Issue Type: Bug
> Components: Core/Query
>Affects Versions: master branch
>Reporter: 刘珍
>Assignee: Yuan Tian
>Priority: Major
> Labels: pull-request-available
> Attachments: config.properties, image-2021-11-17-09-21-37-898.png,
> image-2021-11-17-09-21-49-232.png, screenshot-1.png, screenshot-2.png
>
>
> Comparatives ： PR#4350 & master
>PR#4350 ( has been merged into the master branch）
>master (1105) : 0073a28384cdb84e9469dbf98705ab158dd43a31
> PR#4350 & master （*close compaction*）：
>enable_seq_space_compaction=false
>enable_unseq_space_compaction=false
>enable_cross_space_compaction=false
> PR#4350：
>chunk_timeseriesmeta_free_memory_proportion=*300*:100:200:300:400
> 1.Generate test data
> benchmark ： config.properties （See the attachment）
> 2.Create 1 sensor without writing data
> create timeseries root.ip5.ip59.d_29.s_1 WITH DATATYPE=DOUBLE, ENCODING=PLAIN
> ,compression=UNCOMPRESSED
> 3. The test script
> for i in {1..10}
> do
>./clear.sh
>./clear.sh
>./clear.sh
>sleep 7
>./sbin/start-cli.sh -p 6667 -e "select s_1 from root.ip5.ip59.d_29" >>
> bloom_cache.out
> done
>
> cat clear.sh
> #!/bin/bash
> sudo su root < echo 3 >/proc/sys/vm/drop_caches
> EOF
> 4.The test results
> !image-2021-11-17-09-21-37-898.png!
> !image-2021-11-17-09-21-49-232.png!
> {color:#DE350B}*PR#4350 : BloomFilter cache does not take effect*{color}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (IOTDB-2021) BloomFilterCache does not take effect
刘珍 created IOTDB-2021:
-
Summary: BloomFilterCache does not take effect
Key: IOTDB-2021
URL: https://issues.apache.org/jira/browse/IOTDB-2021
Project: Apache IoTDB
Issue Type: Bug
Components: Core/Query
Reporter: 刘珍
Fix For: master branch
Attachments: image-2021-11-17-09-21-37-898.png,
image-2021-11-17-09-21-49-232.png
PR#4350 ( has been merged into the master branch）
master (1105) : 0073a28384cdb84e9469dbf98705ab158dd43a31
PR#4350 & master （*close compaction*）：
enable_seq_space_compaction=false
enable_unseq_space_compaction=false
enable_cross_space_compaction=false
PR#4350：
chunk_timeseriesmeta_free_memory_proportion=300:100:200:300:400
1.Generate test data
benchmark ： config.properties （See the attachment）
2.Create 1 sensor without writing data
create timeseries root.ip5.ip59.d_29.s_1 WITH DATATYPE=DOUBLE, ENCODING=PLAIN
,compression=UNCOMPRESSED
3. The test script
for i in {1..10}
do
./clear.sh
./clear.sh
./clear.sh
sleep 7
./sbin/start-cli.sh -p 6667 -e "select s_1 from root.ip5.ip59.d_29" >>
bloom_cache.out
done
cat clear.sh
#!/bin/bash
sudo su root </proc/sys/vm/drop_caches
EOF
4.The test results
!image-2021-11-17-09-21-37-898.png!
!image-2021-11-17-09-21-49-232.png!
{color:#DE350B}*PR#4350 : BloomFilter cache does not take effect*{color}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (IOTDB-1895) Cache leader optimization for batch write interfaces on multiple devices
[ https://issues.apache.org/jira/browse/IOTDB-1895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17448443#comment-17448443 ] 刘珍 commented on IOTDB-1895: --- PASS. [^SessionExample.java] rc2 session： real0m20.598s rc1 session： real0m37.477s > Cache leader optimization for batch write interfaces on multiple devices > > > Key: IOTDB-1895 > URL: https://issues.apache.org/jira/browse/IOTDB-1895 > Project: Apache IoTDB > Issue Type: Improvement >Reporter: Xinyu Tan >Assignee: Quan Siyi >Priority: Major > Labels: pull-request-available > Attachments: SessionExample.java > > Original Estimate: 24h > Remaining Estimate: 24h > > At present, the cache leader performance optimization for distributed write > performance is critical ([the design > document|https://shimo.im/docs/dYwjwtrTPXPWcqxj]) . Although the current > implementation in the session module for all equipment cache handling, On the > server side, however, only writes to a single device are passed clues, > causing the partition cache of the batch interface to be effectively > invalidated. As the number of users of multi-device interfaces increases, we > need to do this optimization. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (IOTDB-1897) cluster : The result of "select count(sensor) .. " is inconsistent with that of "select sensor .."
刘珍 created IOTDB-1897:
-
Summary: cluster : The result of "select count(sensor) .. " is
inconsistent with that of "select sensor .."
Key: IOTDB-1897
URL: https://issues.apache.org/jira/browse/IOTDB-1897
Project: Apache IoTDB
Issue Type: Improvement
Components: Core/Cluster
Reporter: 刘珍
Attachments: SessionExample.java, image-2021-10-26-17-38-05-803.png
测试版本：
rel/0.12 958628804c14e58e5083233a6ca6aa370521b504
问题描述：
1. 集群信息
cluster ： 5 nodes 1 replication
seed_nodes=192.168.130.4:9003,192.168.130.10:9003,192.168.130.13:9003,192.168.130.17:9003,192.168.130.20:9003
default_replica_num=1
2. 启动4/10/13/17/20
3.在17节点运行SessionExample.java (见附件)
编译与运行（运行时间约1.5分钟）：
javac -cp ./lib/*:. SessionExample.java
java -cp ./lib/*:. SessionExample
4. cli查询
select count(s1) from root.sg5.d1
select s1 from root.sg5.d1
{color:#DE350B}*执行结果记录数不一致。*{color}
!image-2021-10-26-17-38-05-803.png|thumbnail!
select s1 from root.sg5.d1的结果为：
Total line number = 1
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IOTDB-1899) ERROR o.a.i.d.e.c.t.AbstractCompactionTask:57 - Stream Closed
刘珍 created IOTDB-1899:
-
Summary: ERROR o.a.i.d.e.c.t.AbstractCompactionTask:57 - Stream
Closed
Key: IOTDB-1899
URL: https://issues.apache.org/jira/browse/IOTDB-1899
Project: Apache IoTDB
Issue Type: Bug
Components: Core/Server
Affects Versions: master branch
Reporter: 刘珍
master （new_compaction） ：
{color:#DE350B}*IOException during compaction :*{color}
(合并时，文件流异常）
{color:#DE350B}*2021-10-20 20:58:48,333 [pool-4-IoTDB-Compaction-6] ERROR
o.a.i.d.e.c.t.AbstractCompactionTask:57 - Stream Closed
java.io.IOException: Stream Closed*{color}
at java.io.FileOutputStream.writeBytes(Native Method)
at java.io.FileOutputStream.write(FileOutputStream.java:326)
at
java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82)
at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:140)
at
org.apache.iotdb.tsfile.write.writer.LocalTsFileOutput.getPosition(LocalTsFileOutput.java:65)
at
org.apache.iotdb.tsfile.write.writer.TsFileIOWriter.writeChunk(TsFileIOWriter.java:224)
at
org.apache.iotdb.db.engine.compaction.inner.utils.InnerSpaceCompactionUtils.writeByAppendPageMerge(InnerSpaceCompactionUtils.java:174)
at
org.apache.iotdb.db.engine.compaction.inner.utils.InnerSpaceCompactionUtils.compact(InnerSpaceCompactionUtils.java:435)
at
org.apache.iotdb.db.engine.compaction.inner.sizetiered.SizeTieredCompactionTask.doCompaction(SizeTieredCompactionTask.java:136)
at
org.apache.iotdb.db.engine.compaction.task.AbstractCompactionTask.call(AbstractCompactionTask.java:55)
at
org.apache.iotdb.db.engine.compaction.task.AbstractCompactionTask.call(AbstractCompactionTask.java:36)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
{color:#DE350B}*2021-10-20 23:08:36,137 [pool-4-IoTDB-Compaction-7] ERROR
o.a.i.d.e.c.t.AbstractCompactionTask:57 - null
java.io.IOException: null*{color}
at
org.apache.iotdb.db.engine.compaction.inner.utils.InnerSpaceCompactionUtils.compact(InnerSpaceCompactionUtils.java:298)
at
org.apache.iotdb.db.engine.compaction.inner.sizetiered.SizeTieredCompactionTask.doCompaction(SizeTieredCompactionTask.java:136)
at
org.apache.iotdb.db.engine.compaction.task.AbstractCompactionTask.call(AbstractCompactionTask.java:55)
at
org.apache.iotdb.db.engine.compaction.task.AbstractCompactionTask.call(AbstractCompactionTask.java:36)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IOTDB-1888) [iotdb-benchmark] can't set point_step as 1us
[ https://issues.apache.org/jira/browse/IOTDB-1888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17434818#comment-17434818 ] 张洪胤 commented on IOTDB-1888: https://github.com/thulab/iotdb-benchmark/pull/215 > [iotdb-benchmark] can't set point_step as 1us > - > > Key: IOTDB-1888 > URL: https://issues.apache.org/jira/browse/IOTDB-1888 > Project: Apache IoTDB > Issue Type: Bug > Components: Benchmark >Reporter: FengQingxin >Assignee: 张洪胤 >Priority: Major > Attachments: image-2021-10-25-16-12-40-132.png > > Original Estimate: 1h > Remaining Estimate: 1h > > Hi > There is bug in iotdb-benchmark,I can't use it to set point_step as 1us. > # set iotdb conf as 'timestamp_precision=us' > # set iotdb-benchmark conf as 'TIMESTAMP_PRECISION=us' and 'POINT_STEP=200' > # start iotdb the start iotdb-benchmark > # using iotdb-cli to query the data: > The point_step is 200ms. > !image-2021-10-25-16-12-40-132.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IOTDB-1888) [iotdb-benchmark] can't set point_step as 1us
[ https://issues.apache.org/jira/browse/IOTDB-1888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] 张洪胤 reassigned IOTDB-1888: -- Assignee: 张洪胤 > [iotdb-benchmark] can't set point_step as 1us > - > > Key: IOTDB-1888 > URL: https://issues.apache.org/jira/browse/IOTDB-1888 > Project: Apache IoTDB > Issue Type: Bug > Components: Benchmark >Reporter: FengQingxin >Assignee: 张洪胤 >Priority: Major > Attachments: image-2021-10-25-16-12-40-132.png > > > Hi > There is bug in iotdb-benchmark,I can't use it to set point_step as 1us. > # set iotdb conf as 'timestamp_precision=us' > # set iotdb-benchmark conf as 'TIMESTAMP_PRECISION=us' and 'POINT_STEP=200' > # start iotdb the start iotdb-benchmark > # using iotdb-cli to query the data: > The point_step is 200ms. > !image-2021-10-25-16-12-40-132.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-1976) [Benchmark]Add log when register schema.
张洪胤 created IOTDB-1976: -- Summary: [Benchmark]Add log when register schema. Key: IOTDB-1976 URL: https://issues.apache.org/jira/browse/IOTDB-1976 Project: Apache IoTDB Issue Type: Improvement Components: Benchmark Reporter: 张洪胤 Assignee: 张洪胤 When you set CREATE_SCHEMA = true, benchmark will register schema in your target database. I think add some log in this procedure and stop when register is failed can be a good idea. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (IOTDB-1367) [Distributed] Runtime exception is not properly handled during forwarding
[
https://issues.apache.org/jira/browse/IOTDB-1367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17440863#comment-17440863
]
刘珍 commented on IOTDB-1367:
---
rel/0.12 f295447aafc1687e8b3f55b360601fe1cffa53f1
5节点1副本
seed_nodes=192.168.130.4:9003,192.168.130.10:9003,192.168.130.11:9003,192.168.130.13:9003,192.168.130.19:9003
default_replica_num=1
不通过，表现同上（master）
IoTDB> select avg(s_1) from root.ip4.sg5.dev1
{color:#DE350B}*Msg: 313: Request "Query aggregate: root.ip4.sg5.dev1.s_1 in
[Node(internalIp:192.168.130.13, metaPort:9003, nodeIdentifier:-100054350,
dataPort:40010, clientPort:6667, clientIp:192.168.130.13)]" timeout*{color}
日志：
2021-11-09 10:45:27,895 [ClusterClient-1] ERROR
o.a.i.c.q.a.ClusterAggregator:251 - Meta: {color:#DE350B}Cannot query
aggregation root.ip4.sg5.dev1.s_1 from Node(internalIp:192.168.130.13,
metaPort:9003, nodeIdentifier:-100054350, dataPort:40010, clientPort:6667,
clientIp:192.168.130.13)
org.apache.thrift.TApplicationException: Internal error processing
getAggrResult{color}
at org.apache.thrift.TServiceClient.receiveBase(TServiceClient.java:79)
at
org.apache.iotdb.cluster.rpc.thrift.TSDataService$Client.recv_getAggrResult(TSDataService.java:641)
at
org.apache.iotdb.cluster.rpc.thrift.TSDataService$Client.getAggrResult(TSDataService.java:628)
at
org.apache.iotdb.cluster.query.aggregate.ClusterAggregator.getRemoteAggregateResult(ClusterAggregator.java:278)
at
org.apache.iotdb.cluster.query.aggregate.ClusterAggregator.getRemoteAggregateResult(ClusterAggregator.java:231)
at
org.apache.iotdb.cluster.query.aggregate.ClusterAggregator.getAggregateResult(ClusterAggregator.java:146)
at
org.apache.iotdb.cluster.query.aggregate.ClusterAggregator.getAggregateResult(ClusterAggregator.java:108)
at
org.apache.iotdb.cluster.query.aggregate.ClusterAggregateExecutor.aggregateOneSeries(ClusterAggregateExecutor.java:77)
at
org.apache.iotdb.db.query.executor.AggregationExecutor.executeWithoutValueFilter(AggregationExecutor.java:111)
at
org.apache.iotdb.db.query.executor.QueryRouter.aggregate(QueryRouter.java:136)
at
org.apache.iotdb.db.qp.executor.PlanExecutor.processDataQuery(PlanExecutor.java:539)
at
org.apache.iotdb.cluster.query.ClusterPlanExecutor.processQuery(ClusterPlanExecutor.java:101)
at
org.apache.iotdb.db.service.TSServiceImpl.createQueryDataSet(TSServiceImpl.java:1100)
at
org.apache.iotdb.db.service.TSServiceImpl.internalExecuteQueryStatement(TSServiceImpl.java:731)
at
org.apache.iotdb.db.service.TSServiceImpl.executeStatement(TSServiceImpl.java:596)
at
org.apache.iotdb.service.rpc.thrift.TSIService$Processor$executeStatement.getResult(TSIService.java:2373)
at
org.apache.iotdb.service.rpc.thrift.TSIService$Processor$executeStatement.getResult(TSIService.java:2353)
at org.apache.thrift.ProcessFunction.process(ProcessFunction.java:38)
at org.apache.thrift.TBaseProcessor.process(TBaseProcessor.java:38)
at
org.apache.thrift.server.TThreadPoolServer$WorkerProcess.run(TThreadPoolServer.java:248)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
> [Distributed] Runtime exception is not properly handled during forwarding
> -
>
> Key: IOTDB-1367
> URL: https://issues.apache.org/jira/browse/IOTDB-1367
> Project: Apache IoTDB
> Issue Type: Bug
> Components: Core/Cluster
>Reporter: Tian Jiang
>Priority: Major
> Labels: client-me, distributed, query
> Attachments: image-2021-05-07-20-14-47-670.png, screenshot-1.png
>
>
> When I executed `select avg(s_0) from root.group_0.d_20` (notice that s_0 is
> boolean and does not support avg), I got `Msg: 313: Request "Query aggregate:
> root.group_0.d_20.s_0 in [Node(internalIp:192.168.130.4, metaPort:9003,
> nodeIdentifier:1436654207, dataPort:40003, clientPort:6667,
> clientIp:0.0.0.0)]" timeout`. While the log on node 192.168.130.4 says:
> !image-2021-05-07-20-14-47-670.png|thumbnail!
> The cause is that RunTimeExceptions are not caught explicitly in
> DataClusterServer and MetaClusterServer, so they are converted to TExceptions
> by Thrift and are recognized as network problems by the coordinator.
> The solution is either to catch runtime exceptions explicitly and create
> status codes for them or make the coordinator capable of resolving more
> TExceptions. Both ways have their difficulties, for the first one, it is
> nearly impossi
[jira] [Commented] (IOTDB-1402) Support the auto-create-schema mechanism for insertRecords in cluster module
[
https://issues.apache.org/jira/browse/IOTDB-1402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17440921#comment-17440921
]
刘珍 commented on IOTDB-1402:
---
rel/0.12 f295447aafc1687e8b3f55b360601fe1cffa53f1
{color:#00875A}*测试结果：通过*{color}
iotdb :
seed_nodes=192.168.130.4:9003,192.168.130.10:9003,192.168.130.11:9003,192.168.130.13:9003,192.168.130.19:9003
default_replica_num=1
default_storage_group_level=2
benchmark:
DB_SWITCH=IoTDB-012-JDBC或IoTDB-012-SESSION_BY_RECORDS
CREATE_SCHEMA=false
benchmark先启动写入测试，再启动查询。测试过程中，频繁执行
delete storage group root.*
count timeseries
结果正确：
IoTDB> count timeseries
+-+
|count|
+-+
| {color:#00875A}*100*{color}|
+-+
Total line number = 1
> Support the auto-create-schema mechanism for insertRecords in cluster module
>
>
> Key: IOTDB-1402
> URL: https://issues.apache.org/jira/browse/IOTDB-1402
> Project: Apache IoTDB
> Issue Type: Bug
> Components: Core/Cluster
>Reporter: Xinyu Tan
>Priority: Major
> Attachments: image-2021-08-31-15-46-20-284.png,
> insert_config.properties, query_config.properties, screenshot-1.png,
> screenshot-2.png
>
>
> On 28 May's commit 363bda92dbdb0f2f4739138ec858c91bb7c81efb, after starting
> three node single replica cluster, sessionExample insertrecords interface
> will be written in the failure. This is mainly due to problems with the
> automatic schema creation logic of InsertRowsPlan in the cluster, which does
> not handle BatchProcessException well
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (IOTDB-1628) error message=mid consistency,localAppliedId is smaller than the leaderCommitId
[
https://issues.apache.org/jira/browse/IOTDB-1628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17440932#comment-17440932
]
刘珍 commented on IOTDB-1628:
---
rel/0.12 f295447aafc1687e8b3f55b360601fe1cffa53f1
iotdb:
seed_nodes=192.168.130.4:9003,192.168.130.10:9003,192.168.130.11:9003,192.168.130.13:9003,192.168.130.19:9003
default_replica_num=1
default_storage_group_level=2
benchmark :
先运行insert_config.properties配置
过1分钟，再运行query_config.properties
cli连接节点，执行多次（单用户）：
delete storage group root.*
count timeseries
可复现。：
IoTDB> count timeseries
{color:#00875A}{color:#DE350B}*Msg: 411: Error occurred in query process: check
consistency failed, error message=mid consistency, localAppliedId is smaller
than the leaderCommitId*{color}{color}
> error message=mid consistency,localAppliedId is smaller than the
> leaderCommitId
> ---
>
> Key: IOTDB-1628
> URL: https://issues.apache.org/jira/browse/IOTDB-1628
> Project: Apache IoTDB
> Issue Type: Bug
> Components: Core/Cluster
>Reporter: FengQingxin
>Assignee: 张洪胤
>Priority: Major
> Attachments: image-2021-09-06-11-30-41-100.png,
> image-2021-09-06-11-31-47-086.png
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> _强调文本_Dear Developers:
> I met an error when I using iotdb-cluster,"error message=mid
> consistency,localAppliedId is smaller than the leaderCommitId".
> # start iotdb-cluster [3 nodes，default_replica_num=3]
> # insert data with iotdb-benchmark[read and write]
> !image-2021-09-06-11-30-41-100.png!
> !image-2021-09-06-11-31-47-086.png!
> Please check this.
> Thanks.
> B.R.
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (IOTDB-1977) cluster（master） : delete storage group root.* Msg: 304: Path [root.*] does not exist
刘珍 created IOTDB-1977:
-
Summary: cluster（master） : delete storage group root.* Msg: 304:
Path [root.*] does not exist
Key: IOTDB-1977
URL: https://issues.apache.org/jira/browse/IOTDB-1977
Project: Apache IoTDB
Issue Type: Bug
Components: Core/Cluster
Reporter: 刘珍
Attachments: config.properties, image-2021-11-09-15-55-50-438.png
master 0073a28384cdb84e9469dbf98705ab158dd43a31
iotdb：
seed_nodes=192.168.130.4:9003,192.168.130.10:9003,192.168.130.11:9003,192.168.130.13:9003,192.168.130.19:9003
default_replica_num=1
default_storage_group_level=2
benchmark： config.properties
Once Benchmark gets up and running，cli ：
IoTDB> show storage group
+-+
|storage group|
+-+
|root.test.g_9|
|root.test.g_8|
|root.test.g_1|
|root.test.g_0|
|root.test.g_3|
|root.test.g_2|
|root.test.g_5|
|root.test.g_4|
|root.test.g_7|
|root.test.g_6|
+-+
Total line number = 10
It costs 0.002s
IoTDB> delete storage group root.*
{color:#DE350B}*Msg: 304: Path [root.*] does not exist*{color}
!image-2021-11-09-15-55-50-438.png!
rel /0.12 can be executed successfully
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (IOTDB-1393) Request timed out when create time series
[
https://issues.apache.org/jira/browse/IOTDB-1393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17440860#comment-17440860
]
刘珍 commented on IOTDB-1393:
---
rel/0.12 f295447aafc1687e8b3f55b360601fe1cffa53f1
5节点1副本
seed_nodes=192.168.130.4:9003,192.168.130.10:9003,192.168.130.11:9003,192.168.130.13:9003,192.168.130.19:9003
default_replica_num=1
{color:#00875A}*通过。*{color}
IoTDB> CREATE TIMESERIES root.devices.wf03.wt01.ts0 WITH DATATYPE=BOOLEAN,
ENCODING=PLAIN, compression=UNCOMPRESSED
{color:#00875A}*Msg: The statement is executed successfully.*{color}
IoTDB> create timeseries root.devices.wf03.wt01.ts1(elec_meter) with
datatype=INT32, encoding=RLE, compression=SNAPPY,MAX_POINT_NUMBER=
3 tags(tag1=t1, tag2=t2) attributes(attr1=a1, attr2=a2)
{color:#00875A}*Msg: The statement is executed successfully.*{color}
IoTDB> create timeseries root.devices.wf03.wt01.ts2 with datatype=INT64,
encoding=RLE, compression=LZ4 tags(tag1=t1, tag2=t2) attribute
s(attr1=a1, attr2=a2)
{color:#00875A}*Msg: The statement is executed successfully.*{color}
IoTDB> insert into root.devices.wf03.wt01(time,ts0,ts1,ts2)
values(1,true,23,31);
Msg: The statement is executed successfully.
IoTDB> select * from root.devices.wf03.wt01
+-+--+--+--+
|
Time|root.devices.wf03.wt01.ts0|root.devices.wf03.wt01.ts2|root.devices.wf03.wt01.ts1|
+-+--+--+--+
|1970-01-01T08:00:00.001+08:00| true|
31|23|
+-+--+--+--+
Total line number = 1
It costs 0.107s
> Request timed out when create time series
> -
>
> Key: IOTDB-1393
> URL: https://issues.apache.org/jira/browse/IOTDB-1393
> Project: Apache IoTDB
> Issue Type: Bug
> Components: Core/Cluster
>Affects Versions: 0.12.0
>Reporter: LuMing
>Priority: Major
> Attachments: screenshot-1.png
>
>
> 1.client connected
> 2.execute statement
> CREATE TIMESERIES root.devices.wf03.wt01.ts0 WITH DATATYPE=BOOLEAN,
> ENCODING=PLAIN, compression=UNCOMPRESSED
> create timeseries root.devices.wf03.wt01.ts1(elec_meter) with
> datatype=INT32, encoding=RLE, compression=SNAPPY,MAX_POINT_NUMBER=3
> tags(tag1=t1, tag2=t2) attributes(attr1=a1, attr2=a2)
> create timeseries root.devices.wf03.wt01.ts2 with datatype=INT64,
> encoding=RLE, compression=LZ4 tags(tag1=t1, tag2=t2) attributes(attr1=a1,
> attr2=a2)3.result
> 3. result
> !https://clouddevops.huawei.com/vision-file-storage/api/file/download/upload-v2/2021/4/18/z00293891/8ccad779814e46faaadc92ad27397141/image.png!
> 4. log segments
> 2021-05-18 19:39:07,430 | DEBUG | [DataClientThread-5] | Meta: synchronizing
> commitIndex -1/0 | org.apache.iotdb.cluster.server.member.RaftMember
> (RaftMember.java:906)
> 2021-05-18 19:39:07,473 | DEBUG |
> [Data(node1:22250)-HeartbeatThread@1621328224936] | Data(node1:22250):
> Heartbeat from leader Node(internalIp:node1, metaPort:22250,
> nodeIdentifier:-1394469830, dataPort:22252, clientPort:22260, clientIp:node1)
> is still valid | org.apache.iotdb.cluster.server.heartbeat.HeartbeatThread
> (HeartbeatThread.java:100)
> 2021-05-18 19:39:07,473 | DEBUG |
> [Data(node2:22250)-HeartbeatThread@1621328224966] | Data(node2:22250):
> Heartbeat from leader Node(internalIp:node2, metaPort:22250,
> nodeIdentifier:-1395157557, dataPort:22252, clientPort:22260, clientIp:node2)
> is still valid | org.apache.iotdb.cluster.server.heartbeat.HeartbeatThread
> (HeartbeatThread.java:100)
> 2021-05-18 19:39:07,486 | DEBUG |
> [Data(node3:22250)-HeartbeatThread@1621328224906] | Data(node3:22250): Send
> heartbeat to 2 followers |
> org.apache.iotdb.cluster.server.heartbeat.HeartbeatThread
> (HeartbeatThread.java:150)
> 2021-05-18 19:39:08,005 | DEBUG | [MetaHeartbeatClientThread-1] | Meta:
> Inconsistent log found, leaderCommit: 0-6, localCommit: -1--1, localLast: 0-6
> | org.apache.iotdb.cluster.server.member.RaftMember (RaftMember.java:423)
> *2021-05-18 19:39:08,431 | WARN | [DataClientThread-5] | Meta: Failed to
> synchronize with the leader after 20018ms |
> *org.apache.iotdb.cluster.server.member.RaftMember (RaftMember.java:927)
> 2021-05-18 19:39:08,432 | DEBUG | [DataClientThread-5] | Exception occurred
> when applying seriesPath: root.devices.wf03.wt01.ts2, re
[jira] [Created] (IOTDB-1979) cluster：Insert into the nonexistent sequence succeeded, but show timeseries got "Empty set."
刘珍 created IOTDB-1979:
-
Summary: cluster：Insert into the nonexistent sequence succeeded,
but show timeseries got "Empty set."
Key: IOTDB-1979
URL: https://issues.apache.org/jira/browse/IOTDB-1979
Project: Apache IoTDB
Issue Type: Bug
Components: Core/Cluster
Reporter: 刘珍
Attachments: config.properties.records.insert,
config.properties.records.query, image-2021-11-09-18-04-58-188.png
master 0073a28384cdb84e9469dbf98705ab158dd43a31
rel/0.12 f295447aafc1687e8b3f55b360601fe1cffa53f1
1. cluster
seed_nodes=192.168.130.4:9003,192.168.130.10:9003,192.168.130.11:9003,192.168.130.13:9003,192.168.130.19:9003
default_replica_num=1
* default_storage_group_level=1(default）*
*
2. 192.168.130.10 benchmark
/home/iotdb/liuzhen_test/bm_1103
DB_SWITCH=IoTDB-012-SESSION_BY_RECORDS
HOST=192.168.130.10
DB_NAME=test
BATCH_SIZE_PER_WRITE=10
LOOP=100
GROUP_NUMBER=10
DEVICE_NUMBER=100
SENSOR_NUMBER=1
CLIENT_NUMBER=100
cd /home/iotdb/liuzhen_test/bm_1103
cp conf/config.properties.records.insert conf/config.properties
nohup ./benchmark.sh > records_insert.out &
sleep 120
cp conf/config.properties.records.query conf/config.properties
nohup ./benchmark.sh > records_query.out &
3. 192.168.130.4 cli
delete storage group root.*
count timeseries
If the result of count timeseries is 100，Continue to perform
delete storage group root.*
count timeseries
...
When the result of ”count timeseries “ is less than 100，Run “show timeseries ”
to find the device that failed to create:
count(root.test.g_0~root.test.g_9) <10 .(当count timeseries 的值小于100，运行
show
timeseries,在结果中找出是哪个设备创建失败，root.test.g_0到root.test.g_9的个数应该等于10，如果小于10，看看是哪个设备没创建成功，比如，我的环境是root.test.g_1.d_21没创建成功）
IoTDB> insert into root.test.g_1.d_21(time,s_0) values(1,3.45);
{color:#00875A}*Msg: The statement is executed successfully.*{color}
IoTDB>
IoTDB>
IoTDB> show timeseries root.test.g_1.d_21
+--+-+-+++---++--+
|timeseries|alias|storage group|dataType|encoding|compression|tags|attributes|
+--+-+-+++---++--+
+--+-+-+++---++--+
{color:#DE350B}*Empty set.*{color}
!image-2021-11-09-18-04-58-188.png!
-
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (IOTDB-1937) cluster：The cluster could support sync
刘珍 created IOTDB-1937: - Summary: cluster：The cluster could support sync Key: IOTDB-1937 URL: https://issues.apache.org/jira/browse/IOTDB-1937 Project: Apache IoTDB Issue Type: New Feature Components: Core/Cluster Reporter: 刘珍 集群应该支持sync。 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-1939) sync : The receiver receives more data than the sender sends
刘珍 created IOTDB-1939:
-
Summary: sync : The receiver receives more data than the sender
sends
Key: IOTDB-1939
URL: https://issues.apache.org/jira/browse/IOTDB-1939
Project: Apache IoTDB
Issue Type: New Feature
Components: Tools/Sync
Reporter: 刘珍
Attachments: config.properties, q.sh
iotdb：0.12.3 rc1
receiver: fit 130.19
sender: fit 130.21
benchmark: fit 130.5 (master_0807)
benchmark connect the sender.
Run for about 20mins：
130.19
service network stop
sleep 5s
service network start
After benchmark finished：
execute q.sh
The sender's results is right. (1/sensor)
{color:#DE350B}* All the results on the receiver are incorrect*{color}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IOTDB-1897) cluster : The result of "select count(sensor) .. " is inconsistent with that of "select sensor .."
[
https://issues.apache.org/jira/browse/IOTDB-1897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17439122#comment-17439122
]
刘珍 commented on IOTDB-1897:
---
master 5 nodes 1rep （0073a28384cdb84e9469dbf98705ab158dd43a31），Same problem
> cluster : The result of "select count(sensor) .. " is inconsistent with
> that of "select sensor .."
>
>
> Key: IOTDB-1897
> URL: https://issues.apache.org/jira/browse/IOTDB-1897
> Project: Apache IoTDB
> Issue Type: Bug
> Components: Core/Cluster
>Affects Versions: 0.12.3
>Reporter: 刘珍
>Priority: Major
> Attachments: SessionExample.java, image-2021-10-26-17-38-05-803.png
>
>
> 测试版本：
> rel/0.12 958628804c14e58e5083233a6ca6aa370521b504
> 问题描述：
> 1. 集群信息
> cluster ： 5 nodes 1 replication
>
> seed_nodes=192.168.130.4:9003,192.168.130.10:9003,192.168.130.13:9003,192.168.130.17:9003,192.168.130.20:9003
> default_replica_num=1
> 2. 启动4/10/13/17/20
> 3.在17节点运行SessionExample.java (见附件)
> 编译与运行（运行时间约1.5分钟）：
> javac -cp ./lib/*:. SessionExample.java
> java -cp ./lib/*:. SessionExample
> 4. cli查询
> select count(s1) from root.sg5.d1
> select s1 from root.sg5.d1
> {color:#DE350B}*执行结果记录数不一致。*{color}
> !image-2021-10-26-17-38-05-803.png|thumbnail!
> select count(s1) from
> root.sg5.d1的结果为30003（{color:#DE350B}*这个结果也有问题，应该是3*{color}）
> select s1 from root.sg5.d1的结果为：
> Total line number = 1
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IOTDB-1927) [Benchmark] remove insertOneSensorBatch, use deviceSchema to control
张洪胤 created IOTDB-1927: -- Summary: [Benchmark] remove insertOneSensorBatch, use deviceSchema to control Key: IOTDB-1927 URL: https://issues.apache.org/jira/browse/IOTDB-1927 Project: Apache IoTDB Issue Type: Improvement Components: Benchmark Reporter: 张洪胤 Because of the structure change of benchmark, there is no place use insertOneSensorBatch, so I think remove it is a good idea. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IOTDB-1927) [Benchmark] remove insertOneSensorBatch, use deviceSchema to control
[ https://issues.apache.org/jira/browse/IOTDB-1927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] 张洪胤 reassigned IOTDB-1927: -- Assignee: 张洪胤 > [Benchmark] remove insertOneSensorBatch, use deviceSchema to control > > > Key: IOTDB-1927 > URL: https://issues.apache.org/jira/browse/IOTDB-1927 > Project: Apache IoTDB > Issue Type: Improvement > Components: Benchmark >Reporter: 张洪胤 >Assignee: 张洪胤 >Priority: Major > Original Estimate: 24h > Remaining Estimate: 24h > > Because of the structure change of benchmark, there is no place use > insertOneSensorBatch, so I think remove it is a good idea. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IOTDB-1619) There is an error msg when I restart iotdb-cluster
[ https://issues.apache.org/jira/browse/IOTDB-1619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17437788#comment-17437788 ] 刘珍 commented on IOTDB-1619: --- 1203rc1 resolved. > There is an error msg when I restart iotdb-cluster > -- > > Key: IOTDB-1619 > URL: https://issues.apache.org/jira/browse/IOTDB-1619 > Project: Apache IoTDB > Issue Type: Bug > Components: Core/Cluster >Reporter: FengQingxin >Priority: Major > Labels: pull-request-available > Attachments: image-2021-09-03-17-36-27-985.png > > > Hi > I met a error msg when I try to restart an iotdb-cluster[3 > nodes，default_replica_num=2] . > First I restarted the cluster,and try to insert data to it. > Second using "stop-node.sh" to stop it. > Third reboot server. Then using "start-node.sh" to restart it. > At this time , I met the error msg"2021-09-03 16:33:05,237 [main] ERROR > o.a.i.c.l.m.CommittedEntryManager:252 - missing log entry [last: -1, append > at: 5397176]" > !image-2021-09-03-17-36-27-985.png! > Please check this. > Thanks. > B.R. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-1963) master ：Compaction recover causes of data loss (Before this problem there was the kill operation in revover）
刘珍 created IOTDB-1963:
-
Summary: master ：Compaction recover causes of data loss (Before
this problem there was the kill operation in revover）
Key: IOTDB-1963
URL: https://issues.apache.org/jira/browse/IOTDB-1963
Project: Apache IoTDB
Issue Type: Bug
Components: Core/Compaction
Affects Versions: master branch
Reporter: 刘珍
Attachments: config.properties.1, config.properties.2
master 0073a28384cdb84e9469dbf98705ab158dd43a31
1. Run the Benchmark tool ，Execute 2 times in serial
See the attachment for configuration parameters
2. Execute q.sh （All SQL results：2）
Ensure that data is correct before the restart
3. Back up data
4.Execute stop-server.sh when compacting
5. Execute start-server.sh
Execute q.sh （All SQL results：2）
Run for about 30 minutes
Execute stop-server.sh when compacting
6. Back up data
7. Execute start-server.sh
Execute “killall -u xx” before "Congratulation, IoTDB is set up successfully.
Now, enjoy yourself!"
That is to say,
Execute “killall -u xx” when recovering.
8. Back up data
9. Execute start-server.sh
Execute q.sh（The expected value of all SQL results is：2） :
+-+
|count(root.ip5.ip52.d_12.s_0)|
+-+
|{color:red}*199804000*{color}|
+-+
Total line number = 1
It costs 69.841s
++
|count(root.ip5.ip52.d_2.s_0)|
++
| {color:red}*199803000*{color}|
++
Total line number = 1
It costs 64.820s
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (IOTDB-1402) Support the auto-create-schema mechanism for insertRecords in cluster module
[ https://issues.apache.org/jira/browse/IOTDB-1402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17440202#comment-17440202 ] 刘珍 commented on IOTDB-1402: --- master 0073a28384cdb84e9469dbf98705ab158dd43a31 5节点1副本 seed_nodes=192.168.130.4:9003,192.168.130.10:9003,192.168.130.11:9003,192.168.130.13:9003,192.168.130.19:9003 benchmark 在 130.10机器。 benchmark配置见附件，先启动写入测试，（3分钟后）再启动benchmark查询，测试过程中，cli执行几次(比如 3，4，5次）： delete storage group root.* count timeseries 期望结果： IoTDB> count timeseries +-+ |count| +-+ | 100| +-+ （执行几次delete storage group root.*后的）实际结果： IoTDB> count timeseries +-+ |count| +-+ | 96| +-+ benchmark异常日志： 2021-11-08 14:43:43,360 ERROR cn.edu.tsinghua.iotdb.benchmark.iotdb012.IoTDB:610 - exception occurred when execute query=SELECT count(s_0) FROM root.test.g_2.d_52 WHERE time >= 1537383617000 AND time <= 1537383867000 AND root.test.g_2.d_52.s_0 > -5 org.apache.iotdb.jdbc.IoTDBSQLException: 411: Error occurred in query process: Storage group is not set for current seriesPath: [root.test.g_2.d_52.s_0] at org.apache.iotdb.jdbc.IoTDBStatement.executeQuerySQL(IoTDBStatement.java:396) at org.apache.iotdb.jdbc.IoTDBStatement.executeQuery(IoTDBStatement.java:367) at org.apache.iotdb.jdbc.IoTDBStatement.executeQuery(IoTDBStatement.java:357) at cn.edu.tsinghua.iotdb.benchmark.iotdb012.IoTDB.lambda$executeQueryAndGetStatus$0(IoTDB.java:588) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) > Support the auto-create-schema mechanism for insertRecords in cluster module > > > Key: IOTDB-1402 > URL: https://issues.apache.org/jira/browse/IOTDB-1402 > Project: Apache IoTDB > Issue Type: Bug > Components: Core/Cluster >Reporter: Xinyu Tan >Priority: Major > Attachments: image-2021-08-31-15-46-20-284.png > > > On 28 May's commit 363bda92dbdb0f2f4739138ec858c91bb7c81efb, after starting > three node single replica cluster, sessionExample insertrecords interface > will be written in the failure. This is mainly due to problems with the > automatic schema creation logic of InsertRowsPlan in the cluster, which does > not handle BatchProcessException well -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (IOTDB-1960) cluster：count timeseries Msg: 304: Path [root.**] does not exist ，expect ：0
刘珍 created IOTDB-1960:
-
Summary: cluster：count timeseries Msg: 304: Path [root.**] does
not exist ，expect ：0
Key: IOTDB-1960
URL: https://issues.apache.org/jira/browse/IOTDB-1960
Project: Apache IoTDB
Issue Type: Bug
Components: Core/Cluster
Reporter: 刘珍
Attachments: image-2021-11-08-15-14-57-155.png,
image-2021-11-08-15-15-26-695.png
master 0073a28384cdb84e9469dbf98705ab158dd43a31
5 nodes ：
seed_nodes=192.168.130.4:9003,192.168.130.10:9003,192.168.130.11:9003,192.168.130.13:9003,192.168.130.19:9003
default_replica_num=1
IoTDB> delete storage group root.test;
Msg: The statement is executed successfully.
IoTDB> count timeseries
{color:#DE350B}*Msg: 304: Path [root.**] does not exist*{color}
IoTDB>
!image-2021-11-08-15-14-57-155.png!
expect ：
!image-2021-11-08-15-15-26-695.png!
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (IOTDB-1367) [Distributed] Runtime exception is not properly handled during forwarding
[
https://issues.apache.org/jira/browse/IOTDB-1367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17440173#comment-17440173
]
刘珍 commented on IOTDB-1367:
---
master (0073a28384cdb84e9469dbf98705ab158dd43a31)
CREATE TIMESERIES root.ip4.sg5.dev1.s_1 WITH DATATYPE=BOOLEAN, ENCODING=PLAIN;
CREATE TIMESERIES root.ip4.sg5.dev1.s_2 WITH DATATYPE=FLOAT, ENCODING=PLAIN;
ALTER timeseries root.ip4.sg5.dev1.s_1 ADD TAGS unit=kilometer
ALTER timeseries root.ip4.sg5.dev1.s_2 ADD TAGS description=salary
ALTER timeseries root.ip4.sg5.dev1.s_1 ADD ATTRIBUTES color=green, country=china
ALTER timeseries root.ip4.sg5.dev1.s_2 ADD ATTRIBUTES loaction=shandong,
customer=customer_name
ALTER timeseries root.ip4.sg5.dev1.s_1 UPSERT ALIAS=newAlias ;
ALTER timeseries root.ip4.sg5.dev1.s_2 UPSERT ALIAS=good ;
insert into root.ip4.sg5.dev1(time,s_1,s_2) values(11000,true,1.14);
insert into root.ip4.sg5.dev1(time,s_1,s_2) values(12000,false,2.14);
insert into root.ip4.sg5.dev1(time,s_1,s_2) values(13000,true,3.14);
insert into root.ip4.sg5.dev1(time,s_1,s_2) values(14000,false,9.14);
insert into root.ip4.sg5.dev1(time,s_1,s_2) values(15000,true,4.14);
insert into root.ip4.sg5.dev1(time,s_1,s_2) values(16000,false,5.14);
insert into root.ip4.sg5.dev1(time,s_1,s_2) values(17000,true,6.14);
insert into root.ip4.sg5.dev1(time,s_1,s_2) values(18000,false,7.14);
select avg(s_1) from root.ip4.sg5.dev1
{color:#DE350B}*Msg: 313: Request "Query aggregate: root.ip4.sg5.dev1.s_1 in
[Node(internalIp:192.168.130.19, metaPort:9003, nodeIdentifier:-854866469,
dataPort:40010, clientPort:6667, clientIp:192.168.130.19)]" timeout*{color}
!screenshot-1.png!
> [Distributed] Runtime exception is not properly handled during forwarding
> -
>
> Key: IOTDB-1367
> URL: https://issues.apache.org/jira/browse/IOTDB-1367
> Project: Apache IoTDB
> Issue Type: Bug
> Components: Core/Cluster
>Reporter: Tian Jiang
>Priority: Major
> Labels: client-me, distributed, query
> Attachments: image-2021-05-07-20-14-47-670.png, screenshot-1.png
>
>
> When I executed `select avg(s_0) from root.group_0.d_20` (notice that s_0 is
> boolean and does not support avg), I got `Msg: 313: Request "Query aggregate:
> root.group_0.d_20.s_0 in [Node(internalIp:192.168.130.4, metaPort:9003,
> nodeIdentifier:1436654207, dataPort:40003, clientPort:6667,
> clientIp:0.0.0.0)]" timeout`. While the log on node 192.168.130.4 says:
> !image-2021-05-07-20-14-47-670.png|thumbnail!
> The cause is that RunTimeExceptions are not caught explicitly in
> DataClusterServer and MetaClusterServer, so they are converted to TExceptions
> by Thrift and are recognized as network problems by the coordinator.
> The solution is either to catch runtime exceptions explicitly and create
> status codes for them or make the coordinator capable of resolving more
> TExceptions. Both ways have their difficulties, for the first one, it is
> nearly impossible to know how many runtime exceptions can occur; for the
> second one, when an exception is converted to a TException, only its message
> remains, so it is not easy to determine what exactly the problem is.
> ps: this only occurs when the coordinator does not have the corresponding
> data, so try querying another node if you can not repeat it.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (IOTDB-1955) cluster ：insert into root.test.g_5.d_85(s_0 ) values(1,4.56) expect syntax parsing error
刘珍 created IOTDB-1955:
-
Summary: cluster ：insert into root.test.g_5.d_85(s_0 )
values(1,4.56) expect syntax parsing error
Key: IOTDB-1955
URL: https://issues.apache.org/jira/browse/IOTDB-1955
Project: Apache IoTDB
Issue Type: Bug
Components: Planner/SQLParser
Affects Versions: master branch
Reporter: 刘珍
master 0073a28384cdb84e9469dbf98705ab158dd43a31
5 nodes single rep.
IoTDB> insert into root.test.g_5.d_85(s_0 ) values(1,4.56)
{color:#DE350B}*Msg: The statement is executed successfully.*{color}
expect :
Msg: 401: Error occurred while parsing SQL to physical plan: line 1:31
mismatched input 's_0' expecting {'*', '.', '('}
IoTDB>
IoTDB> SELECT s_0 FROM root.test.g_5.d_85 WHERE time >= 1537383267000 AND time
<= 1537383517000 AND root.test.g_5.d_85.s_0 > -5 order by time desc
Msg: 411: Error occurred in query process: Path [root.test.g_5.d_85.s_0] does
not exist
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (IOTDB-1402) Support the auto-create-schema mechanism for insertRecords in cluster module
[
https://issues.apache.org/jira/browse/IOTDB-1402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17440207#comment-17440207
]
刘珍 commented on IOTDB-1402:
---
这个问题也解决一下：
IoTDB> delete storage group root.test;
Msg: The statement is executed successfully.
IoTDB> count timeseries
{color:#DE350B}*Msg: 304: Path [root.**] does not exist*{color}
期望结果：
!screenshot-2.png!
> Support the auto-create-schema mechanism for insertRecords in cluster module
>
>
> Key: IOTDB-1402
> URL: https://issues.apache.org/jira/browse/IOTDB-1402
> Project: Apache IoTDB
> Issue Type: Bug
> Components: Core/Cluster
>Reporter: Xinyu Tan
>Priority: Major
> Attachments: image-2021-08-31-15-46-20-284.png,
> insert_config.properties, query_config.properties, screenshot-1.png,
> screenshot-2.png
>
>
> On 28 May's commit 363bda92dbdb0f2f4739138ec858c91bb7c81efb, after starting
> three node single replica cluster, sessionExample insertrecords interface
> will be written in the failure. This is mainly due to problems with the
> automatic schema creation logic of InsertRowsPlan in the cluster, which does
> not handle BatchProcessException well
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (IOTDB-1393) Request timed out when create time series
[ https://issues.apache.org/jira/browse/IOTDB-1393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17440262#comment-17440262 ] 刘珍 commented on IOTDB-1393: --- master 0073a28384cdb84e9469dbf98705ab158dd43a31 : seed_nodes=192.168.130.4:9003,192.168.130.10:9003,192.168.130.11:9003,192.168.130.13:9003,192.168.130.19:9003 default_replica_num=1 SQL: CREATE TIMESERIES root.devices.wf03.wt01.ts0 WITH DATATYPE=BOOLEAN, ENCODING=PLAIN, compression=UNCOMPRESSED create timeseries root.devices.wf03.wt01.ts1(elec_meter) with datatype=INT32, encoding=RLE, compression=SNAPPY,MAX_POINT_NUMBER=3 tags(tag1=t1, tag2=t2) attributes(attr1=a1, attr2=a2) create timeseries root.devices.wf03.wt01.ts2 with datatype=INT64, encoding=RLE, compression=LZ4 tags(tag1=t1, tag2=t2) attributes(attr1=a1, attr2=a2) RESULT: IoTDB> CREATE TIMESERIES root.devices.wf03.wt01.ts0 WITH DATATYPE=BOOLEAN, ENCODING=PLAIN, compression=UNCOMPRESSED Msg: 401: Error occurred while parsing SQL to physical plan: line 1:23 mismatched input 'devices' expecting ID IoTDB> create timeseries root.devices.wf03.wt01.ts1(elec_meter) with datatype=INT32, encoding=RLE, compression=SNAPPY,MAX_POINT_NUMBER=3 tags(tag1=t1, tag2=t2) attributes(attr1=a1, attr2=a2) Msg: 401: Error occurred while parsing SQL to physical plan: line 1:23 mismatched input 'devices' expecting ID IoTDB> create timeseries root.devices.wf03.wt01.ts2 with datatype=INT64, encoding=RLE, compression=LZ4 tags(tag1=t1, tag2=t2) attributes(attr1=a1, attr2=a2) Msg: 401: Error occurred while parsing SQL to physical plan: line 1:23 mismatched input 'devices' expecting ID IoTDB> !screenshot-1.png! > Request timed out when create time series > - > > Key: IOTDB-1393 > URL: https://issues.apache.org/jira/browse/IOTDB-1393 > Project: Apache IoTDB > Issue Type: Bug > Components: Core/Cluster >Affects Versions: 0.12.0 >Reporter: LuMing >Priority: Major > Attachments: screenshot-1.png > > > 1.client connected > 2.execute statement > CREATE TIMESERIES root.devices.wf03.wt01.ts0 WITH DATATYPE=BOOLEAN, > ENCODING=PLAIN, compression=UNCOMPRESSED > create timeseries root.devices.wf03.wt01.ts1(elec_meter) with > datatype=INT32, encoding=RLE, compression=SNAPPY,MAX_POINT_NUMBER=3 > tags(tag1=t1, tag2=t2) attributes(attr1=a1, attr2=a2) > create timeseries root.devices.wf03.wt01.ts2 with datatype=INT64, > encoding=RLE, compression=LZ4 tags(tag1=t1, tag2=t2) attributes(attr1=a1, > attr2=a2)3.result > 3. result > !https://clouddevops.huawei.com/vision-file-storage/api/file/download/upload-v2/2021/4/18/z00293891/8ccad779814e46faaadc92ad27397141/image.png! > 4. log segments > 2021-05-18 19:39:07,430 | DEBUG | [DataClientThread-5] | Meta: synchronizing > commitIndex -1/0 | org.apache.iotdb.cluster.server.member.RaftMember > (RaftMember.java:906) > 2021-05-18 19:39:07,473 | DEBUG | > [Data(node1:22250)-HeartbeatThread@1621328224936] | Data(node1:22250): > Heartbeat from leader Node(internalIp:node1, metaPort:22250, > nodeIdentifier:-1394469830, dataPort:22252, clientPort:22260, clientIp:node1) > is still valid | org.apache.iotdb.cluster.server.heartbeat.HeartbeatThread > (HeartbeatThread.java:100) > 2021-05-18 19:39:07,473 | DEBUG | > [Data(node2:22250)-HeartbeatThread@1621328224966] | Data(node2:22250): > Heartbeat from leader Node(internalIp:node2, metaPort:22250, > nodeIdentifier:-1395157557, dataPort:22252, clientPort:22260, clientIp:node2) > is still valid | org.apache.iotdb.cluster.server.heartbeat.HeartbeatThread > (HeartbeatThread.java:100) > 2021-05-18 19:39:07,486 | DEBUG | > [Data(node3:22250)-HeartbeatThread@1621328224906] | Data(node3:22250): Send > heartbeat to 2 followers | > org.apache.iotdb.cluster.server.heartbeat.HeartbeatThread > (HeartbeatThread.java:150) > 2021-05-18 19:39:08,005 | DEBUG | [MetaHeartbeatClientThread-1] | Meta: > Inconsistent log found, leaderCommit: 0-6, localCommit: -1--1, localLast: 0-6 > | org.apache.iotdb.cluster.server.member.RaftMember (RaftMember.java:423) > *2021-05-18 19:39:08,431 | WARN | [DataClientThread-5] | Meta: Failed to > synchronize with the leader after 20018ms | > *org.apache.iotdb.cluster.server.member.RaftMember (RaftMember.java:927) > 2021-05-18 19:39:08,432 | DEBUG | [DataClientThread-5] | Exception occurred > when applying seriesPath: root.devices.wf03.wt01.ts2, resultDataType: INT64, > encoding: RLE, compression: LZ4, tagOffset: -1,term:19,index:4 | > org.apache.iotdb.cluster.log.applier.AsyncDataLogApplier > (AsyncDataLogApplier.java:95) > org.apache.iotdb.db.exception.metadata.Stor
[jira] [Created] (IOTDB-1900) [Benchmark] When set IS_SENSOR_TS_ALIGNMENT=true, there is need to control of the ratio of null sensor of a device
张洪胤 created IOTDB-1900: -- Summary: [Benchmark] When set IS_SENSOR_TS_ALIGNMENT=true, there is need to control of the ratio of null sensor of a device Key: IOTDB-1900 URL: https://issues.apache.org/jira/browse/IOTDB-1900 Project: Apache IoTDB Issue Type: Improvement Components: Benchmark Reporter: 张洪胤 Assignee: 张洪胤 when set IS_SENSOR_TS_ALIGNMENT=true, iotdb-benchmark will write data one sensor per time. And I think there is need to control the ratio of null sensor number of a device at a timestamp, for example, the data that benchmark generate can be(eg. ratio = 0.5) ||Time||s_1||s_2||s_3||s_4||s_5||s_6||s_7||s_8||s_9||s_10|| ||null|6|null|null|null|7|8|9|10|null| |1|1|null|2|null|3|null|4|null|5|null| -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-2097) Fix aborting compaction task when deleting time partition
周沛辰 created IOTDB-2097: -- Summary: Fix aborting compaction task when deleting time partition Key: IOTDB-2097 URL: https://issues.apache.org/jira/browse/IOTDB-2097 Project: Apache IoTDB Issue Type: Bug Affects Versions: 0.13.0-SNAPSHOT Reporter: 周沛辰 Assignee: 周沛辰 Fix For: 0.13.0-SNAPSHOT Currently, there is a problem in aborting compaction tasks when a time partition dir is being deleted. And currently, we abort all compaction tasks under the physical storage group, we should only abort the compaction tasks under the deleted time partition in the virtual storage group. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (IOTDB-2096) Fix aborting compaction task when deleting time partition
周沛辰 created IOTDB-2096: -- Summary: Fix aborting compaction task when deleting time partition Key: IOTDB-2096 URL: https://issues.apache.org/jira/browse/IOTDB-2096 Project: Apache IoTDB Issue Type: Bug Affects Versions: 0.13.0-SNAPSHOT Reporter: 周沛辰 Assignee: 周沛辰 Fix For: 0.13.0-SNAPSHOT Currently, there is a problem in aborting compaction tasks when a time partition dir is being deleted. And currently, we abort all compaction tasks under the physical storage group, we should only abort the compaction tasks under the deleted time partition in the virtual storage group. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (IOTDB-2098) Fix priority bug of cross space task
周沛辰 created IOTDB-2098: -- Summary: Fix priority bug of cross space task Key: IOTDB-2098 URL: https://issues.apache.org/jira/browse/IOTDB-2098 Project: Apache IoTDB Issue Type: Bug Affects Versions: 0.13.0-SNAPSHOT Reporter: 周沛辰 Assignee: 周沛辰 Fix For: 0.13.0-SNAPSHOT We specify that when two compaction tasks have the same number of seqFiles, the task with more unseqFiles has higher priority. But the current CompactionTaskComparator is written backwards, and part of the CI should be modified. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (IOTDB-2125) Create a session,open 2 “pool-14-IoTDB-RPC-Client” threads
刘珍 created IOTDB-2125:
-
Summary: Create a session,open 2 “pool-14-IoTDB-RPC-Client” threads
Key: IOTDB-2125
URL: https://issues.apache.org/jira/browse/IOTDB-2125
Project: Apache IoTDB
Issue Type: Bug
Components: Core/Server
Reporter: 刘珍
Attachments: config.properties
rel/0.12 *strong text*
Benchmark connects to IoTDB，and opens 2 “pool-14-IoTDB-RPC-Client” threads per
session.
cli doesn't have this problem.
1. Run benchmark (config.properties）
CLIENT_NUMBER={color:#DE350B}20{color}
2. jstack iotdb_pid > a.out
grep "pool-14-IoTDB-RPC-Client" a.out |wc -l
{color:#DE350B}*40*{color}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (IOTDB-2125) Create a session,open 2 “pool-14-IoTDB-RPC-Client” threads
[
https://issues.apache.org/jira/browse/IOTDB-2125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17455054#comment-17455054
]
刘珍 commented on IOTDB-2125:
---
看起来还是benchmark的问题，创建单个Session连接，对应创建1个“pool-14-IoTDB-RPC-Client”线程，没发现新建1个session打开2个client的现象。
> Create a session,open 2 “pool-14-IoTDB-RPC-Client” threads
> --
>
> Key: IOTDB-2125
> URL: https://issues.apache.org/jira/browse/IOTDB-2125
> Project: Apache IoTDB
> Issue Type: Bug
> Components: Core/Server
>Affects Versions: 0.12.3
>Reporter: 刘珍
>Priority: Critical
> Attachments: config.properties
>
>
> rel/0.12
> Benchmark connects to IoTDB，and opens 2 “pool-14-IoTDB-RPC-Client” threads
> per session.
> cli doesn't have this problem.
> 1. Run benchmark (config.properties）
> DB_SWITCH=IoTDB-012-*SESSION_BY_TABLET*
> CLIENT_NUMBER={color:#DE350B}20{color}
> 2. jstack iotdb_pid > a.out
> grep "pool-14-IoTDB-RPC-Client" a.out |wc -l
> {color:#DE350B}*40*{color}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (IOTDB-2126) The content of the file header is not MAGIC_STRING（TsFile），after IoTDB is restarted, there is no exception and this tsfile is deleted
刘珍 created IOTDB-2126:
-
Summary: The content of the file header is not
MAGIC_STRING（TsFile），after IoTDB is restarted, there is no exception and this
tsfile is deleted
Key: IOTDB-2126
URL: https://issues.apache.org/jira/browse/IOTDB-2126
Project: Apache IoTDB
Issue Type: Bug
Components: Core/TsFile
Affects Versions: 0.12.3, 0.12.4
Reporter: 刘珍
Attachments: image-2021-12-08-17-21-27-652.png,
image-2021-12-08-17-22-10-608.png, image-2021-12-08-17-24-16-631.png
rel/0.12 fa2669824e681b34a2704242ad24b82325244a61
1. cli ：generate test data
set storage group to root.sg;
CREATE TIMESERIES root.sg.d_0.s_0 WITH DATATYPE=INT64, ENCODING=PLAIN;
insert into root.sg.d_0(time,s_0) values(1,100);
insert into root.sg.d_0(time,s_0) values(2,200);
*flush*;
IoTDB> select * from root.sg.d_0;
+-+---+
| Time|root.sg.d_0.s_0|
+-+---+
|1970-01-01T08:00:00.001+08:00|100|
|1970-01-01T08:00:00.002+08:00|200|
+-+---+
Total line number = 2
2../sbin/stop-server.sh
[iotdb@i-k2e7btap db]$ ls -l data/data/sequence/root.sg/0/0/
total 8
-rw-rw-r-- 1 iotdb iotdb 244 Dec 8 17:10 1638954616788-1-0-0.tsfile
-rw-rw-r-- 1 iotdb iotdb 57 Dec 8 17:10 1638954616788-1-0-0.tsfile.resource
3. vim data/data/sequence/root.sg/0/0/1638954616788-1-0-0.tsfile
!image-2021-12-08-17-21-27-652.png!
4. start-server.sh
{color:#DE350B}*MAGIC_STRING不正确的tsfile被删除，并且没有异常信息*{color}。
1638954616788-1-0-0.tsfile is {color:#DE350B}*deleted*{color}
{color:#DE350B}*No exception message was thrown*{color}
!image-2021-12-08-17-22-10-608.png!
!image-2021-12-08-17-24-16-631.png!
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
