[jira] [Created] (IOTDB-5416) the metric's data is null and the cluster is slower 40% than the cluster with no IoTDB metric
刘俊男 created IOTDB-5416: -- Summary: the metric's data is null and the cluster is slower 40% than the cluster with no IoTDB metric Key: IOTDB-5416 URL: https://issues.apache.org/jira/browse/IOTDB-5416 Project: Apache IoTDB Issue Type: Bug Reporter: 刘俊男 Assignee: Hongyin Zhang Attachments: image-2023-01-13-14-34-18-741.png, image-2023-01-13-14-34-33-148.png !image-2023-01-13-14-34-18-741.png|thumbnail! !image-2023-01-13-14-34-33-148.png|thumbnail! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5415) Move parameters into correct ConfigClass
Yongzao Dan created IOTDB-5415: -- Summary: Move parameters into correct ConfigClass Key: IOTDB-5415 URL: https://issues.apache.org/jira/browse/IOTDB-5415 Project: Apache IoTDB Issue Type: Improvement Reporter: Yongzao Dan Assignee: Yongzao Dan -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5414) Timeseries with alias deleted success but can still be queried by alias
yanze chen created IOTDB-5414:
-
Summary: Timeseries with alias deleted success but can still be
queried by alias
Key: IOTDB-5414
URL: https://issues.apache.org/jira/browse/IOTDB-5414
Project: Apache IoTDB
Issue Type: Bug
Reporter: yanze chen
Assignee: yanze chen
{code:java}
IoTDB> create timeseries root.turbine.d1.s1(temprature) with datatype=FLOAT,
encoding=RLE, compression=SNAPPY
Msg: The statement is executed successfully.
IoTDB> create timeseries root.turbine.d1.s2 with datatype=FLOAT, encoding=RLE,
compression=SNAPPY
Msg: The statement is executed successfully.
IoTDB> SHOW TIMESERIES root.**
+--+--++++---++--++--+
| Timeseries| Alias|
Database|DataType|Encoding|Compression|Tags|Attributes|Deadband|DeadbandParameters|
+--+--++++---++--++--+
|root.turbine.d1.s1|temprature|root.turbine| FLOAT| RLE| SNAPPY|null|
null| null| null|
|root.turbine.d1.s2| null|root.turbine| FLOAT| RLE| SNAPPY|null|
null| null| null|
+--+--++++---++--++--+
Total line number = 2
It costs 0.109s
IoTDB> delete timeseries root.turbine.d1.s1
Msg: The statement is executed successfully.
IoTDB> SHOW TIMESERIES root.**
+--+-++++---++--++--+
| Timeseries|Alias|
Database|DataType|Encoding|Compression|Tags|Attributes|Deadband|DeadbandParameters|
+--+-++++---++--++--+
|root.turbine.d1.s2| null|root.turbine| FLOAT| RLE| SNAPPY|null|
null| null| null|
+--+-++++---++--++--+
Total line number = 1
It costs 0.022s
IoTDB> SHOW TIMESERIES root.turbine.d1.temprature
+--+--++++---++--++--+
| Timeseries| Alias|
Database|DataType|Encoding|Compression|Tags|Attributes|Deadband|DeadbandParameters|
+--+--++++---++--++--+
|root.turbine.d1.s1|temprature|root.turbine| FLOAT| RLE| SNAPPY|null|
null| null| null|
+--+--++++---++--++--+
Total line number = 1
It costs 0.019s {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IOTDB-5413) ReadWriteLock for CachedMTreeStore
yanze chen created IOTDB-5413: - Summary: ReadWriteLock for CachedMTreeStore Key: IOTDB-5413 URL: https://issues.apache.org/jira/browse/IOTDB-5413 Project: Apache IoTDB Issue Type: Improvement Reporter: yanze chen Assignee: yanze chen https://apache-iotdb.feishu.cn/docx/WwdAd6SYLofsAHxEJeRcDuWBnPh -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5412) Print Help Message when loading empty tsfile
yusicheng created IOTDB-5412: Summary: Print Help Message when loading empty tsfile Key: IOTDB-5412 URL: https://issues.apache.org/jira/browse/IOTDB-5412 Project: Apache IoTDB Issue Type: Improvement Reporter: yusicheng Assignee: yusicheng Fix For: master branch, 1.0.1 Print Help Message when loading empty tsfile -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IOTDB-5163) [monitor]the file size of sequence of datanode is different from actual facts
[
https://issues.apache.org/jira/browse/IOTDB-5163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17675942#comment-17675942
]
Liuxuxin commented on IOTDB-5163:
-
This bug cannot be reproduced now. We guessed that the issue of IOTDB-5286
might have caused the inaccurate file count, and as the ISSUE was fixed, the
bug no longer appeared.
> [monitor]the file size of sequence of datanode is different from actual facts
> -
>
> Key: IOTDB-5163
> URL: https://issues.apache.org/jira/browse/IOTDB-5163
> Project: Apache IoTDB
> Issue Type: Bug
>Affects Versions: 1.0.0
>Reporter: changxue
>Assignee: Liuxuxin
>Priority: Major
> Attachments: image-2022-12-09-14-24-03-964.png
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> [monitor]the file size of sequence of datanode is different from actual facts
> the monitor:
> !image-2022-12-09-14-24-03-964.png!
> the actual facts on disk:
> {code}
> 51M ./datanode/data/unsequence/root.test
> 51M ./datanode/data/unsequence
> 124G ./datanode/data/sequence/root.test
> 124G ./datanode/data/sequence
> 228G ./datanode/data
> 35M ./datanode/wal/root.test-3
> 66M ./datanode/wal/root.test-0
> 53M ./datanode/wal/root.test-1
> 80M ./datanode/wal/root.test-4
> 16M ./datanode/wal/root.test-2
> 248M ./datanode/wal
> 21G ./datanode/data/snapshot/root.test-3
> 21G ./datanode/data/snapshot/root.test-0
> 22G ./datanode/data/snapshot/root.test-1
> 21G ./datanode/data/snapshot/root.test-4
> 21G ./datanode/data/snapshot/root.test-2
> 104G ./datanode/data/snapshot
> {code}
> sequence:
> {code}
> [atmos@i-rh6m726k root.test]$ du -hl -d 1
> 26G ./4
> 26G ./0
> 24G ./3
> 26G ./1
> 25G ./2
> 124G .
> {code}
> the monitor show seq is about 22.7G but the disk is 124G
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IOTDB-5411) Write an error using the session interface
sunhao created IOTDB-5411: - Summary: Write an error using the session interface Key: IOTDB-5411 URL: https://issues.apache.org/jira/browse/IOTDB-5411 Project: Apache IoTDB Issue Type: Bug Components: Client/Java Reporter: sunhao Assignee: Hongyin Zhang Attachments: image-2023-01-12-18-17-00-706.png !image-2023-01-12-18-17-00-706.png|width=1035,height=188! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Reopened] (IOTDB-5061) Failed to rename mtree.snapshot.tmp to mtree.snapshot while creating mtree snapshot
[
https://issues.apache.org/jira/browse/IOTDB-5061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
刘珍 reopened IOTDB-5061:
---
rc/1.0.1 2023-01-07_09dd173
需要等ratis发版，目前此iotdb版本，缩容失败，报错：
> Failed to rename mtree.snapshot.tmp to mtree.snapshot while creating mtree
> snapshot
> ---
>
> Key: IOTDB-5061
> URL: https://issues.apache.org/jira/browse/IOTDB-5061
> Project: Apache IoTDB
> Issue Type: Bug
> Components: mpp-cluster
>Affects Versions: 0.14.0-SNAPSHOT
>Reporter: 刘珍
>Assignee: Song Ziyang
>Priority: Blocker
> Labels: pull-request-available
> Attachments: image-2022-12-17-08-39-00-520.png, iotdb_4593.conf,
> screenshot-1.png, screenshot-2.png, screenshot-3.png, screenshot-4.png
>
> Original Estimate: 2h
> Remaining Estimate: 2h
>
> m_1127_ffbdaf3
> 1. 启动3副本3C5D 集群
> 2.BM 写入数据，1小时后，缩容IP72 datanode。
> 3. 开始缩容，1小时40分钟IP72 刷大量ERROR（308个ERROR 日志文件 NPE）
> 2022-11-27 15:42:25,876 [3@group-00020006-StateMachineUpdater] ERROR
> o.a.i.d.m.m.s.MemMTreeSnapshotUtil:89 - {color:#DE350B}Failed to rename
> mtree.snapshot.tmp to mtree.snapshot while creating mtree snapshot.{color}
> 2022-11-27 15:42:26,157 [3@group-00020006-StateMachineUpdater] ERROR
> o.a.r.s.i.StateMachineUpdater:194 - 3@group-00020006-StateMachineUpdater
> caught a Throwable.
> {color:#DE350B}java.lang.NullPointerException: null{color}
> at
> org.apache.iotdb.db.metadata.tag.TagManager.createSnapshot(TagManager.java:79)
> at
> org.apache.iotdb.db.metadata.schemaregion.SchemaRegionMemoryImpl.createSnapshot(SchemaRegionMemoryImpl.java:456)
> at
> org.apache.iotdb.db.consensus.statemachine.SchemaRegionStateMachine.takeSnapshot(SchemaRegionStateMachine.java:62)
> at
> org.apache.iotdb.consensus.IStateMachine.takeSnapshot(IStateMachine.java:82)
> at
> org.apache.iotdb.consensus.ratis.ApplicationStateMachineProxy.takeSnapshot(ApplicationStateMachineProxy.java:212)
> at
> org.apache.ratis.server.impl.StateMachineUpdater.takeSnapshot(StateMachineUpdater.java:270)
> at
> org.apache.ratis.server.impl.StateMachineUpdater.checkAndTakeSnapshot(StateMachineUpdater.java:262)
> at
> org.apache.ratis.server.impl.StateMachineUpdater.run(StateMachineUpdater.java:186)
> at java.base/java.lang.Thread.run(Thread.java:834)
> 2022-11-27 15:42:26,158 [3@group-00020006-StateMachineUpdater] ERROR
> o.a.r.s.i.StateMachineUpdater:194 - 3@group-00020006-StateMachineUpdater
> caught a Throwable.
> java.lang.NullPointerException: null
> at
> org.apache.iotdb.db.metadata.tag.TagManager.createSnapshot(TagManager.java:79)
> at
> org.apache.iotdb.db.metadata.schemaregion.SchemaRegionMemoryImpl.createSnapshot(SchemaRegionMemoryImpl.java:456)
> at
> org.apache.iotdb.db.consensus.statemachine.SchemaRegionStateMachine.takeSnapshot(SchemaRegionStateMachine.java:62)
> at
> org.apache.iotdb.consensus.IStateMachine.takeSnapshot(IStateMachine.java:82)
> at
> org.apache.iotdb.consensus.ratis.ApplicationStateMachineProxy.takeSnapshot(ApplicationStateMachineProxy.java:212)
> at
> org.apache.ratis.server.impl.StateMachineUpdater.takeSnapshot(StateMachineUpdater.java:270)
> at
> org.apache.ratis.server.impl.StateMachineUpdater.checkAndTakeSnapshot(StateMachineUpdater.java:262)
> at
> org.apache.ratis.server.impl.StateMachineUpdater.run(StateMachineUpdater.java:183)
> at java.base/java.lang.Thread.run(Thread.java:834)
> 测试环境
> 1. 192.168.10.72~76
> ConfigNode
> MAX_HEAP_SIZE="8G"
> cn_connection_timeout_ms=12
> Common
> schema_region_consensus_protocol_class=org.apache.iotdb.consensus.ratis.RatisConsensus
> data_region_consensus_protocol_class=org.apache.iotdb.consensus.iot.IoTConsensus
> schema_replication_factor=3
> data_replication_factor=3
> connection_timeout_ms=12
> max_connection_for_internal_service=200
> max_waiting_time_when_insert_blocked=60
> query_timeout_threshold=3600
> DataNode
> MAX_HEAP_SIZE="256G"
> MAX_DIRECT_MEMORY_SIZE="32G"
> 2. bm配置见附件
> 3. ip72 ${iotdb_dir}下的脚本
> sleep 1h
> ./sbin/start-cli.sh -h 192.168.10.72 -e "show cluster" > bef_remove.out
> ./sbin/start-cli.sh -h 192.168.10.72 -e "show regions" >> bef_remove.out
> ./sbin/start-cli.sh -h 192.168.10.72 -e "show storage group" >> bef_remove.out
> ./sbin/remove-datanode.sh "192.168.10.72:6667" >> remove_ip72.out
> 4. 查看缩容结果，各节点日志
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IOTDB-5288) [Metric] Got a wrong number of files
[ https://issues.apache.org/jira/browse/IOTDB-5288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17675918#comment-17675918 ] Liuxuxin commented on IOTDB-5288: - This bug cannot be reproduced now. We guessed that the issue of IOTDB-5286 might have caused the inaccurate file count, and as the ISSUE was fixed, the bug no longer appeared. > [Metric] Got a wrong number of files > > > Key: IOTDB-5288 > URL: https://issues.apache.org/jira/browse/IOTDB-5288 > Project: Apache IoTDB > Issue Type: Bug >Affects Versions: 1.0.0 >Reporter: Qingxin Feng >Assignee: Liuxuxin >Priority: Minor > Labels: pull-request-available > Attachments: image-2022-12-27-08-39-27-765.png > > Original Estimate: 24h > Remaining Estimate: 24h > > commit version: version 1.0.1-SNAPSHOT (Build: 752d7cf) > Got a wrong number of files, like below picture. > !image-2022-12-27-08-39-27-765.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5410) Refine Session and SessionPoolIT
Eric Pai created IOTDB-5410: --- Summary: Refine Session and SessionPoolIT Key: IOTDB-5410 URL: https://issues.apache.org/jira/browse/IOTDB-5410 Project: Apache IoTDB Issue Type: Improvement Components: integration-test Reporter: Eric Pai Assignee: Eric Pai -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5409) [rel/0.13]Show TTL with wildcards is not supported
xiaozhihong created IOTDB-5409:
--
Summary: [rel/0.13]Show TTL with wildcards is not supported
Key: IOTDB-5409
URL: https://issues.apache.org/jira/browse/IOTDB-5409
Project: Apache IoTDB
Issue Type: Bug
Affects Versions: 0.13.4-SNAPSHOT
Reporter: xiaozhihong
Assignee: Yukun Zhou
In V0.13.4 snapshot, execute sql about TTL.
{code:java}
IoTDB> set storage group to root.sg;
Msg: The statement is executed successfully.
IoTDB> create storage group root.ln.sg;
Msg: The statement is executed successfully.
IoTDB> show all ttl;
+-+---+
|storage group|ttl(ms)|
+-+---+
| root.sg| null|
| root.ln.sg| null|
+-+---+
Total line number = 2
It costs 0.072s
IoTDB> set ttl to root.sg 360;
Msg: The statement is executed successfully.
IoTDB> show all ttl;
+-+---+
|storage group|ttl(ms)|
+-+---+
| root.sg|360|
| root.ln.sg| null|
+-+---+
Total line number = 2
It costs 0.005s
IoTDB> SHOW TTL ON root.sg;
+-+---+
|storage group|ttl(ms)|
+-+---+
| root.sg|360|
+-+---+
Total line number = 1
It costs 0.041s
IoTDB> SHOW TTL ON root.*;
+-+---+
|storage group|ttl(ms)|
+-+---+
+-+---+
Empty set.
It costs 0.005s
IoTDB> SHOW TTL ON root.**;
+-+---+
|storage group|ttl(ms)|
+-+---+
+-+---+
Empty set.
It costs 0.003s
{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (IOTDB-5397) The cluster goes wrong after insert 200 records of aligned 50w timeseries
[ https://issues.apache.org/jira/browse/IOTDB-5397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jialin Qiao reassigned IOTDB-5397: -- Assignee: (was: Jialin Qiao) > The cluster goes wrong after insert 200 records of aligned 50w timeseries > -- > > Key: IOTDB-5397 > URL: https://issues.apache.org/jira/browse/IOTDB-5397 > Project: Apache IoTDB > Issue Type: Bug >Reporter: changxue >Priority: Major > Attachments: IOTDB-5397_allnodes-log.tar.gz, config.properties, > image-2023-01-11-11-41-41-506.png, image-2023-01-11-11-42-04-777.png, > image-2023-01-11-14-14-12-596.png > > > The cluster goes wrong after insert 200 records of aligned 50w timeseries > iotdb master Build: 4a90dbc > reproduction: > 1. start 3C3D IoTDB cluster > 2. Insert values into IoTDB with benchmark, using the config in attachment > actual result: > 1. schema create successfully, value insert successfully > 2. data node show logs : > node 45: > !image-2023-01-11-11-41-41-506.png|width=700! > node 46: > !image-2023-01-11-11-42-04-777.png|width=700! > node 44: > !image-2023-01-11-14-14-12-596.png|width=700! > > expect result: > The IoTDB service should always work properly with normal operation. > 线索： > device=1 > sensors=50w > batch-size=100 > thrift 请求： 50*1*100*16 ～ 800M > 谭新宇： > 一般不建议这样来写入，需要控制每个 RPC 的大小，最好别超过几十 M > 这里要改的话是得在客户端这边搞限制，不允许这么大的请求进来 > 最好还是能在客户端搞一些请求分批 > 问题： > 正常的操作不应该破坏集群，使集群状态不正常 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5408) the cluster's status will be unkown or the node's will be not connected when i use benchmark to test
刘俊男 created IOTDB-5408: -- Summary: the cluster's status will be unkown or the node's will be not connected when i use benchmark to test Key: IOTDB-5408 URL: https://issues.apache.org/jira/browse/IOTDB-5408 Project: Apache IoTDB Issue Type: Bug Reporter: 刘俊男 Fix For: 1.0.0 Attachments: image-2023-01-12-16-12-25-500.png, image-2023-01-12-16-12-30-872.png 6台 4C 16G的机器（3C 3D） 或者30台（3C 27D） DataNode配置 MAX_HEAP_SIZE="12G" HEAP_NEWSIZE="12G" dn_metric_reporter_list=PROMETHEUS,IoTDB Confignode配置 MAX_HEAP_SIZE="12G" HEAP_NEWSIZE="12G" cn_metric_reporter_list=PROMETHEUS common配置 schema_replication_factor=3 data_replication_factor=3 enable_last_cache=false timestamp_precision=ns benchmark配置 PORT=6667 LOOP=50 DEVICE_NUMBER=1 SENSOR_NUMBER=100 OP_MIN_INTERVAL=0 BATCH_SIZE=100 CLIENT_NUM =5 TIMESTAMP_PRECISION=ns 当使用以上配置测试IoTDB集群时，会产生Unkown和can‘t concenct的情况，吞吐较单机版大大降低。 !image-2023-01-12-16-12-25-500.png|thumbnail! !image-2023-01-12-16-12-30-872.png|thumbnail! 测试报告【腾讯文档】IoTDB-1.0.0测试结果分析报告 https://docs.qq.com/doc/DQkFzRU5acHV1bmtN -- This message was sent by Atlassian Jira (v8.20.10#820010)
