[jira] [Created] (IOTDB-4633) Unequal value after bytes transformation by BytesUtils in Tsfile
Wendi He created IOTDB-4633: --- Summary: Unequal value after bytes transformation by BytesUtils in Tsfile Key: IOTDB-4633 URL: https://issues.apache.org/jira/browse/IOTDB-4633 Project: Apache IoTDB Issue Type: Bug Components: TsFile Reporter: Wendi He Attachments: example-1-1.jpg, example-1.jpg, example-2.jpg In iotdb/tsfile, there seems to be some bugs in BytesUtils. BytesUtils.longToBytes is to transform data to bytes and BytesUtils.bytesToLong is to transform the bytes back to the data. The data after transformation is suppoesed to be equal to the data before transformation. However, in some cases and certain values of data, the value has changed after such transformation. The following examples shows a simple test of this problem. !example-1.jpg!!example-2.jpg! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-4632) [ MetaData ] org.apache.iotdb.db.exception.metadata.MeasurementAlreadyExistException: Path [xx] already exist
刘珍 created IOTDB-4632: - Summary: [ 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 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] [Assigned] (IOTDB-4631) [ remove datanode ] The number of nodes that can be removed is not determined
[
https://issues.apache.org/jira/browse/IOTDB-4631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
刘珍 reassigned IOTDB-4631:
-
Assignee: 刘珍 (was: Jinrui Zhang)
> [ remove datanode ] The number of nodes that can be removed is not determined
> -
>
> Key: IOTDB-4631
> URL: https://issues.apache.org/jira/browse/IOTDB-4631
> Project: Apache IoTDB
> Issue Type: Bug
> Components: mpp-cluster
>Affects Versions: 0.14.0-SNAPSHOT
>Reporter: 刘珍
>Assignee: 刘珍
>Priority: Major
> Attachments: more_dev.conf, screenshot-1.png, screenshot-2.png,
> screenshot-3.png
>
>
> m_1012_d7ed1c1
> 3副本，3C5D，multiLeader
> 可缩容的节点数没有进行判定，缩容3个datanode都成功，导致可用datanode只有2个，小于副本数（3）
> 第2个，第3个缩容操作对应的节点的数据没迁移成功，缩容后查询5万dev（select count(s_0),count(s_599) from
> root.** align by device;），只返回1000条记录
> 缩容3个节点后的集群状态 ：
> !screenshot-2.png!
> !screenshot-1.png!
> 测试环境
> 1. 192.168.10.72/73/74/75/76 5个物理机 48cpu 384GB
> 3C：72/73/74
> 5D: 72/73/74/75/76
> bm在ip1
> 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
> DataNode
> MAX_HEAP_SIZE="256G"
> MAX_DIRECT_MEMORY_SIZE="32G"
> max_connection_for_internal_service=300
> 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
> query_timeout_threshold=3600
> 启动3C5D集群
> 2. bm写入完成
> 配置见附件
> 3. 执行缩容脚本
> 脚本在ip72，缩容3个datanode，在第3个缩容操作应该报错，实际处理了缩容，进程退出（data没迁移）
> liuzhen@fit-72:/data/mpp_test/m_1012_d7ed1c1/datanode$ cat rm.sh
> #!/bin.bash
> ./sbin/remove-datanode.sh 192.168.10.72:6667 > rm_ip72.out
> sleep 2h
> ./sbin/remove-datanode.sh 192.168.10.73:6667 > rm_ip73.out
> ./sbin/remove-datanode.sh 5 > rm_ip74.out
> ip74的log：
> 2022-10-13 00:23:37,887 [pool-22-IoTDB-DataNodeInternalRPC-Processor-67] INFO
> o.a.i.c.conf.CommonConfig:315 -{color:#DE350B}* Change system status to
> Removing! The current Node is being removed from cluster!*{color}
> 另外 ip73的data也没迁移成功，ip73缩容后的data：
> !screenshot-3.png!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (IOTDB-4631) [ remove datanode ] The number of nodes that can be removed is not determined
[
https://issues.apache.org/jira/browse/IOTDB-4631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
刘珍 reassigned IOTDB-4631:
-
Assignee: Gaofei Cao (was: 刘珍)
> [ remove datanode ] The number of nodes that can be removed is not determined
> -
>
> Key: IOTDB-4631
> URL: https://issues.apache.org/jira/browse/IOTDB-4631
> Project: Apache IoTDB
> Issue Type: Bug
> Components: mpp-cluster
>Affects Versions: 0.14.0-SNAPSHOT
>Reporter: 刘珍
>Assignee: Gaofei Cao
>Priority: Major
> Attachments: more_dev.conf, screenshot-1.png, screenshot-2.png,
> screenshot-3.png
>
>
> m_1012_d7ed1c1
> 3副本，3C5D，multiLeader
> 可缩容的节点数没有进行判定，缩容3个datanode都成功，导致可用datanode只有2个，小于副本数（3）
> 第2个，第3个缩容操作对应的节点的数据没迁移成功，缩容后查询5万dev（select count(s_0),count(s_599) from
> root.** align by device;），只返回1000条记录
> 缩容3个节点后的集群状态 ：
> !screenshot-2.png!
> !screenshot-1.png!
> 测试环境
> 1. 192.168.10.72/73/74/75/76 5个物理机 48cpu 384GB
> 3C：72/73/74
> 5D: 72/73/74/75/76
> bm在ip1
> 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
> DataNode
> MAX_HEAP_SIZE="256G"
> MAX_DIRECT_MEMORY_SIZE="32G"
> max_connection_for_internal_service=300
> 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
> query_timeout_threshold=3600
> 启动3C5D集群
> 2. bm写入完成
> 配置见附件
> 3. 执行缩容脚本
> 脚本在ip72，缩容3个datanode，在第3个缩容操作应该报错，实际处理了缩容，进程退出（data没迁移）
> liuzhen@fit-72:/data/mpp_test/m_1012_d7ed1c1/datanode$ cat rm.sh
> #!/bin.bash
> ./sbin/remove-datanode.sh 192.168.10.72:6667 > rm_ip72.out
> sleep 2h
> ./sbin/remove-datanode.sh 192.168.10.73:6667 > rm_ip73.out
> ./sbin/remove-datanode.sh 5 > rm_ip74.out
> ip74的log：
> 2022-10-13 00:23:37,887 [pool-22-IoTDB-DataNodeInternalRPC-Processor-67] INFO
> o.a.i.c.conf.CommonConfig:315 -{color:#DE350B}* Change system status to
> Removing! The current Node is being removed from cluster!*{color}
> 另外 ip73的data也没迁移成功，ip73缩容后的data：
> !screenshot-3.png!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IOTDB-4631) [ remove datanode ] The number of nodes that can be removed is not determined
刘珍 created IOTDB-4631:
-
Summary: [ remove datanode ] The number of nodes that can be
removed is not determined
Key: IOTDB-4631
URL: https://issues.apache.org/jira/browse/IOTDB-4631
Project: Apache IoTDB
Issue Type: Bug
Components: mpp-cluster
Affects Versions: 0.14.0-SNAPSHOT
Reporter: 刘珍
Assignee: Jinrui Zhang
m_1012_d7ed1c1
3副本，3C5D，multiLeader
可缩容的节点数没有进行判定，缩容3个datanode都成功，导致可用datanode只有2个，小于副本数（3）
缩容3个节点后的集群状态
!image-2022-10-13-10-44-02-461.png!
!image-2022-10-13-10-45-01-117.png!
测试环境
1. 192.168.10.72/73/74/75/76 5个物理机 48cpu 384GB
3C：72/73/74
5D: 72/73/74/75/76
bm在ip1
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
DataNode
MAX_HEAP_SIZE="256G"
MAX_DIRECT_MEMORY_SIZE="32G"
max_connection_for_internal_service=300
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
query_timeout_threshold=3600
启动3C5D集群
2. bm写入完成
配置见附件
3. 执行缩容脚本
脚本在ip72，缩容3个datanode，在第3个缩容操作应该报错，实际处理了缩容，进程退出（data没迁移）
liuzhen@fit-72:/data/mpp_test/m_1012_d7ed1c1/datanode$ cat rm.sh
#!/bin.bash
./sbin/remove-datanode.sh 192.168.10.72:6667 > rm_ip72.out
sleep 2h
./sbin/remove-datanode.sh 192.168.10.73:6667 > rm_ip73.out
./sbin/remove-datanode.sh 5 > rm_ip74.out
ip74的log：
2022-10-13 00:23:37,887 [pool-22-IoTDB-DataNodeInternalRPC-Processor-67] INFO
o.a.i.c.conf.CommonConfig:315 -{color:#DE350B}* Change system status to
Removing! The current Node is being removed from cluster!*{color}
另外 ip73的data也没迁移成功，ip73缩容后的data：
!image-2022-10-13-10-40-35-862.png!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IOTDB-4630) Using observer pattern to deal with the leader switchover of confignode and restart of datanode.
Gaofei Cao created IOTDB-4630: - Summary: Using observer pattern to deal with the leader switchover of confignode and restart of datanode. Key: IOTDB-4630 URL: https://issues.apache.org/jira/browse/IOTDB-4630 Project: Apache IoTDB Issue Type: Improvement Reporter: Gaofei Cao Assignee: Yongzao Dan Mainly used for stateful trigger. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Reopened] (IOTDB-4508) [cluster]Got an OOM error when using bm with batch=100
[
https://issues.apache.org/jira/browse/IOTDB-4508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
FengQingxin reopened IOTDB-4508:
该问题在以下commit仍可复现
commit d7ed1c10e52deb720b0c207a19cda3f3ac29e46d
Author: Zhizhou Li <87249...@qq.com>
Date: Wed Oct 12 14:46:06 2022 +0800
Add new sampling algorithm largest triangle to sample UDF (#7462)
!image-2022-10-13-08-49-50-521.png!
> [cluster]Got an OOM error when using bm with batch=100
> --
>
> Key: IOTDB-4508
> URL: https://issues.apache.org/jira/browse/IOTDB-4508
> Project: Apache IoTDB
> Issue Type: Bug
> Components: Core/Cluster
>Affects Versions: 0.14.0-SNAPSHOT
>Reporter: FengQingxin
>Assignee: Jinrui Zhang
>Priority: Major
> Attachments: config.properties, confignode-env.sh, datanode-env.sh,
> image-2022-09-23-09-11-54-951.png, iotdb-confignode.properties,
> iotdb-datanode.properties, logs_Chaos-22.tar.gz, logs_Chaos-23.tar.gz,
> logs_Chaos-24.tar.gz
>
>
> commit 7dc11bae567cb6aac18827b5c746e84538538ac3
> Author: ZhangHongYin <46039728+sprico...@users.noreply.github.com>
> Date: Thu Sep 22 23:36:17 2022 +0800
> IOTDB-4493 Fix null message in TSStatus (#7402)
> 【oom was happened on172.20.70.24、dump files are on 172.20.70.17
> D:\IOTDB-4508】
> Reproduce steps：
> # Setup a cluster with 3C3D({color:#de350b}MultiLeaderConsensus{color})
> # Using 3BMs to insert data(Batch=100)
> # PS: There is no oom errr if we changed benchmark config from 'Batch=100'
> to 'Batch=10'.
> BM - 》 IoTDB Node
> 172.20.70.7 - 》 172.20.70.22
> 172.20.70.8 - 》 172.20.70.23
> 172.20.70.9 - 》 172.20.70.24
>
> 2022-09-23 09:08:23,470 [pool-27-IoTDB-LogDispatcher-DataRegion[10]-2] ERROR
> o.a.i.c.c.t.WrappedThreadPoolExecutor:104 - Exception in thread pool
> org.apache.iotdb.threadpool:type=LogDispatcher-DataRegion[10]
> java.lang.OutOfMemoryError: Java heap space
> at java.util.Arrays.copyOf(Arrays.java:3236)
> at java.io.ByteArrayOutputStream.grow(ByteArrayOutputStream.java:118)
> at
> java.io.ByteArrayOutputStream.ensureCapacity(ByteArrayOutputStream.java:93)
> at java.io.ByteArrayOutputStream.write(ByteArrayOutputStream.java:153)
> at
> org.apache.thrift.transport.TMemoryBuffer.write(TMemoryBuffer.java:88)
> at
> org.apache.thrift.protocol.TBinaryProtocol.writeBinary(TBinaryProtocol.java:235)
> at
> org.apache.iotdb.consensus.multileader.thrift.TLogBatch$TLogBatchStandardScheme.write(TLogBatch.java:524)
> at
> org.apache.iotdb.consensus.multileader.thrift.TLogBatch$TLogBatchStandardScheme.write(TLogBatch.java:465)
> at
> org.apache.iotdb.consensus.multileader.thrift.TLogBatch.write(TLogBatch.java:404)
> at
> org.apache.iotdb.consensus.multileader.thrift.TSyncLogReq$TSyncLogReqStandardScheme.write(TSyncLogReq.java:569)
> at
> org.apache.iotdb.consensus.multileader.thrift.TSyncLogReq$TSyncLogReqStandardScheme.write(TSyncLogReq.java:490)
> at
> org.apache.iotdb.consensus.multileader.thrift.TSyncLogReq.write(TSyncLogReq.java:416)
> at
> org.apache.iotdb.consensus.multileader.thrift.MultiLeaderConsensusIService$syncLog_args$syncLog_argsStandardScheme.write(MultiLeaderConsensusIService.java:563)
> at
> org.apache.iotdb.consensus.multileader.thrift.MultiLeaderConsensusIService$syncLog_args$syncLog_argsStandardScheme.write(MultiLeaderConsensusIService.java:525)
> at
> org.apache.iotdb.consensus.multileader.thrift.MultiLeaderConsensusIService$syncLog_args.write(MultiLeaderConsensusIService.java:476)
> at
> org.apache.iotdb.consensus.multileader.thrift.MultiLeaderConsensusIService$AsyncClient$syncLog_call.write_args(MultiLeaderConsensusIService.java:104)
> at
> org.apache.thrift.async.TAsyncMethodCall.prepareMethodCall(TAsyncMethodCall.java:129)
> at
> org.apache.thrift.async.TAsyncClientManager.call(TAsyncClientManager.java:55)
> at
> org.apache.iotdb.consensus.multileader.thrift.MultiLeaderConsensusIService$AsyncClient.syncLog(MultiLeaderConsensusIService.java:90)
> at
> org.apache.iotdb.consensus.multileader.logdispatcher.LogDispatcher$LogDispatcherThread.sendBatchAsync(LogDispatcher.java:337)
> at
> org.apache.iotdb.consensus.multileader.logdispatcher.LogDispatcher$LogDispatcherThread.run(LogDispatcher.java:214)
> 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)
> 2022-09-23
[jira] [Assigned] (IOTDB-4621) Show regions command meets error when data region is not created completely.
[ https://issues.apache.org/jira/browse/IOTDB-4621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaofei Cao reassigned IOTDB-4621: - Assignee: Gaofei Cao > Show regions command meets error when data region is not created completely. > > > Key: IOTDB-4621 > URL: https://issues.apache.org/jira/browse/IOTDB-4621 > Project: Apache IoTDB > Issue Type: Improvement >Reporter: Gaofei Cao >Assignee: Gaofei Cao >Priority: Minor > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-4629) New standalone architecture, add build-in confignode for datanode.
[ https://issues.apache.org/jira/browse/IOTDB-4629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaofei Cao reassigned IOTDB-4629: - Assignee: 陈哲涵 > New standalone architecture, add build-in confignode for datanode. > -- > > Key: IOTDB-4629 > URL: https://issues.apache.org/jira/browse/IOTDB-4629 > Project: Apache IoTDB > Issue Type: New Feature >Reporter: Gaofei Cao >Assignee: 陈哲涵 >Priority: Major > > see this doc > [https://apache-iotdb.feishu.cn/docx/doxcnvRKE4InwXB4gFvU8RLUW6c] for more > details -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-4629) New standalone architecture, add build-in confignode for datanode.
Gaofei Cao created IOTDB-4629: - Summary: New standalone architecture, add build-in confignode for datanode. Key: IOTDB-4629 URL: https://issues.apache.org/jira/browse/IOTDB-4629 Project: Apache IoTDB Issue Type: New Feature Reporter: Gaofei Cao see this doc [https://apache-iotdb.feishu.cn/docx/doxcnvRKE4InwXB4gFvU8RLUW6c] for more details -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-4628) [sync] Do not store pipe infomation after drop
yanze chen created IOTDB-4628: - Summary: [sync] Do not store pipe infomation after drop Key: IOTDB-4628 URL: https://issues.apache.org/jira/browse/IOTDB-4628 Project: Apache IoTDB Issue Type: Improvement Reporter: yanze chen Assignee: yanze chen In old version, pipe infomation will be stored even if pipe has been dropped. There are two advantages to not storing pipe infomation after drop can. # Support rollback logic in procedure better. If failed to create pipe, drop directlt. # Other modules(e.g.Trigger) do the same thing. Doing so can keep the semantics consistent in IoTDB. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-4627) Transfer stateful triggers when DataNode Status is Unknown
[ https://issues.apache.org/jira/browse/IOTDB-4627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] 李伟豪 reassigned IOTDB-4627: -- Assignee: 李伟豪 > Transfer stateful triggers when DataNode Status is Unknown > --- > > Key: IOTDB-4627 > URL: https://issues.apache.org/jira/browse/IOTDB-4627 > Project: Apache IoTDB > Issue Type: Sub-task >Reporter: 李伟豪 >Assignee: 李伟豪 >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-4627) Transfer stateful triggers when DataNode Status is Unknown
李伟豪 created IOTDB-4627: -- Summary: Transfer stateful triggers when DataNode Status is Unknown Key: IOTDB-4627 URL: https://issues.apache.org/jira/browse/IOTDB-4627 Project: Apache IoTDB Issue Type: Sub-task Reporter: 李伟豪 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-4623) [ remove ConfigNode ] Surviving confignodes after removing other confignodes need to be updated confignode_list
[
https://issues.apache.org/jira/browse/IOTDB-4623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
陈哲涵 reassigned IOTDB-4623:
--
Assignee: 陈哲涵 (was: Gaofei Cao)
> [ remove ConfigNode ] Surviving confignodes after removing other confignodes
> need to be updated confignode_list
> ---
>
> Key: IOTDB-4623
> URL: https://issues.apache.org/jira/browse/IOTDB-4623
> Project: Apache IoTDB
> Issue Type: Bug
> Components: mpp-cluster
>Affects Versions: 0.14.0-SNAPSHOT
>Reporter: 刘珍
>Assignee: 陈哲涵
>Priority: Major
> Attachments: config.properties
>
>
> master_1010_9917053
> 3 ConfigNode , Successfully removed 1 confignode (follower ,ip:port ，ip66) ,
> remove another follower confignode （NodeID ，ip68），{color:#DE350B}*Error
> reported, but removed successfully *{color}：
> 2022-10-12 10:40:21,083 [main] WARN
> o.a.i.c.c.s.c.SyncConfigNodeClientPool:95 - REMOVE_CONFIG_NODE
> {color:#DE350B}*failed on ConfigNode TEndPoint(ip:192.168.10.66,
> port:22277)*{color}, because Borrow client from pool for node
> TEndPoint(ip:192.168.10.66, port:22277) failed., retrying 5...
> 2022-10-12 10:40:24,284 [main] ERROR
> o.a.i.c.c.s.c.SyncConfigNodeClientPool:104 - REMOVE_CONFIG_NODE failed on
> ConfigNode TEndPoint(ip:192.168.10.66, port:22277)
> java.io.IOException: Borrow client from pool for node
> TEndPoint(ip:192.168.10.66, port:22277) failed.
> at
> org.apache.iotdb.commons.client.ClientManager.borrowClient(ClientManager.java:61)
> at
> org.apache.iotdb.confignode.client.sync.confignode.SyncConfigNodeClientPool.sendSyncRequestToConfigNodeWithRetry(SyncConfigNodeClientPool.java:72)
> at
> org.apache.iotdb.confignode.conf.ConfigNodeRemoveCheck.removeConfigNode(ConfigNodeRemoveCheck.java:98)
> at
> org.apache.iotdb.confignode.service.ConfigNodeCommandLine.doRemoveNode(ConfigNodeCommandLine.java:112)
> at
> org.apache.iotdb.confignode.service.ConfigNodeCommandLine.run(ConfigNodeCommandLine.java:83)
> at
> org.apache.iotdb.commons.ServerCommandLine.doMain(ServerCommandLine.java:58)
> at
> org.apache.iotdb.confignode.service.ConfigNode.main(ConfigNode.java:71)
> 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
> net.sf.cglib.proxy.Enhancer.createUsingReflection(Enhancer.java:639)
> at net.sf.cglib.proxy.Enhancer.firstInstance(Enhancer.java:538)
> at
> net.sf.cglib.core.AbstractClassGenerator.create(AbstractClassGenerator.java:231)
> at net.sf.cglib.proxy.Enhancer.createHelper(Enhancer.java:377)
> at net.sf.cglib.proxy.Enhancer.create(Enhancer.java:304)
> at
> org.apache.iotdb.commons.client.sync.SyncThriftClientWithErrorHandler.newErrorHandler(SyncThriftClientWithErrorHandler.java:48)
> at
> org.apache.iotdb.commons.client.sync.SyncConfigNodeIServiceClient$Factory.makeObject(SyncConfigNodeIServiceClient.java:115)
> at
> org.apache.iotdb.commons.client.sync.SyncConfigNodeIServiceClient$Factory.makeObject(SyncConfigNodeIServiceClient.java:94)
> at
> org.apache.commons.pool2.impl.GenericKeyedObjectPool.create(GenericKeyedObjectPool.java:780)
> at
> org.apache.commons.pool2.impl.GenericKeyedObjectPool.borrowObject(GenericKeyedObjectPool.java:439)
> at
> org.apache.commons.pool2.impl.GenericKeyedObjectPool.borrowObject(GenericKeyedObjectPool.java:350)
> at
> org.apache.iotdb.commons.client.ClientManager.borrowClient(ClientManager.java:50)
> ... 6 common frames omitted
> Caused by: org.apache.thrift.transport.TTransportException:
> java.net.ConnectException: Connection refused (Connection refused)
> at org.apache.thrift.transport.TSocket.open(TSocket.java:243)
> at
> org.apache.iotdb.rpc.TElasticFramedTransport.open(TElasticFramedTransport.java:91)
> at
> org.apache.iotdb.commons.client.sync.SyncConfigNodeIServiceClient.(SyncConfigNodeIServiceClient.java:62)
> at
> org.apache.iotdb.commons.client.sync.SyncConfigNodeIServiceClient$$EnhancerByCGLIB$$763d90ac.()
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at
[jira] [Assigned] (IOTDB-4626) Implement SQL `getSlots`, `getTimeSlotList`, `getSeriesSlotList` for MPP mode
[ https://issues.apache.org/jira/browse/IOTDB-4626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaofei Cao reassigned IOTDB-4626: - Assignee: 陈哲涵 (was: Gaofei Cao) > Implement SQL `getSlots`, `getTimeSlotList`, `getSeriesSlotList` for MPP mode > - > > Key: IOTDB-4626 > URL: https://issues.apache.org/jira/browse/IOTDB-4626 > Project: Apache IoTDB > Issue Type: New Feature >Reporter: Gaofei Cao >Assignee: 陈哲涵 >Priority: Major > > see the doc [https://apache-iotdb.feishu.cn/docx/doxcnA4xpA6vrmKssH2GgbeHFhh] > for more details -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-4626) Implement SQL `getSlots`, `getTimeSlotList`, `getSeriesSlotList` for MPP mode
Gaofei Cao created IOTDB-4626: - Summary: Implement SQL `getSlots`, `getTimeSlotList`, `getSeriesSlotList` for MPP mode Key: IOTDB-4626 URL: https://issues.apache.org/jira/browse/IOTDB-4626 Project: Apache IoTDB Issue Type: New Feature Reporter: Gaofei Cao see the doc [https://apache-iotdb.feishu.cn/docx/doxcnA4xpA6vrmKssH2GgbeHFhh] for more details -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-4626) Implement SQL `getSlots`, `getTimeSlotList`, `getSeriesSlotList` for MPP mode
[ https://issues.apache.org/jira/browse/IOTDB-4626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaofei Cao reassigned IOTDB-4626: - Assignee: Gaofei Cao > Implement SQL `getSlots`, `getTimeSlotList`, `getSeriesSlotList` for MPP mode > - > > Key: IOTDB-4626 > URL: https://issues.apache.org/jira/browse/IOTDB-4626 > Project: Apache IoTDB > Issue Type: New Feature >Reporter: Gaofei Cao >Assignee: Gaofei Cao >Priority: Major > > see the doc [https://apache-iotdb.feishu.cn/docx/doxcnA4xpA6vrmKssH2GgbeHFhh] > for more details -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-4625) Support updatePeer in RatisConsensus
伊丹翔 created IOTDB-4625: -- Summary: Support updatePeer in RatisConsensus Key: IOTDB-4625 URL: https://issues.apache.org/jira/browse/IOTDB-4625 Project: Apache IoTDB Issue Type: Task Reporter: 伊丹翔 Assignee: Song Ziyang -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-4624) Support updatePeer in MultiLeaderConsensus
伊丹翔 created IOTDB-4624: -- Summary: Support updatePeer in MultiLeaderConsensus Key: IOTDB-4624 URL: https://issues.apache.org/jira/browse/IOTDB-4624 Project: Apache IoTDB Issue Type: Task Reporter: 伊丹翔 Assignee: 张洪胤 -- This message was sent by Atlassian Jira (v8.20.10#820010)
