[jira] [Commented] (IOTDB-4811) [ snapshot dir ] The folder name contains ".tmp."
[
https://issues.apache.org/jira/browse/IOTDB-4811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17628115#comment-17628115
]
suchenglong commented on IOTDB-4811:
The cause of the problem:
Due to the change of the implementation of IStateMachine#takeSnapshot
interface, the snapshots (snapshotId:.tMP_XX_xx) generated by the
implementation of the snapshot interface are in the same place, and
snapshot.log is in the consensus directory. The hard link file of the data is
in the data/snapshot directory.
The hard link file path uses only the snapshotId information of the
takeSnapshot interface to generate a snapshot path. As a result, after the
takeSnapshot interface is invoked to generate a snapshot, only the path in the
consensus directory is migrated. The file path under data/snapshot is not
migrated.
Modification Method:
A new takeSnapshot interface is added in IStateMachine and receives two
parameters. One is the path of the snapshot file directory and the other is
snapshotId. In addition, snapshotId can be used to create a snapshot directory.
> [ snapshot dir ] The folder name contains ".tmp."
> -
>
> Key: IOTDB-4811
> URL: https://issues.apache.org/jira/browse/IOTDB-4811
> Project: Apache IoTDB
> Issue Type: Bug
> Components: mpp-cluster
>Affects Versions: 0.14.0-SNAPSHOT
>Reporter: 刘珍
>Assignee: suchenglong
>Priority: Minor
> Attachments: more_dev.conf, screenshot-1.png, screenshot-2.png,
> screenshot-3.png
>
>
> master_1031_76b947f
> 3rep , 3C3D
> schema region : ratis
> data region : ratis
> take snapshot ，有2个问题：
> 问题1 ：
> after take snapshot , data snapshot dir {color:#DE350B}*contains
> ".tmp."*{color} (And there is no dataregion information ）
> !screenshot-1.png!
> 问题2：
> snapshot log dir :
> !screenshot-2.png!
> {color:#DE350B}*但是{color:#DE350B}*日志里的这个路径不正确*{color}：*{color}
> !screenshot-3.png!
> 测试环境
> 1. 192.168.10.68 / 62 /66 72CPU 256GB
> ConfigNode
> MAX_HEAP_SIZE="8G"
> Common :
> query_timeout_threshold=3600
> enable_partition=false
> schema_region_consensus_protocol_class=org.apache.iotdb.consensus.ratis.RatisConsensus
> data_region_consensus_protocol_class=org.apache.iotdb.consensus.ratis.RatisConsensus
> schema_replication_factor=3
> data_replication_factor=3
> DataNode :
> MAX_HEAP_SIZE="192G"
> MAX_DIRECT_MEMORY_SIZE="32G"
> dn_consensus_dir=/data/liuzhen_test/master_1031_76b947f/data_consensus
> 2. bm 配置见附件
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IOTDB-4839) [trigger]多个trigger叠加到一个timeseries上，插入时报错：355
[
https://issues.apache.org/jira/browse/IOTDB-4839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17628110#comment-17628110
]
liaolanyu commented on IOTDB-4839:
--
Fixed. The implemented Trigger Class should be modified.
> [trigger]多个trigger叠加到一个timeseries上，插入时报错：355
>
>
> Key: IOTDB-4839
> URL: https://issues.apache.org/jira/browse/IOTDB-4839
> Project: Apache IoTDB
> Issue Type: Bug
>Affects Versions: 0.14.0-SNAPSHOT
>Reporter: changxue
>Assignee: liaolanyu
>Priority: Major
> Attachments: DoubleValueMonitor.java,
> double-value-monitor-0.14-SNAPSHOT.jar, log_datanode_all.log
>
>
> [trigger]多个trigger叠加到一个timeseries上，插入时报错：355
>
> environment:
> 3C3D cluster , 10-31日master代码
>
> reproduction:
> 在start-cli.sh模式下，依次执行以下sql
> {code:java}
> CREATE TIMESERIES root.sg1.d1.s1 WITH DATATYPE=DOUBLE, ENCODING=PLAIN
> CREATE STATELESS TRIGGER `alert01` AFTER INSERT ON root.sg1.d1.s1 AS
> 'org.example.DoubleValueMonitor' WITH ( "lo" = '5' )
> INSERT INTO root.sg1.d1(timestamp, s1) VALUES (1, 0);
> INSERT INTO root.sg1.d1(timestamp, s1) VALUES (2, 2);
> INSERT INTO root.sg1.d1(timestamp, s1) VALUES (3, 4);
> INSERT INTO root.sg1.d1(timestamp, s1) VALUES (4, 6);
> INSERT INTO root.sg1.d1(timestamp, s1) VALUES (5, 8);
> -- 2条
> select * from root.ln.alerting;
> CREATE STATELESS TRIGGER `alert02` before INSERT ON root.sg1.d1.* AS
> 'org.example.DoubleValueMonitor' WITH ( 'lo' = '10', hi = 80 )
> CREATE TIMESERIES root.sg1.d1.s2 WITH DATATYPE=DOUBLE, ENCODING=PLAIN;
> INSERT INTO root.sg1.d1(timestamp, s1, s2) VALUES
> (6,4,5.1);
> INSERT INTO root.sg1.d1(timestamp, s1, s2) VALUES (7,8,4.567);
> -- 从这里开始报错
> INSERT INTO root.sg1.d1(timestamp, s1, s2) VALUES (8,10,18);
> INSERT INTO root.sg1.d1(timestamp, s1, s2) VALUES (9,20,1.8);
> INSERT INTO root.sg1.d1(timestamp, s1, s2) VALUES
> (10,120,80.123);
> {code}
>
> 错误日志datanode:
> {code:java}
> 2022-11-02 20:44:15,940
> [pool-25-IoTDB-ClientRPC-Processor-87$20221102_124416_04406_3] INFO
> o.a.i.d.m.p.Coordinator:123 - [QueryStart] sql: INSERT INTO
> root.sg1.d1(timestamp, s1, s2) VALUES (10,120,80.123)
> 2022-11-02 20:44:15,942
> [pool-25-IoTDB-ClientRPC-Processor-87$20221102_124416_04406_3.1.0] ERROR
> o.a.i.d.m.p.s.FragmentInstanceDispatcherImpl:173 - dispatch write failed.
> status: TSStatus(code:355, message:Meet trigger error before/after the
> insertion, the insertion itself is completed.), message: Meet trigger error
> before/after the insertion, the insertion itself is completed.
> 2022-11-02 20:44:15,943
> [pool-21-IoTDB-MPPCoordinator-4$20221102_124416_04406_3] INFO
> o.a.i.d.m.p.e.QueryExecution:159 - [ReleaseQueryResource] state is: FAILED
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (IOTDB-4839) [trigger]多个trigger叠加到一个timeseries上，插入时报错：355
[
https://issues.apache.org/jira/browse/IOTDB-4839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
liaolanyu reassigned IOTDB-4839:
Assignee: liaolanyu (was: Yuan Tian)
> [trigger]多个trigger叠加到一个timeseries上，插入时报错：355
>
>
> Key: IOTDB-4839
> URL: https://issues.apache.org/jira/browse/IOTDB-4839
> Project: Apache IoTDB
> Issue Type: Bug
>Affects Versions: 0.14.0-SNAPSHOT
>Reporter: changxue
>Assignee: liaolanyu
>Priority: Major
> Attachments: DoubleValueMonitor.java,
> double-value-monitor-0.14-SNAPSHOT.jar, log_datanode_all.log
>
>
> [trigger]多个trigger叠加到一个timeseries上，插入时报错：355
>
> environment:
> 3C3D cluster , 10-31日master代码
>
> reproduction:
> 在start-cli.sh模式下，依次执行以下sql
> {code:java}
> CREATE TIMESERIES root.sg1.d1.s1 WITH DATATYPE=DOUBLE, ENCODING=PLAIN
> CREATE STATELESS TRIGGER `alert01` AFTER INSERT ON root.sg1.d1.s1 AS
> 'org.example.DoubleValueMonitor' WITH ( "lo" = '5' )
> INSERT INTO root.sg1.d1(timestamp, s1) VALUES (1, 0);
> INSERT INTO root.sg1.d1(timestamp, s1) VALUES (2, 2);
> INSERT INTO root.sg1.d1(timestamp, s1) VALUES (3, 4);
> INSERT INTO root.sg1.d1(timestamp, s1) VALUES (4, 6);
> INSERT INTO root.sg1.d1(timestamp, s1) VALUES (5, 8);
> -- 2条
> select * from root.ln.alerting;
> CREATE STATELESS TRIGGER `alert02` before INSERT ON root.sg1.d1.* AS
> 'org.example.DoubleValueMonitor' WITH ( 'lo' = '10', hi = 80 )
> CREATE TIMESERIES root.sg1.d1.s2 WITH DATATYPE=DOUBLE, ENCODING=PLAIN;
> INSERT INTO root.sg1.d1(timestamp, s1, s2) VALUES
> (6,4,5.1);
> INSERT INTO root.sg1.d1(timestamp, s1, s2) VALUES (7,8,4.567);
> -- 从这里开始报错
> INSERT INTO root.sg1.d1(timestamp, s1, s2) VALUES (8,10,18);
> INSERT INTO root.sg1.d1(timestamp, s1, s2) VALUES (9,20,1.8);
> INSERT INTO root.sg1.d1(timestamp, s1, s2) VALUES
> (10,120,80.123);
> {code}
>
> 错误日志datanode:
> {code:java}
> 2022-11-02 20:44:15,940
> [pool-25-IoTDB-ClientRPC-Processor-87$20221102_124416_04406_3] INFO
> o.a.i.d.m.p.Coordinator:123 - [QueryStart] sql: INSERT INTO
> root.sg1.d1(timestamp, s1, s2) VALUES (10,120,80.123)
> 2022-11-02 20:44:15,942
> [pool-25-IoTDB-ClientRPC-Processor-87$20221102_124416_04406_3.1.0] ERROR
> o.a.i.d.m.p.s.FragmentInstanceDispatcherImpl:173 - dispatch write failed.
> status: TSStatus(code:355, message:Meet trigger error before/after the
> insertion, the insertion itself is completed.), message: Meet trigger error
> before/after the insertion, the insertion itself is completed.
> 2022-11-02 20:44:15,943
> [pool-21-IoTDB-MPPCoordinator-4$20221102_124416_04406_3] INFO
> o.a.i.d.m.p.e.QueryExecution:159 - [ReleaseQueryResource] state is: FAILED
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (IOTDB-4843) Two back quotes in the node path do not resolve to one
[ https://issues.apache.org/jira/browse/IOTDB-4843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sixing Wu reassigned IOTDB-4843: Assignee: Sixing Wu > Two back quotes in the node path do not resolve to one > -- > > Key: IOTDB-4843 > URL: https://issues.apache.org/jira/browse/IOTDB-4843 > Project: Apache IoTDB > Issue Type: Bug >Reporter: Sixing Wu >Assignee: Sixing Wu >Priority: Minor > Attachments: image-2022-11-03-11-43-33-070.png > > > create timeseries root.sg1.d1.`1``1` DOUBLE > !image-2022-11-03-11-43-33-070.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-4843) Two back quotes in the node path do not resolve to one
Sixing Wu created IOTDB-4843: Summary: Two back quotes in the node path do not resolve to one Key: IOTDB-4843 URL: https://issues.apache.org/jira/browse/IOTDB-4843 Project: Apache IoTDB Issue Type: Bug Reporter: Sixing Wu Attachments: image-2022-11-03-11-43-33-070.png create timeseries root.sg1.d1.`1``1` DOUBLE !image-2022-11-03-11-43-33-070.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-4752) some data is lost after the read-only node returns to normal
[
https://issues.apache.org/jira/browse/IOTDB-4752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jinrui Zhang reassigned IOTDB-4752:
---
Assignee: Haiming Zhu (was: 张洪胤)
> some data is lost after the read-only node returns to normal
>
>
> Key: IOTDB-4752
> URL: https://issues.apache.org/jira/browse/IOTDB-4752
> Project: Apache IoTDB
> Issue Type: Bug
> Components: mpp-cluster
>Affects Versions: 0.14.0-SNAPSHOT
>Reporter: 刘珍
>Assignee: Haiming Zhu
>Priority: Major
> Attachments: image-2022-10-25-16-22-00-198.png, iotdb_4752.conf,
> 同步完成_ip72.out, 同步完成_ip73_ip74.out
>
>
> m_1025_cbc6225
> schema region : ratis
> data region : multiLeader
> 3rep , 3C3D
> During benchmark writing, ip72 is set to read-only due to "no space left on
> device".
> Wait for the benchmark write to complete, ip72 release disk space.
> ip72 : SET SYSTEM TO RUNNING
> Wait for synchronization to complete
> ip72 : flush
> Perform query comparison，ip72 {color:#DE350B}*lost some data*{color}.
> "select count(s_0) ,count(s_9),count(s_99),count(s_999),count(s_) from
> root.** align by device"
> !image-2022-10-25-16-22-00-198.png!
> Test environment ：
> 1. 192.168.10.72 / 73 /74 48CPU 384GB
> benchmark : ip75 /home/liuzhen/benchmark/bm_0620_7ec96c1
> iotdb_dir : /ssd_data/mpp_test/m_1025_cbc6225
> ConfigNode
> MAX_HEAP_SIZE="8G"
> schema_region_consensus_protocol_class=org.apache.iotdb.consensus.ratis.RatisConsensus
> data_region_consensus_protocol_class=org.apache.iotdb.consensus.multileader.MultiLeaderConsensus
> schema_replication_factor=3
> data_replication_factor=3
> connection_timeout_ms=12
> schema_region_ratis_request_timeout_ms=120
> data_region_ratis_request_timeout_ms=120
> schema_region_ratis_max_retry_attempts=1
> data_region_ratis_max_retry_attempts=2
> DataNode
> MAX_HEAP_SIZE="256G"
> MAX_DIRECT_MEMORY_SIZE="32G"
> avg_series_point_number_threshold=1
> max_waiting_time_when_insert_blocked=360
> enable_seq_space_compaction=false
> enable_unseq_space_compaction=false
> enable_cross_space_compaction=false
> query_timeout_threshold=3600
> 2. benchmark configuration
> see attachment .
> 3. During benchmark writing, ip72 is set to read-only due to "no space left
> on device".
> 4. Wait for the benchmark write to complete, ip72 release disk space.
> 5. ip72 : SET SYSTEM TO RUNNING
> 6. Wait for synchronization to complete
> 7. ip72 : flush
> 8. Perform query comparison
> select count(s_0) ,count(s_9),count(s_99),count(s_999),count(s_) from
> root.** align by device
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IOTDB-4839) [trigger]多个trigger叠加到一个timeseries上，插入时报错：355
[
https://issues.apache.org/jira/browse/IOTDB-4839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17628073#comment-17628073
]
changxue commented on IOTDB-4839:
-
使用今早最新代码，仍然有这个问题。
> [trigger]多个trigger叠加到一个timeseries上，插入时报错：355
>
>
> Key: IOTDB-4839
> URL: https://issues.apache.org/jira/browse/IOTDB-4839
> Project: Apache IoTDB
> Issue Type: Bug
>Affects Versions: 0.14.0-SNAPSHOT
>Reporter: changxue
>Assignee: Yuan Tian
>Priority: Major
>
> [trigger]多个trigger叠加到一个timeseries上，插入时报错：355
>
> environment:
> 3C3D cluster , 10-31日master代码
>
> reproduction:
> 在start-cli.sh模式下，依次执行以下sql
> {code:java}
> CREATE TIMESERIES root.sg1.d1.s1 WITH DATATYPE=DOUBLE, ENCODING=PLAIN
> CREATE STATELESS TRIGGER `alert01` AFTER INSERT ON root.sg1.d1.s1 AS
> 'org.example.DoubleValueMonitor' WITH ( "lo" = '5' )
> INSERT INTO root.sg1.d1(timestamp, s1) VALUES (1, 0);
> INSERT INTO root.sg1.d1(timestamp, s1) VALUES (2, 2);
> INSERT INTO root.sg1.d1(timestamp, s1) VALUES (3, 4);
> INSERT INTO root.sg1.d1(timestamp, s1) VALUES (4, 6);
> INSERT INTO root.sg1.d1(timestamp, s1) VALUES (5, 8);
> -- 2条
> select * from root.ln.alerting;
> CREATE STATELESS TRIGGER `alert02` before INSERT ON root.sg1.d1.* AS
> 'org.example.DoubleValueMonitor' WITH ( 'lo' = '10', hi = 80 )
> CREATE TIMESERIES root.sg1.d1.s2 WITH DATATYPE=DOUBLE, ENCODING=PLAIN;
> INSERT INTO root.sg1.d1(timestamp, s1, s2) VALUES
> (6,4,5.1);
> INSERT INTO root.sg1.d1(timestamp, s1, s2) VALUES (7,8,4.567);
> -- 从这里开始报错
> INSERT INTO root.sg1.d1(timestamp, s1, s2) VALUES (8,10,18);
> INSERT INTO root.sg1.d1(timestamp, s1, s2) VALUES (9,20,1.8);
> INSERT INTO root.sg1.d1(timestamp, s1, s2) VALUES
> (10,120,80.123);
> {code}
>
> 错误日志datanode:
> {code:java}
> 2022-11-02 20:44:15,940
> [pool-25-IoTDB-ClientRPC-Processor-87$20221102_124416_04406_3] INFO
> o.a.i.d.m.p.Coordinator:123 - [QueryStart] sql: INSERT INTO
> root.sg1.d1(timestamp, s1, s2) VALUES (10,120,80.123)
> 2022-11-02 20:44:15,942
> [pool-25-IoTDB-ClientRPC-Processor-87$20221102_124416_04406_3.1.0] ERROR
> o.a.i.d.m.p.s.FragmentInstanceDispatcherImpl:173 - dispatch write failed.
> status: TSStatus(code:355, message:Meet trigger error before/after the
> insertion, the insertion itself is completed.), message: Meet trigger error
> before/after the insertion, the insertion itself is completed.
> 2022-11-02 20:44:15,943
> [pool-21-IoTDB-MPPCoordinator-4$20221102_124416_04406_3] INFO
> o.a.i.d.m.p.e.QueryExecution:159 - [ReleaseQueryResource] state is: FAILED
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (IOTDB-4842) Type infer error when insert a large number
[
https://issues.apache.org/jira/browse/IOTDB-4842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Haonan Hou reassigned IOTDB-4842:
-
Assignee: Haonan Hou
> Type infer error when insert a large number
> ---
>
> Key: IOTDB-4842
> URL: https://issues.apache.org/jira/browse/IOTDB-4842
> Project: Apache IoTDB
> Issue Type: Bug
> Components: Core/Engine
>Affects Versions: 0.13.0, 0.14.0-SNAPSHOT
>Reporter: Haonan Hou
>Assignee: Haonan Hou
>Priority: Major
>
> To reproduce:
> {code:java}
> IoTDB> insert into root.sg1.d2(time, s98, s99) values(10, 2,
> 27184088)
> Msg: 500: Unexpected errors: For input string: "27184088"
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IOTDB-4842) Type infer error when insert a large number
Haonan Hou created IOTDB-4842:
-
Summary: Type infer error when insert a large number
Key: IOTDB-4842
URL: https://issues.apache.org/jira/browse/IOTDB-4842
Project: Apache IoTDB
Issue Type: Bug
Components: Core/Engine
Affects Versions: 0.13.0, 0.14.0-SNAPSHOT
Reporter: Haonan Hou
To reproduce:
{code:java}
IoTDB> insert into root.sg1.d2(time, s98, s99) values(10, 2,
27184088)
Msg: 500: Unexpected errors: For input string: "27184088" {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IOTDB-4097) Implementation of Aligned timeseries in new cross space compaction
[ https://issues.apache.org/jira/browse/IOTDB-4097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17628054#comment-17628054 ] 周沛辰 commented on IOTDB-4097: Here is the doc of fast compaction performer: [https://apache-iotdb.feishu.cn/docx/doxcn4Zi8dXgiNyGjngKDuO4Mj2?from=from_copylink] > Implementation of Aligned timeseries in new cross space compaction > -- > > Key: IOTDB-4097 > URL: https://issues.apache.org/jira/browse/IOTDB-4097 > Project: Apache IoTDB > Issue Type: Improvement >Reporter: 周沛辰 >Assignee: 周沛辰 >Priority: Major > Original Estimate: 80h > Remaining Estimate: 80h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IOTDB-3928) Implementation of NonAligned timeseries in New Cross-Space Compaction performer
[ https://issues.apache.org/jira/browse/IOTDB-3928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17628053#comment-17628053 ] 周沛辰 commented on IOTDB-3928: Here is the doc of fast compaction performer: https://apache-iotdb.feishu.cn/docx/doxcn4Zi8dXgiNyGjngKDuO4Mj2?from=from_copylink > Implementation of NonAligned timeseries in New Cross-Space Compaction > performer > > > Key: IOTDB-3928 > URL: https://issues.apache.org/jira/browse/IOTDB-3928 > Project: Apache IoTDB > Issue Type: New Feature >Reporter: 周沛辰 >Assignee: 周沛辰 >Priority: Major > Labels: pull-request-available > Fix For: master branch > > Original Estimate: 80h > Remaining Estimate: 80h > > Implement and improve cross space compaction of nonAligned time series from > V0.12. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IOTDB-4632) [ MetaData ] org.apache.iotdb.db.exception.metadata.MeasurementAlreadyExistException: Path [xx] already exist
[ https://issues.apache.org/jira/browse/IOTDB-4632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17628036#comment-17628036 ] Yukun Zhou commented on IOTDB-4632: --- 一个可选的方案是，系统内部执行时，将超大的请求拆分为若干个较轻量的小请求然后进行稳定消费和执行。 > [ MetaData ] > org.apache.iotdb.db.exception.metadata.MeasurementAlreadyExistException: Path > [xx] already exist > - > > Key: IOTDB-4632 > URL: https://issues.apache.org/jira/browse/IOTDB-4632 > Project: Apache IoTDB > Issue Type: Bug > Components: mpp-cluster >Affects Versions: 0.14.0-SNAPSHOT >Reporter: 刘珍 >Assignee: Yukun Zhou >Priority: Major > Attachments: more_ts.conf, screenshot-1.png > > > master_1010_9917053 > schema region ： ratis > 3副本 > 500dev，10万sensor/dev , enable_auto_create_schema=false > 注册元数据，大量ERROR，部分dev没注册成功（ratis 超时？超时时间需可配置） > ERROR 信息： > 2022-10-13 11:37:36,676 > [192.168.10.62_50010@group-00020001-StateMachineUpdater] ERROR > o.a.i.d.m.v.SchemaExecutionVisitor:109 - IoTDB: MetaData error: > org.apache.iotdb.db.exception.metadata.MeasurementAlreadyExistException: Path > [root.test.g_1.d_221.s_48893] already exist > at > org.apache.iotdb.db.metadata.mtree.MTreeBelowSGMemoryImpl.createTimeseries(MTreeBelowSGMemoryImpl.java:218) > at > org.apache.iotdb.db.metadata.schemaregion.SchemaRegionMemoryImpl.createTimeseries(SchemaRegionMemoryImpl.java:622) > at > org.apache.iotdb.db.metadata.visitor.SchemaExecutionVisitor.visitCreateMultiTimeSeries(SchemaExecutionVisitor.java:106) > at > org.apache.iotdb.db.metadata.visitor.SchemaExecutionVisitor.visitCreateMultiTimeSeries(SchemaExecutionVisitor.java:63) > at > org.apache.iotdb.db.mpp.plan.planner.plan.node.metedata.write.CreateMultiTimeSeriesNode.accept(CreateMultiTimeSeriesNode.java:141) > at > org.apache.iotdb.db.consensus.statemachine.SchemaRegionStateMachine.write(SchemaRegionStateMachine.java:74) > at > org.apache.iotdb.consensus.ratis.ApplicationStateMachineProxy.applyTransaction(ApplicationStateMachineProxy.java:135) > at > org.apache.ratis.server.impl.RaftServerImpl.applyLogToStateMachine(RaftServerImpl.java:1588) > at > org.apache.ratis.server.impl.StateMachineUpdater.applyLog(StateMachineUpdater.java:239) > at > org.apache.ratis.server.impl.StateMachineUpdater.run(StateMachineUpdater.java:182) > at java.lang.Thread.run(Thread.java:748) > 测试环境 > 1. 192.168.10.62/66/68 物理机 72CPU 256GB > bm在64 > ConfigNode > MAX_HEAP_SIZE="8G" > MAX_DIRECT_MEMORY_SIZE="8G" > > schema_region_consensus_protocol_class=org.apache.iotdb.consensus.ratis.RatisConsensus > data_region_consensus_protocol_class=org.apache.iotdb.consensus.multileader.MultiLeaderConsensus > schema_replication_factor=3 > data_replication_factor=3 > connection_timeout_ms=120 > DataNode > MAX_HEAP_SIZE="192G" > MAX_DIRECT_MEMORY_SIZE="32G" > connection_timeout_ms=120 > max_connection_for_internal_service=1100 > enable_timed_flush_seq_memtable=true > seq_memtable_flush_interval_in_ms=360 > seq_memtable_flush_check_interval_in_ms=60 > enable_timed_flush_unseq_memtable=true > unseq_memtable_flush_interval_in_ms=360 > unseq_memtable_flush_check_interval_in_ms=60 > max_waiting_time_when_insert_blocked=360 > query_timeout_threshold=3600 > enable_auto_create_schema=false > 2. bm配置见附件 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-4841) [doc] Update user guide in website (query part)
Minghui Liu created IOTDB-4841: -- Summary: [doc] Update user guide in website (query part) Key: IOTDB-4841 URL: https://issues.apache.org/jira/browse/IOTDB-4841 Project: Apache IoTDB Issue Type: Task Reporter: Minghui Liu Assignee: Minghui Liu Fix For: master branch -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-4840) [schema] Fix MLog writing logic about template
yanze chen created IOTDB-4840: - Summary: [schema] Fix MLog writing logic about template Key: IOTDB-4840 URL: https://issues.apache.org/jira/browse/IOTDB-4840 Project: Apache IoTDB Issue Type: Bug Reporter: yanze chen Assignee: yanze chen Attachments: image-2022-11-02-20-52-49-392.png MLog entry should be splitted into actual fullPath and templateId !image-2022-11-02-20-52-49-392.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-4839) [trigger]多个trigger叠加到一个timeseries上，插入时报错：355
changxue created IOTDB-4839:
---
Summary: [trigger]多个trigger叠加到一个timeseries上，插入时报错：355
Key: IOTDB-4839
URL: https://issues.apache.org/jira/browse/IOTDB-4839
Project: Apache IoTDB
Issue Type: Bug
Affects Versions: 0.14.0-SNAPSHOT
Reporter: changxue
Assignee: Yuan Tian
[trigger]多个trigger叠加到一个timeseries上，插入时报错：355
environment:
3C3D cluster , 10-31日master代码
reproduction:
在start-cli.sh模式下，依次执行以下sql
{code:java}
CREATE TIMESERIES root.sg1.d1.s1 WITH DATATYPE=DOUBLE, ENCODING=PLAIN
CREATE STATELESS TRIGGER `alert01` AFTER INSERT ON root.sg1.d1.s1 AS
'org.example.DoubleValueMonitor' WITH ( "lo" = '5' )
INSERT INTO root.sg1.d1(timestamp, s1) VALUES (1, 0);
INSERT INTO root.sg1.d1(timestamp, s1) VALUES (2, 2);
INSERT INTO root.sg1.d1(timestamp, s1) VALUES (3, 4);
INSERT INTO root.sg1.d1(timestamp, s1) VALUES (4, 6);
INSERT INTO root.sg1.d1(timestamp, s1) VALUES (5, 8);
-- 2条
select * from root.ln.alerting;
CREATE STATELESS TRIGGER `alert02` before INSERT ON root.sg1.d1.* AS
'org.example.DoubleValueMonitor' WITH ( 'lo' = '10', hi = 80 )
CREATE TIMESERIES root.sg1.d1.s2 WITH DATATYPE=DOUBLE, ENCODING=PLAIN;
INSERT INTO root.sg1.d1(timestamp, s1, s2) VALUES
(6,4,5.1);
INSERT INTO root.sg1.d1(timestamp, s1, s2) VALUES (7,8,4.567);
-- 从这里开始报错
INSERT INTO root.sg1.d1(timestamp, s1, s2) VALUES (8,10,18);
INSERT INTO root.sg1.d1(timestamp, s1, s2) VALUES (9,20,1.8);
INSERT INTO root.sg1.d1(timestamp, s1, s2) VALUES
(10,120,80.123);
{code}
错误日志datanode:
{code:java}
2022-11-02 20:44:15,940
[pool-25-IoTDB-ClientRPC-Processor-87$20221102_124416_04406_3] INFO
o.a.i.d.m.p.Coordinator:123 - [QueryStart] sql: INSERT INTO
root.sg1.d1(timestamp, s1, s2) VALUES (10,120,80.123)
2022-11-02 20:44:15,942
[pool-25-IoTDB-ClientRPC-Processor-87$20221102_124416_04406_3.1.0] ERROR
o.a.i.d.m.p.s.FragmentInstanceDispatcherImpl:173 - dispatch write failed.
status: TSStatus(code:355, message:Meet trigger error before/after the
insertion, the insertion itself is completed.), message: Meet trigger error
before/after the insertion, the insertion itself is completed.
2022-11-02 20:44:15,943
[pool-21-IoTDB-MPPCoordinator-4$20221102_124416_04406_3] INFO
o.a.i.d.m.p.e.QueryExecution:159 - [ReleaseQueryResource] state is: FAILED
{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (IOTDB-4838) Adapt SchemaRegionSchemaFileImpl's recovery to Ratis.
[ https://issues.apache.org/jira/browse/IOTDB-4838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yukun Zhou reassigned IOTDB-4838: - Assignee: Yukun Zhou > Adapt SchemaRegionSchemaFileImpl's recovery to Ratis. > - > > Key: IOTDB-4838 > URL: https://issues.apache.org/jira/browse/IOTDB-4838 > Project: Apache IoTDB > Issue Type: Bug >Reporter: Yukun Zhou >Assignee: Yukun Zhou >Priority: Major > Fix For: master branch > > > Currently, the SchemaRegionSchemaFileImpl relies on mlog and schema file to > recover. > In cluster mode, schemaRegion relies on Ratis to guarantee consistency, while > raftlog takes repeating info of mlog. > We want to use raftlog to recover info not in snapshot and use schema file to > implement snapshot and online business. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-4838) Adapt SchemaRegionSchemaFileImpl's recovery to Ratis.
Yukun Zhou created IOTDB-4838: - Summary: Adapt SchemaRegionSchemaFileImpl's recovery to Ratis. Key: IOTDB-4838 URL: https://issues.apache.org/jira/browse/IOTDB-4838 Project: Apache IoTDB Issue Type: Bug Reporter: Yukun Zhou Currently, the SchemaRegionSchemaFileImpl relies on mlog and schema file to recover. In cluster mode, schemaRegion relies on Ratis to guarantee consistency, while raftlog takes repeating info of mlog. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-4837) Refine Set Schema Template Implementation with Procedure and 2PC
Yukun Zhou created IOTDB-4837: - Summary: Refine Set Schema Template Implementation with Procedure and 2PC Key: IOTDB-4837 URL: https://issues.apache.org/jira/browse/IOTDB-4837 Project: Apache IoTDB Issue Type: Bug Reporter: Yukun Zhou Assignee: Yukun Zhou Fix For: master branch Currently, the implementation of set schema template is not that robust enough. Thus refine the implementation with Procedure and new design. https://apache-iotdb.feishu.cn/docx/doxcnXewADHKWTpgJ5RnP4iyetd -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-4836) Support multi-tenancy
[ https://issues.apache.org/jira/browse/IOTDB-4836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Houliang Qi reassigned IOTDB-4836: -- Assignee: 任宇华 > Support multi-tenancy > - > > Key: IOTDB-4836 > URL: https://issues.apache.org/jira/browse/IOTDB-4836 > Project: Apache IoTDB > Issue Type: New Feature > Components: Core/Engine >Reporter: Houliang Qi >Assignee: 任宇华 >Priority: Major > > The design and user manual： > https://apache-iotdb.feishu.cn/drive/folder/fldcnM1FWjno8GDkBWXiK4J35Ib -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-4836) Support multi-tenancy
Houliang Qi created IOTDB-4836: -- Summary: Support multi-tenancy Key: IOTDB-4836 URL: https://issues.apache.org/jira/browse/IOTDB-4836 Project: Apache IoTDB Issue Type: New Feature Components: Core/Engine Reporter: Houliang Qi The design and user manual： https://apache-iotdb.feishu.cn/drive/folder/fldcnM1FWjno8GDkBWXiK4J35Ib -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-4835) Inner space compaction may be blocked
Jinrui Zhang created IOTDB-4835: --- Summary: Inner space compaction may be blocked Key: IOTDB-4835 URL: https://issues.apache.org/jira/browse/IOTDB-4835 Project: Apache IoTDB Issue Type: Bug Reporter: Jinrui Zhang Assignee: Liuxuxin Attachments: image-2022-11-02-17-32-11-934.png See the code below, !image-2022-11-02-17-32-11-934.png|width=664,height=221! Let's call the file which needn't be merged as an OK-file. When selecting the candidate files, an OK-file will block the search to next level and lead to no compaction task be added to the queue. Please check the logic here. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IOTDB-3633) [ compaction & raft snapshot ] When recovery , the merged files without snapshot are restored to level-0 tsfiles
[ https://issues.apache.org/jira/browse/IOTDB-3633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17627558#comment-17627558 ] Liuxuxin commented on IOTDB-3633: - One possible way to fix this problem would be to trigger a snapshot after a compaction ends and notify the consensus that a new snapshot has been created. However, this allows the consensus layer to couple to the compaction module, and it requires additional logic to handle as a standalone server without the consensus layer. > [ compaction & raft snapshot ] When recovery , the merged files without > snapshot are restored to level-0 tsfiles > > > Key: IOTDB-3633 > URL: https://issues.apache.org/jira/browse/IOTDB-3633 > Project: Apache IoTDB > Issue Type: Improvement > Components: mpp-cluster >Affects Versions: 0.14.0-SNAPSHOT >Reporter: 刘珍 >Assignee: Liuxuxin >Priority: Major > Attachments: image-2022-06-23-16-55-05-097.png, > image-2022-06-23-16-56-05-675.png > > > 1. 停止datanode（kill -9），没有做snapshot，有合并文件 > !image-2022-06-23-16-55-05-097.png! > 2. 重启恢复，恢复后的合并文件消解成合并发生前的0层文件 > !image-2022-06-23-16-56-05-675.png! > 期望，raft log恢复后，已经合并的tsfile，还是合并状态。 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-4834) Remove data in compaction when the datatype of one series is not consistent in different tsfile
Liuxuxin created IOTDB-4834: --- Summary: Remove data in compaction when the datatype of one series is not consistent in different tsfile Key: IOTDB-4834 URL: https://issues.apache.org/jira/browse/IOTDB-4834 Project: Apache IoTDB Issue Type: New Feature Reporter: Liuxuxin Assignee: Liuxuxin Fix For: master branch, 0.13.4-SNAPSHOT In some scenario, the data type of one series is different in different tsfile for some reason(eg, the bug in auto data type inference). Compaction should remove the data whose type is different with the type in MManager. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-4833) [0.14][confignode] 3C start-confignode.sh start 2c frist，warning but no no information about the node not started
[ https://issues.apache.org/jira/browse/IOTDB-4833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ZhangZhengming reassigned IOTDB-4833: - Assignee: Gaofei Cao > [0.14][confignode] 3C start-confignode.sh start 2c frist，warning but no no > information about the node not started > - > > Key: IOTDB-4833 > URL: https://issues.apache.org/jira/browse/IOTDB-4833 > Project: Apache IoTDB > Issue Type: Improvement >Affects Versions: 0.14.0-SNAPSHOT >Reporter: ZhangZhengming >Assignee: Gaofei Cao >Priority: Minor > Attachments: image-2022-11-02-15-01-33-130.png > > > 3C，启动2C，leader节点会报如下错误，但是根据如下信息看不到未启动节点的信息，建议在如下log里增加未启动confignode的internal > ip !image-2022-11-02-15-01-33-130.png|width=1133,height=192! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-4833) [0.14][confignode] 3C start-confignode.sh start 2c frist，warning but no no information about the node not started
ZhangZhengming created IOTDB-4833: - Summary: [0.14][confignode] 3C start-confignode.sh start 2c frist，warning but no no information about the node not started Key: IOTDB-4833 URL: https://issues.apache.org/jira/browse/IOTDB-4833 Project: Apache IoTDB Issue Type: Bug Affects Versions: 0.14.0-SNAPSHOT Reporter: ZhangZhengming Attachments: image-2022-11-02-15-01-33-130.png 3C，启动2C，leader节点会报如下错误，但是根据如下信息看不到未启动节点的信息，建议在如下log里增加未启动confignode的internal ip !image-2022-11-02-15-01-33-130.png|width=1133,height=192! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-4832) Introducing freemarker to auto-generate type-specific code
Alima777 created IOTDB-4832: --- Summary: Introducing freemarker to auto-generate type-specific code Key: IOTDB-4832 URL: https://issues.apache.org/jira/browse/IOTDB-4832 Project: Apache IoTDB Issue Type: New Feature Reporter: Alima777 Assignee: Alima777 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-4703) 3rep/3C3D , stop 1 datanode ,delete storage group root.** failed
[
https://issues.apache.org/jira/browse/IOTDB-4703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gaofei Cao reassigned IOTDB-4703:
-
Assignee: 伊丹翔 (was: Yongzao Dan)
> 3rep/3C3D , stop 1 datanode ,delete storage group root.** failed
>
>
> Key: IOTDB-4703
> URL: https://issues.apache.org/jira/browse/IOTDB-4703
> Project: Apache IoTDB
> Issue Type: Bug
> Components: mpp-cluster
>Affects Versions: 0.14.0-SNAPSHOT
>Reporter: 刘珍
>Assignee: 伊丹翔
>Priority: Major
>
> m_1019_f2ffb49
> 3rep ,3C3D
> stop ip73 datanode , ip72 cli execute "delete storage group root.**"
> ip72 datanode error log：
> 2022-10-21 09:16:09,286
> [pool-26-IoTDB-ClientRPC-Processor-987$20221021_011534_06996_3] ERROR
> o.a.i.d.m.p.e.c.e.ClusterConfigTaskExecutor:248 - Failed to execute delete
> storage group [root.**] in config node, status is TSStatus(code:506,
> subStatus:[TSStatus(code:400, {color:#DE350B}message:Invalidate cache
> failed), TSStatus(code:400, message:Invalidate cache failed),
> TSStatus(code:400, message:Invalidate cache failed)]).{color}
> 2022-10-21 09:16:09,288 [pool-23-IoTDB-MPPCoordinator-17] ERROR
> o.a.i.d.m.p.e.c.ConfigExecution:124 - Failures happened during running
> ConfigExecution.
> org.apache.iotdb.commons.exception.IoTDBException: null
> at
> org.apache.iotdb.db.mpp.plan.execution.config.executor.ClusterConfigTaskExecutor.deleteStorageGroup(ClusterConfigTaskExecutor.java:252)
> at
> org.apache.iotdb.db.mpp.plan.execution.config.metadata.DeleteStorageGroupTask.execute(DeleteStorageGroupTask.java:41)
> at
> org.apache.iotdb.db.mpp.plan.execution.config.ConfigExecution.start(ConfigExecution.java:99)
> at
> org.apache.iotdb.db.mpp.plan.Coordinator.execute(Coordinator.java:146)
> at
> org.apache.iotdb.db.service.thrift.impl.ClientRPCServiceImpl.executeStatement(ClientRPCServiceImpl.java:601)
> at
> org.apache.iotdb.service.rpc.thrift.IClientRPCService$Processor$executeStatement.getResult(IClientRPCService.java:3037)
> at
> org.apache.iotdb.service.rpc.thrift.IClientRPCService$Processor$executeStatement.getResult(IClientRPCService.java:3017)
> 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.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> at java.base/java.lang.Thread.run(Thread.java:834)
> ip72 confignode error log：
> 2022-10-21 09:22:03,847 [ProcExecWorker-2] ERROR
> o.a.i.c.c.s.SyncDataNodeClientPool:113 -{color:#DE350B}*
> INVALIDATE_SCHEMA_CACHE failed on DataNode TEndPoint(ip:192.168.10.73,
> port:9003)*{color}
> java.io.IOException: Borrow client from pool for node
> TEndPoint(ip:192.168.10.73, port:9003) failed.
> at
> org.apache.iotdb.commons.client.ClientManager.borrowClient(ClientManager.java:61)
> at
> org.apache.iotdb.confignode.client.sync.SyncDataNodeClientPool.sendSyncRequestToDataNodeWithRetry(SyncDataNodeClientPool.java:68)
> at
> org.apache.iotdb.confignode.procedure.env.ConfigNodeProcedureEnv.invalidateCache(ConfigNodeProcedureEnv.java:147)
> at
> org.apache.iotdb.confignode.procedure.impl.statemachine.DeleteStorageGroupProcedure.executeFromState(DeleteStorageGroupProcedure.java:90)
> at
> org.apache.iotdb.confignode.procedure.impl.statemachine.DeleteStorageGroupProcedure.executeFromState(DeleteStorageGroupProcedure.java:47)
> at
> org.apache.iotdb.confignode.procedure.impl.statemachine.StateMachineProcedure.execute(StateMachineProcedure.java:186)
> at
> org.apache.iotdb.confignode.procedure.Procedure.doExecute(Procedure.java:365)
> at
> org.apache.iotdb.confignode.procedure.ProcedureExecutor.executeProcedure(ProcedureExecutor.java:414)
> at
> org.apache.iotdb.confignode.procedure.ProcedureExecutor.executeProcedure(ProcedureExecutor.java:373)
> at
> org.apache.iotdb.confignode.procedure.ProcedureExecutor.access$300(ProcedureExecutor.java:50)
> at
> org.apache.iotdb.confignode.procedure.ProcedureExecutor$WorkerThread.run(ProcedureExecutor.java:741)
> Caused by: net.sf.cglib.core.CodeGenerationException:
> org.apache.thrift.transport.TTransportException-->java.net.ConnectException:
> Connection refused (Connection refused)
> at net.sf.cglib.core.ReflectUtils.newInstance(ReflectUtils.java:235)
> at net.sf.cglib.core.ReflectUtils.newInstance(ReflectUtils.java:220)
> at
>
[jira] [Assigned] (IOTDB-4823) [ delete storage group root.** ] The corresponding path and tsfile are not deleted
[
https://issues.apache.org/jira/browse/IOTDB-4823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gaofei Cao reassigned IOTDB-4823:
-
Assignee: 伊丹翔 (was: Yongzao Dan)
> [ delete storage group root.** ] The corresponding path and tsfile are not
> deleted
> ---
>
> Key: IOTDB-4823
> URL: https://issues.apache.org/jira/browse/IOTDB-4823
> Project: Apache IoTDB
> Issue Type: Bug
> Components: mpp-cluster
>Affects Versions: 0.14.0-SNAPSHOT
>Reporter: 刘珍
>Assignee: 伊丹翔
>Priority: Major
> Attachments: image-2022-11-01-15-16-55-472.png, iotdb_4823.conf
>
>
> master_1101_bc0e88b
> 3rep ， 3C3D
> schema region : ratis
> data region : multiLeader
> delete storage group root.**
> The corresponding path and tsfile are not deleted :
> !image-2022-11-01-15-16-55-472.png!
> ConfigNode leader (ip62) warn :
> 2022-11-01 14:58:25,186 [ProcExecWorker-10] WARN
> o.a.i.c.c.s.SyncDataNodeClientPool:104 -{color:#DE350B}*
> INVALIDATE_SCHEMA_CACHE failed on *{color}DataNode
> TEndPoint(ip:192.168.10.62, port:9003), because Error in calling method
> invalidateSchemaCache, retrying 0...
> 2022-11-01 14:58:29,609 [ProcedureWorkerThreadMonitor] WARN
> o.a.i.c.p.ProcedureExecutor$WorkerMonitor:811 - Worker stuck
> ProcExecWorker-9(pid=9), run time 24559 ms
> 2022-11-01 14:58:29,609 [ProcedureWorkerThreadMonitor] WARN
> o.a.i.c.p.ProcedureExecutor$WorkerMonitor:811 - Worker stuck
> ProcExecWorker-10(pid=10), run time 24558 ms
> 2022-11-01 14:58:29,609 [ProcedureWorkerThreadMonitor] WARN
> o.a.i.c.p.ProcedureExecutor$WorkerMonitor:811 - Worker stuck
> ProcExecWorker-11(pid=11), run time 24548 ms
> 2022-11-01 14:58:34,610 [ProcedureWorkerThreadMonitor] WARN
> o.a.i.c.p.ProcedureExecutor$WorkerMonitor:811 - Worker stuck
> ProcExecWorker-9(pid=9), run time 29560 ms
> 2022-11-01 14:58:34,610 [ProcedureWorkerThreadMonitor] WARN
> o.a.i.c.p.ProcedureExecutor$WorkerMonitor:811 - Worker stuck
> ProcExecWorker-10(pid=10), run time 29559 ms
> 2022-11-01 14:58:34,610 [ProcedureWorkerThreadMonitor] WARN
> o.a.i.c.p.ProcedureExecutor$WorkerMonitor:811 - Worker stuck
> ProcExecWorker-11(pid=11), run time 29549 ms
> 2022-11-01 14:58:37,869 [ProcExecWorker-13] WARN
> o.a.i.c.m.ClusterSchemaManager:333 - {color:#DE350B}*Adjust
> maxRegionGroupCount failed because StorageGroup doesn't exist*{color}
> org.apache.iotdb.confignode.exception.StorageGroupNotExistsException:
> StorageGroup: root.test.g_0 doesn't exist.
> at
> org.apache.iotdb.confignode.persistence.partition.PartitionInfo.getRegionCount(PartitionInfo.java:620)
> at
> org.apache.iotdb.confignode.manager.partition.PartitionManager.getRegionCount(PartitionManager.java:483)
> at
> org.apache.iotdb.confignode.manager.ClusterSchemaManager.adjustMaxRegionGroupCount(ClusterSchemaManager.java:299)
> at
> org.apache.iotdb.confignode.manager.ClusterSchemaManager.deleteStorageGroup(ClusterSchemaManager.java:145)
> at
> org.apache.iotdb.confignode.procedure.env.ConfigNodeProcedureEnv.deleteConfig(ConfigNodeProcedureEnv.java:125)
> at
> org.apache.iotdb.confignode.procedure.impl.schema.DeleteStorageGroupProcedure.executeFromState(DeleteStorageGroupProcedure.java:122)
> at
> org.apache.iotdb.confignode.procedure.impl.schema.DeleteStorageGroupProcedure.executeFromState(DeleteStorageGroupProcedure.java:48)
> at
> org.apache.iotdb.confignode.procedure.impl.statemachine.StateMachineProcedure.execute(StateMachineProcedure.java:186)
> at
> org.apache.iotdb.confignode.procedure.Procedure.doExecute(Procedure.java:365)
> at
> org.apache.iotdb.confignode.procedure.ProcedureExecutor.executeProcedure(ProcedureExecutor.java:414)
> at
> org.apache.iotdb.confignode.procedure.ProcedureExecutor.executeProcedure(ProcedureExecutor.java:373)
> at
> org.apache.iotdb.confignode.procedure.ProcedureExecutor.access$300(ProcedureExecutor.java:50)
> at
> org.apache.iotdb.confignode.procedure.ProcedureExecutor$WorkerThread.run(ProcedureExecutor.java:741)
> 测试流程：
> 1. 192.168.10.62/66/68 72C256GB
> ConfigNode
> MAX_HEAP_SIZE="8G"
> Common
> query_timeout_threshold=3600
> schema_region_consensus_protocol_class=org.apache.iotdb.consensus.ratis.RatisConsensus
> data_region_consensus_protocol_class=org.apache.iotdb.consensus.multileader.MultiLeaderConsensus
> schema_replication_factor=3
> data_replication_factor=3
> partition_region_ratis_request_timeout_ms=120
> schema_region_ratis_request_timeout_ms=120
> data_region_ratis_request_timeout_ms=120
> partition_region_ratis_max_retry_attempts=1
> schema_region_ratis_max_retry_attempts=1
> data_region_ratis_max_retry_attempts=1
> DataNode
> MAX_HEAP_SIZE="192G"
>
[jira] [Assigned] (IOTDB-4830) [ confignode ] remove datanode that has stopped ，confignode executes “DELETE_OLD_REGION_PEER” on this datanode
[
https://issues.apache.org/jira/browse/IOTDB-4830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gaofei Cao reassigned IOTDB-4830:
-
Assignee: 陈哲涵 (was: Gaofei Cao)
> [ confignode ] remove datanode that has stopped ，confignode executes
> “DELETE_OLD_REGION_PEER” on this datanode
> --
>
> Key: IOTDB-4830
> URL: https://issues.apache.org/jira/browse/IOTDB-4830
> Project: Apache IoTDB
> Issue Type: Bug
> Components: mpp-cluster
>Affects Versions: 0.14.0-SNAPSHOT
>Reporter: 刘珍
>Assignee: 陈哲涵
>Priority: Major
> Attachments: image-2022-11-02-14-55-28-013.png
>
>
> m_1102_09e2566
> 3rep , 3C5D
> stop 1 datanode (ip76)
> remove this stopped datanode (ip76)
> confignode log :
> 2022-11-02 14:34:23,637 [ProcExecWorker-9] ERROR
> o.a.i.c.c.s.SyncDataNodeClientPool:113 -
> {color:#DE350B}*DELETE_OLD_REGION_PEER*{color} failed on DataNode
> TEndPoint(ip:192.168.10.76, port:9003)
> {color:#DE350B}*“DELETE_OLD_REGION_PEER” does not need to be executed*{color}
> start ip76 datanode ， remove start execution on ip76 ，{color:#DE350B}* but
> its status is always Running*{color}
> !image-2022-11-02-14-55-28-013.png!
> ip76 datanode log （已经在执行remove了）：
> 2022-11-02 14:38:45,611 [pool-53-IoTDB-Region-Migrate-Pool-1] INFO
> o.a.i.d.s.RegionMigrateService$DeleteOldRegionPeerTask:493 - succeed to
> remove region DataRegion[12] consensus group
> TEST ENV
> 192.168.10.72~76
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (IOTDB-4829) Let NoMoreTsBlockEvent RPC is called in async way
[ https://issues.apache.org/jira/browse/IOTDB-4829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yuan Tian reassigned IOTDB-4829: Assignee: liaolanyu (was: Yuan Tian) > Let NoMoreTsBlockEvent RPC is called in async way > - > > Key: IOTDB-4829 > URL: https://issues.apache.org/jira/browse/IOTDB-4829 > Project: Apache IoTDB > Issue Type: Improvement >Reporter: Yuan Tian >Assignee: liaolanyu >Priority: Major > > Let NoMoreTsBlockEvent RPC is called in async way, otherwise it may occupy > precious query execution thread time. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-4819) Record concrete failure info in FI State and pass it to client
[ https://issues.apache.org/jira/browse/IOTDB-4819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yuan Tian reassigned IOTDB-4819: Assignee: liaolanyu (was: Yuan Tian) > Record concrete failure info in FI State and pass it to client > -- > > Key: IOTDB-4819 > URL: https://issues.apache.org/jira/browse/IOTDB-4819 > Project: Apache IoTDB > Issue Type: Improvement >Reporter: Yuan Tian >Assignee: liaolanyu >Priority: Major > > Currently, when any FI failed, in coordinator we will only track its state > and lack its concrete failure messages which cause users will only see 500: > Task was cancelled. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-4761) [ flush ] ERROR o.a.i.d.m.p.e.c.ConfigExecution:124 - Failures happened during running ConfigExecution
[ https://issues.apache.org/jira/browse/IOTDB-4761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaofei Cao reassigned IOTDB-4761: - Assignee: Gaofei Cao (was: 陈哲涵) > [ flush ] ERROR o.a.i.d.m.p.e.c.ConfigExecution:124 - Failures happened > during running ConfigExecution > -- > > Key: IOTDB-4761 > URL: https://issues.apache.org/jira/browse/IOTDB-4761 > Project: Apache IoTDB > Issue Type: Bug > Components: mpp-cluster >Affects Versions: 0.14.0-SNAPSHOT >Reporter: 刘珍 >Assignee: Gaofei Cao >Priority: Major > Attachments: screenshot-1.png > > > /ssd_data/mpp_test/m_1025_cbc6225 > schema region : ratis > data region : multiLeader > 3rep , 3C3D > During benchmark writing, ip72 is set to read-only due to "no space left on > device". > Wait for the benchmark write to complete, ip72 release disk space. > ip72 : SET SYSTEM TO RUNNING > Wait for synchronization to complete > ip72 : flush , datanode error log: > 2022-10-26 14:48:29,578 [pool-21-IoTDB-MPPCoordinator-14] ERROR > o.a.i.d.m.p.e.c.ConfigExecution:124 - Failures happened during running > ConfigExecution. > org.apache.thrift.TException: Error in calling method flush > at > org.apache.iotdb.commons.client.sync.SyncThriftClientWithErrorHandler.intercept(SyncThriftClientWithErrorHandler.java:94) > at > org.apache.iotdb.db.client.ConfigNodeClient$$EnhancerByCGLIB$$4b2c71c8.flush() > at > org.apache.iotdb.db.mpp.plan.execution.config.executor.ClusterConfigTaskExecutor.flush(ClusterConfigTaskExecutor.java:516) > at > org.apache.iotdb.db.mpp.plan.execution.config.sys.FlushTask.execute(FlushTask.java:58) > at > org.apache.iotdb.db.mpp.plan.execution.config.ConfigExecution.start(ConfigExecution.java:99) > at > org.apache.iotdb.db.mpp.plan.Coordinator.execute(Coordinator.java:146) > at > org.apache.iotdb.db.service.thrift.impl.ClientRPCServiceImpl.executeStatement(ClientRPCServiceImpl.java:601) > at > org.apache.iotdb.service.rpc.thrift.IClientRPCService$Processor$executeStatement.getResult(IClientRPCService.java:3037) > at > org.apache.iotdb.service.rpc.thrift.IClientRPCService$Processor$executeStatement.getResult(IClientRPCService.java:3017) > 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.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) > at > java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) > at java.base/java.lang.Thread.run(Thread.java:834) > Caused by: org.apache.thrift.TException: Fail to connect to any config node. > Please check server status > at > org.apache.iotdb.db.client.ConfigNodeClient.flush(ConfigNodeClient.java:722) > at > org.apache.iotdb.db.client.ConfigNodeClient$$EnhancerByCGLIB$$4b2c71c8.CGLIB$flush$70() > at > org.apache.iotdb.db.client.ConfigNodeClient$$EnhancerByCGLIB$$4b2c71c8$$FastClassByCGLIB$$46f69aba.invoke() > at net.sf.cglib.proxy.MethodProxy.invokeSuper(MethodProxy.java:228) > at > org.apache.iotdb.commons.client.sync.SyncThriftClientWithErrorHandler.intercept(SyncThriftClientWithErrorHandler.java:55) > ... 14 common frames omitted > !screenshot-1.png! > The test process is the same as > https://issues.apache.org/jira/browse/IOTDB-4752 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-4823) [ delete storage group root.** ] The corresponding path and tsfile are not deleted
[
https://issues.apache.org/jira/browse/IOTDB-4823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gaofei Cao reassigned IOTDB-4823:
-
Assignee: Yongzao Dan (was: Gaofei Cao)
> [ delete storage group root.** ] The corresponding path and tsfile are not
> deleted
> ---
>
> Key: IOTDB-4823
> URL: https://issues.apache.org/jira/browse/IOTDB-4823
> Project: Apache IoTDB
> Issue Type: Bug
> Components: mpp-cluster
>Affects Versions: 0.14.0-SNAPSHOT
>Reporter: 刘珍
>Assignee: Yongzao Dan
>Priority: Major
> Attachments: image-2022-11-01-15-16-55-472.png, iotdb_4823.conf
>
>
> master_1101_bc0e88b
> 3rep ， 3C3D
> schema region : ratis
> data region : multiLeader
> delete storage group root.**
> The corresponding path and tsfile are not deleted :
> !image-2022-11-01-15-16-55-472.png!
> ConfigNode leader (ip62) warn :
> 2022-11-01 14:58:25,186 [ProcExecWorker-10] WARN
> o.a.i.c.c.s.SyncDataNodeClientPool:104 -{color:#DE350B}*
> INVALIDATE_SCHEMA_CACHE failed on *{color}DataNode
> TEndPoint(ip:192.168.10.62, port:9003), because Error in calling method
> invalidateSchemaCache, retrying 0...
> 2022-11-01 14:58:29,609 [ProcedureWorkerThreadMonitor] WARN
> o.a.i.c.p.ProcedureExecutor$WorkerMonitor:811 - Worker stuck
> ProcExecWorker-9(pid=9), run time 24559 ms
> 2022-11-01 14:58:29,609 [ProcedureWorkerThreadMonitor] WARN
> o.a.i.c.p.ProcedureExecutor$WorkerMonitor:811 - Worker stuck
> ProcExecWorker-10(pid=10), run time 24558 ms
> 2022-11-01 14:58:29,609 [ProcedureWorkerThreadMonitor] WARN
> o.a.i.c.p.ProcedureExecutor$WorkerMonitor:811 - Worker stuck
> ProcExecWorker-11(pid=11), run time 24548 ms
> 2022-11-01 14:58:34,610 [ProcedureWorkerThreadMonitor] WARN
> o.a.i.c.p.ProcedureExecutor$WorkerMonitor:811 - Worker stuck
> ProcExecWorker-9(pid=9), run time 29560 ms
> 2022-11-01 14:58:34,610 [ProcedureWorkerThreadMonitor] WARN
> o.a.i.c.p.ProcedureExecutor$WorkerMonitor:811 - Worker stuck
> ProcExecWorker-10(pid=10), run time 29559 ms
> 2022-11-01 14:58:34,610 [ProcedureWorkerThreadMonitor] WARN
> o.a.i.c.p.ProcedureExecutor$WorkerMonitor:811 - Worker stuck
> ProcExecWorker-11(pid=11), run time 29549 ms
> 2022-11-01 14:58:37,869 [ProcExecWorker-13] WARN
> o.a.i.c.m.ClusterSchemaManager:333 - {color:#DE350B}*Adjust
> maxRegionGroupCount failed because StorageGroup doesn't exist*{color}
> org.apache.iotdb.confignode.exception.StorageGroupNotExistsException:
> StorageGroup: root.test.g_0 doesn't exist.
> at
> org.apache.iotdb.confignode.persistence.partition.PartitionInfo.getRegionCount(PartitionInfo.java:620)
> at
> org.apache.iotdb.confignode.manager.partition.PartitionManager.getRegionCount(PartitionManager.java:483)
> at
> org.apache.iotdb.confignode.manager.ClusterSchemaManager.adjustMaxRegionGroupCount(ClusterSchemaManager.java:299)
> at
> org.apache.iotdb.confignode.manager.ClusterSchemaManager.deleteStorageGroup(ClusterSchemaManager.java:145)
> at
> org.apache.iotdb.confignode.procedure.env.ConfigNodeProcedureEnv.deleteConfig(ConfigNodeProcedureEnv.java:125)
> at
> org.apache.iotdb.confignode.procedure.impl.schema.DeleteStorageGroupProcedure.executeFromState(DeleteStorageGroupProcedure.java:122)
> at
> org.apache.iotdb.confignode.procedure.impl.schema.DeleteStorageGroupProcedure.executeFromState(DeleteStorageGroupProcedure.java:48)
> at
> org.apache.iotdb.confignode.procedure.impl.statemachine.StateMachineProcedure.execute(StateMachineProcedure.java:186)
> at
> org.apache.iotdb.confignode.procedure.Procedure.doExecute(Procedure.java:365)
> at
> org.apache.iotdb.confignode.procedure.ProcedureExecutor.executeProcedure(ProcedureExecutor.java:414)
> at
> org.apache.iotdb.confignode.procedure.ProcedureExecutor.executeProcedure(ProcedureExecutor.java:373)
> at
> org.apache.iotdb.confignode.procedure.ProcedureExecutor.access$300(ProcedureExecutor.java:50)
> at
> org.apache.iotdb.confignode.procedure.ProcedureExecutor$WorkerThread.run(ProcedureExecutor.java:741)
> 测试流程：
> 1. 192.168.10.62/66/68 72C256GB
> ConfigNode
> MAX_HEAP_SIZE="8G"
> Common
> query_timeout_threshold=3600
> schema_region_consensus_protocol_class=org.apache.iotdb.consensus.ratis.RatisConsensus
> data_region_consensus_protocol_class=org.apache.iotdb.consensus.multileader.MultiLeaderConsensus
> schema_replication_factor=3
> data_replication_factor=3
> partition_region_ratis_request_timeout_ms=120
> schema_region_ratis_request_timeout_ms=120
> data_region_ratis_request_timeout_ms=120
> partition_region_ratis_max_retry_attempts=1
> schema_region_ratis_max_retry_attempts=1
> data_region_ratis_max_retry_attempts=1
> DataNode
>
[jira] [Assigned] (IOTDB-4703) 3rep/3C3D , stop 1 datanode ,delete storage group root.** failed
[
https://issues.apache.org/jira/browse/IOTDB-4703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gaofei Cao reassigned IOTDB-4703:
-
Assignee: Yongzao Dan (was: Gaofei Cao)
> 3rep/3C3D , stop 1 datanode ,delete storage group root.** failed
>
>
> Key: IOTDB-4703
> URL: https://issues.apache.org/jira/browse/IOTDB-4703
> Project: Apache IoTDB
> Issue Type: Bug
> Components: mpp-cluster
>Affects Versions: 0.14.0-SNAPSHOT
>Reporter: 刘珍
>Assignee: Yongzao Dan
>Priority: Major
>
> m_1019_f2ffb49
> 3rep ,3C3D
> stop ip73 datanode , ip72 cli execute "delete storage group root.**"
> ip72 datanode error log：
> 2022-10-21 09:16:09,286
> [pool-26-IoTDB-ClientRPC-Processor-987$20221021_011534_06996_3] ERROR
> o.a.i.d.m.p.e.c.e.ClusterConfigTaskExecutor:248 - Failed to execute delete
> storage group [root.**] in config node, status is TSStatus(code:506,
> subStatus:[TSStatus(code:400, {color:#DE350B}message:Invalidate cache
> failed), TSStatus(code:400, message:Invalidate cache failed),
> TSStatus(code:400, message:Invalidate cache failed)]).{color}
> 2022-10-21 09:16:09,288 [pool-23-IoTDB-MPPCoordinator-17] ERROR
> o.a.i.d.m.p.e.c.ConfigExecution:124 - Failures happened during running
> ConfigExecution.
> org.apache.iotdb.commons.exception.IoTDBException: null
> at
> org.apache.iotdb.db.mpp.plan.execution.config.executor.ClusterConfigTaskExecutor.deleteStorageGroup(ClusterConfigTaskExecutor.java:252)
> at
> org.apache.iotdb.db.mpp.plan.execution.config.metadata.DeleteStorageGroupTask.execute(DeleteStorageGroupTask.java:41)
> at
> org.apache.iotdb.db.mpp.plan.execution.config.ConfigExecution.start(ConfigExecution.java:99)
> at
> org.apache.iotdb.db.mpp.plan.Coordinator.execute(Coordinator.java:146)
> at
> org.apache.iotdb.db.service.thrift.impl.ClientRPCServiceImpl.executeStatement(ClientRPCServiceImpl.java:601)
> at
> org.apache.iotdb.service.rpc.thrift.IClientRPCService$Processor$executeStatement.getResult(IClientRPCService.java:3037)
> at
> org.apache.iotdb.service.rpc.thrift.IClientRPCService$Processor$executeStatement.getResult(IClientRPCService.java:3017)
> 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.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> at java.base/java.lang.Thread.run(Thread.java:834)
> ip72 confignode error log：
> 2022-10-21 09:22:03,847 [ProcExecWorker-2] ERROR
> o.a.i.c.c.s.SyncDataNodeClientPool:113 -{color:#DE350B}*
> INVALIDATE_SCHEMA_CACHE failed on DataNode TEndPoint(ip:192.168.10.73,
> port:9003)*{color}
> java.io.IOException: Borrow client from pool for node
> TEndPoint(ip:192.168.10.73, port:9003) failed.
> at
> org.apache.iotdb.commons.client.ClientManager.borrowClient(ClientManager.java:61)
> at
> org.apache.iotdb.confignode.client.sync.SyncDataNodeClientPool.sendSyncRequestToDataNodeWithRetry(SyncDataNodeClientPool.java:68)
> at
> org.apache.iotdb.confignode.procedure.env.ConfigNodeProcedureEnv.invalidateCache(ConfigNodeProcedureEnv.java:147)
> at
> org.apache.iotdb.confignode.procedure.impl.statemachine.DeleteStorageGroupProcedure.executeFromState(DeleteStorageGroupProcedure.java:90)
> at
> org.apache.iotdb.confignode.procedure.impl.statemachine.DeleteStorageGroupProcedure.executeFromState(DeleteStorageGroupProcedure.java:47)
> at
> org.apache.iotdb.confignode.procedure.impl.statemachine.StateMachineProcedure.execute(StateMachineProcedure.java:186)
> at
> org.apache.iotdb.confignode.procedure.Procedure.doExecute(Procedure.java:365)
> at
> org.apache.iotdb.confignode.procedure.ProcedureExecutor.executeProcedure(ProcedureExecutor.java:414)
> at
> org.apache.iotdb.confignode.procedure.ProcedureExecutor.executeProcedure(ProcedureExecutor.java:373)
> at
> org.apache.iotdb.confignode.procedure.ProcedureExecutor.access$300(ProcedureExecutor.java:50)
> at
> org.apache.iotdb.confignode.procedure.ProcedureExecutor$WorkerThread.run(ProcedureExecutor.java:741)
> Caused by: net.sf.cglib.core.CodeGenerationException:
> org.apache.thrift.transport.TTransportException-->java.net.ConnectException:
> Connection refused (Connection refused)
> at net.sf.cglib.core.ReflectUtils.newInstance(ReflectUtils.java:235)
> at net.sf.cglib.core.ReflectUtils.newInstance(ReflectUtils.java:220)
> at
>
[jira] [Assigned] (IOTDB-4546) Add Procedure development guide
[ https://issues.apache.org/jira/browse/IOTDB-4546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaofei Cao reassigned IOTDB-4546: - Assignee: 伊丹翔 (was: Gaofei Cao) > Add Procedure development guide > --- > > Key: IOTDB-4546 > URL: https://issues.apache.org/jira/browse/IOTDB-4546 > Project: Apache IoTDB > Issue Type: Improvement >Reporter: Jialin Qiao >Assignee: 伊丹翔 >Priority: Minor > > Add a guide for developing a new procedure process. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-4831) Save one rpc call in query processing
Yuan Tian created IOTDB-4831: Summary: Save one rpc call in query processing Key: IOTDB-4831 URL: https://issues.apache.org/jira/browse/IOTDB-4831 Project: Apache IoTDB Issue Type: Improvement Reporter: Yuan Tian Assignee: Yuan Tian Currently, even if there is no more data in server side, client will still need one more rpc call to fetch result and then client found that this rpc call return no data, it will end. However, we can add a `moreData` field in response to indicate that there is no more data in server side after this rpc call and client can use this filed to decide whether to do another one rpc to fetch data from server side. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IOTDB-3149) There is a difference between adding ** path and without a path to list user privileges
[
https://issues.apache.org/jira/browse/IOTDB-3149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17627500#comment-17627500
]
xiaozhihong commented on IOTDB-3149:
commit dbfacd9c1c85d61c658a151f1cd210ed41b8f44e
I verified.
!image-2022-11-02-15-25-32-903.png!
> There is a difference between adding ** path and without a path to list user
> privileges
>
>
> Key: IOTDB-3149
> URL: https://issues.apache.org/jira/browse/IOTDB-3149
> Project: Apache IoTDB
> Issue Type: Bug
> Components: Core/Server
>Affects Versions: master branch
>Reporter: xiaozhihong
>Assignee: 任宇华
>Priority: Minor
> Labels: pull-request-available
> Fix For: 0.14.0
>
> Attachments: image-2022-05-11-10-36-43-442.png,
> image-2022-10-31-11-13-24-388.png, image-2022-11-02-15-25-32-903.png
>
>
> List the privileges that a user has: After executing without the path
> (root.{*}{{*}}) and with the path (root.{{*}}{*}), there are differences in
> the privileges displayed by the user.
> The following SQL shows:
> LIST USER PRIVILEGES user01: Shows all the privileges of the current user.
> LIST PRIVILEGES USER user01 on root.**: Generally speaking, all paths are
> wildcarded **, but only the privileges of a certain path are currently
> displayed.
> {code:java}
> IoTDB> LIST USER PRIVILEGES user01;
> ++-+
> |role| privilege|
> ++-+
> | | root : SET_STORAGE_GROUP|
> | | root.ln : CREATE_TIMESERIES|
> | |root.** : SET_STORAGE_GROUP LIST_USER|
> | | root.ln.** : CREATE_TIMESERIES|
> ++-+
> Total line number = 4
> It costs 0.003s
> IoTDB> LIST PRIVILEGES USER user01 on root.**;
> ++-+
> |role| privilege|
> ++-+
> | |root.** : SET_STORAGE_GROUP LIST_USER|
> ++-+
> Total line number = 1
> It costs 0.003s
> {code}
> !image-2022-05-11-10-36-43-442.png!
>
>
>
> This problem has been solved, but new problems have been found.
> The user checks the permissions on the root. sg. ** path, and the root. ** is
> also matched
>
> !image-2022-10-31-11-13-24-388.png!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (IOTDB-4704) [ ConfigNode ] Wait 10 seconds and try again to create the region
[ https://issues.apache.org/jira/browse/IOTDB-4704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaofei Cao reassigned IOTDB-4704: - Assignee: 陈哲涵 (was: Yongzao Dan) > [ ConfigNode ] Wait 10 seconds and try again to create the region > - > > Key: IOTDB-4704 > URL: https://issues.apache.org/jira/browse/IOTDB-4704 > Project: Apache IoTDB > Issue Type: Improvement > Components: mpp-cluster >Affects Versions: 0.14.0-SNAPSHOT >Reporter: 刘珍 >Assignee: 陈哲涵 >Priority: Minor > > m_1019_f2ffb49 > 3rep , 3C3D > kill 1 datanode (ip74 ) when creating metadata , start ip74 datanode after > benchmark write done. > ERROR logs : > 2022-10-20 13:48:17,218 [pool-23-IoTDB-MultiLeaderConsensusRPC-Processor-1] > ERROR o.a.i.c.m.s.MultiLeaderRPCServiceProcessor:80 - unexpected > consensusGroupId DataRegion[5] for TSyncLogReq which size is 6 > ConfigNode wait 10s , try agagin to create the regions , 10s is too long . -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-4830) [ confignode ] remove datanode that has stopped ，confignode executes “DELETE_OLD_REGION_PEER” on this datanode
[
https://issues.apache.org/jira/browse/IOTDB-4830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
刘珍 reassigned IOTDB-4830:
-
Attachment: image-2022-11-02-14-55-28-013.png
Component/s: mpp-cluster
Sprint: 2022-11-Cluster
Affects Version/s: 0.14.0-SNAPSHOT
Assignee: Gaofei Cao
Description:
m_1102_09e2566
3rep , 3C5D
stop 1 datanode (ip76)
remove this stopped datanode (ip76)
confignode log :
2022-11-02 14:34:23,637 [ProcExecWorker-9] ERROR
o.a.i.c.c.s.SyncDataNodeClientPool:113 -
{color:#DE350B}*DELETE_OLD_REGION_PEER*{color} failed on DataNode
TEndPoint(ip:192.168.10.76, port:9003)
{color:#DE350B}*“DELETE_OLD_REGION_PEER” does not need to be executed*{color}
start ip76 datanode ， remove start execution on ip76 ， but its status is always
Running
!image-2022-11-02-14-55-28-013.png!
ip76 datanode log （已经在执行remove了）：
2022-11-02 14:38:45,611 [pool-53-IoTDB-Region-Migrate-Pool-1] INFO
o.a.i.d.s.RegionMigrateService$DeleteOldRegionPeerTask:493 - succeed to remove
region DataRegion[12] consensus group
TEST ENV
192.168.10.72~76
> [ confignode ] remove datanode that has stopped ，confignode executes
> “DELETE_OLD_REGION_PEER” on this datanode
> --
>
> Key: IOTDB-4830
> URL: https://issues.apache.org/jira/browse/IOTDB-4830
> Project: Apache IoTDB
> Issue Type: Bug
> Components: mpp-cluster
>Affects Versions: 0.14.0-SNAPSHOT
>Reporter: 刘珍
>Assignee: Gaofei Cao
>Priority: Major
> Attachments: image-2022-11-02-14-55-28-013.png
>
>
> m_1102_09e2566
> 3rep , 3C5D
> stop 1 datanode (ip76)
> remove this stopped datanode (ip76)
> confignode log :
> 2022-11-02 14:34:23,637 [ProcExecWorker-9] ERROR
> o.a.i.c.c.s.SyncDataNodeClientPool:113 -
> {color:#DE350B}*DELETE_OLD_REGION_PEER*{color} failed on DataNode
> TEndPoint(ip:192.168.10.76, port:9003)
> {color:#DE350B}*“DELETE_OLD_REGION_PEER” does not need to be executed*{color}
> start ip76 datanode ， remove start execution on ip76 ， but its status is
> always Running
> !image-2022-11-02-14-55-28-013.png!
> ip76 datanode log （已经在执行remove了）：
> 2022-11-02 14:38:45,611 [pool-53-IoTDB-Region-Migrate-Pool-1] INFO
> o.a.i.d.s.RegionMigrateService$DeleteOldRegionPeerTask:493 - succeed to
> remove region DataRegion[12] consensus group
> TEST ENV
> 192.168.10.72~76
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (IOTDB-4630) Implement observer pattern in LoadBalancing framework
[ https://issues.apache.org/jira/browse/IOTDB-4630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yongzao Dan reassigned IOTDB-4630: -- Assignee: Yongzao Dan (was: 陈哲涵) > Implement observer pattern in LoadBalancing framework > - > > Key: IOTDB-4630 > URL: https://issues.apache.org/jira/browse/IOTDB-4630 > Project: Apache IoTDB > Issue Type: Improvement >Reporter: Gaofei Cao >Assignee: Yongzao Dan >Priority: Major > > Many of the services running on ConfigNode-leader have a requirement to make > decisions when the status of a DataNode changed. Currently, we've implemented > a `Unknown-DataNode-Detector` service at NodeManager to periodically check > the DataNodes' status and notify other services when some DataNodes' status > changed. However, the `Unknown-DataNode-Detector` only check `Running` and > `Unknown` status and the notification is serial, which is a inferior > implementation for cluster version. > > Obviously, observer pattern is more suitable for soving this problem. And > there are some requirements that the observer pattern needs to satisfy: > > # The observed(nodeCache in NodeManager) should publish some information as > soon as some Nodes' status have changed. > # There observed may produce multiple information at the same time. i.e. > there are multiple Nodes changed their status within a heartbeat loop. > # The observers should receive the information and perform its own mission > asynchronously between each other. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-4830) [ config
刘珍 created IOTDB-4830: - Summary: [ config Key: IOTDB-4830 URL: https://issues.apache.org/jira/browse/IOTDB-4830 Project: Apache IoTDB Issue Type: Bug Reporter: 刘珍 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-4809) [ remove datanode ] ConsensusGroupNotExistException: The consensus group DataRegion[11] doesn't exist
[
https://issues.apache.org/jira/browse/IOTDB-4809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yongzao Dan reassigned IOTDB-4809:
--
Assignee: 陈哲涵 (was: Yongzao Dan)
> [ remove datanode ] ConsensusGroupNotExistException: The consensus group
> DataRegion[11] doesn't exist
> -
>
> Key: IOTDB-4809
> URL: https://issues.apache.org/jira/browse/IOTDB-4809
> Project: Apache IoTDB
> Issue Type: Bug
> Components: mpp-cluster
>Affects Versions: 0.14.0-SNAPSHOT
>Reporter: 刘珍
>Assignee: 陈哲涵
>Priority: Major
> Attachments: after_remove_regions_info.out,
> before_remove_regions_info.out, more_dev.conf, screenshot-1.png,
> screenshot-2.png
>
>
> m_1031_76b947f
> 3rep , 3C5D
> schema region : ratis
> data region : multiLeader
> {color:#DE350B}*This issue contains 3 bugs*{color}
> benchmark runs for 1 hour and execute remove (ip72) datanode , ip72 datanode
> brushes ERROR logs ：
> 2022-10-31 17:48:06,277
> [pool-25-IoTDB-ClientRPC-Processor-85$20221031_094806_31457_3.1.0] ERROR
> o.a.i.d.m.p.s.FragmentInstanceDispatcherImpl:234 - write locally failed.
> TSStatus: TSStatus(code:412,
> message:org.apache.iotdb.consensus.exception.ConsensusGroupNotExistException:
> The consensus group DataRegion[13] doesn't exist), message:
> org.apache.iotdb.consensus.exception.ConsensusGroupNotExistException: The
> consensus group DataRegion[13] doesn't exist
> 2022-10-31 17:48:06,285
> [pool-25-IoTDB-ClientRPC-Processor-93$20221031_094806_31458_3.1.0] ERROR
> o.a.i.d.m.e.e.RegionWriteExecutor$WritePlanNodeExecutionVisitor:235 -
> {color:#DE350B}*Something wrong happened while calling consensus layer's
> write API.
> org.apache.iotdb.consensus.exception.ConsensusGroupNotExistException: The
> consensus group DataRegion[11] doesn't exist*{color}
> at
> org.apache.iotdb.consensus.multileader.MultiLeaderConsensus.write(MultiLeaderConsensus.java:155)
> at
> org.apache.iotdb.db.mpp.execution.executor.RegionWriteExecutor.fireTriggerAndInsert(RegionWriteExecutor.java:101)
> at
> org.apache.iotdb.db.mpp.execution.executor.RegionWriteExecutor$WritePlanNodeExecutionVisitor.executeDataInsert(RegionWriteExecutor.java:215)
> at
> org.apache.iotdb.db.mpp.execution.executor.RegionWriteExecutor$WritePlanNodeExecutionVisitor.visitInsertTablet(RegionWriteExecutor.java:163)
> at
> org.apache.iotdb.db.mpp.execution.executor.RegionWriteExecutor$WritePlanNodeExecutionVisitor.visitInsertTablet(RegionWriteExecutor.java:117)
> at
> org.apache.iotdb.db.mpp.plan.planner.plan.node.write.InsertTabletNode.accept(InsertTabletNode.java:1085)
> at
> org.apache.iotdb.db.mpp.execution.executor.RegionWriteExecutor.execute(RegionWriteExecutor.java:83)
> at
> org.apache.iotdb.db.mpp.plan.scheduler.FragmentInstanceDispatcherImpl.dispatchLocally(FragmentInstanceDispatcherImpl.java:232)
> at
> org.apache.iotdb.db.mpp.plan.scheduler.FragmentInstanceDispatcherImpl.dispatchOneInstance(FragmentInstanceDispatcherImpl.java:137)
> at
> org.apache.iotdb.db.mpp.plan.scheduler.FragmentInstanceDispatcherImpl.dispatchWriteSync(FragmentInstanceDispatcherImpl.java:119)
> at
> org.apache.iotdb.db.mpp.plan.scheduler.FragmentInstanceDispatcherImpl.dispatch(FragmentInstanceDispatcherImpl.java:90)
> at
> org.apache.iotdb.db.mpp.plan.scheduler.ClusterScheduler.start(ClusterScheduler.java:102)
> at
> org.apache.iotdb.db.mpp.plan.execution.QueryExecution.schedule(QueryExecution.java:283)
> at
> org.apache.iotdb.db.mpp.plan.execution.QueryExecution.start(QueryExecution.java:201)
> at
> org.apache.iotdb.db.mpp.plan.Coordinator.execute(Coordinator.java:146)
> at
> org.apache.iotdb.db.mpp.plan.Coordinator.execute(Coordinator.java:160)
> at
> org.apache.iotdb.db.service.thrift.impl.ClientRPCServiceImpl.insertTablet(ClientRPCServiceImpl.java:1198)
> at
> org.apache.iotdb.service.rpc.thrift.IClientRPCService$Processor$insertTablet.getResult(IClientRPCService.java:4078)
> at
> org.apache.iotdb.service.rpc.thrift.IClientRPCService$Processor$insertTablet.getResult(IClientRPCService.java:4058)
> 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.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> at java.base/java.lang.Thread.run(Thread.java:834)
> {color:#DE350B}**See the
[GitHub] [iotdb-bin-resources] ericpai merged pull request #46: Replace OneCopy_Category.png
ericpai merged PR #46: URL: https://github.com/apache/iotdb-bin-resources/pull/46 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@iotdb.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
