[jira] [Assigned] (IOTDB-5515) Support group by series in aggregation query.
[ https://issues.apache.org/jira/browse/IOTDB-5515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yang caiyin reassigned IOTDB-5515: -- Assignee: yang caiyin > Support group by series in aggregation query. > - > > Key: IOTDB-5515 > URL: https://issues.apache.org/jira/browse/IOTDB-5515 > Project: Apache IoTDB > Issue Type: New Feature >Reporter: yang caiyin >Assignee: yang caiyin >Priority: Major > > user guide: > https://apache-iotdb.feishu.cn/docx/NgCXdVmPSoTdZsx3TzNcF0J9n6d > deign doc: > https://apache-iotdb.feishu.cn/docx/N1Mmd3HWyoDjohxCO9ic6JO2nXc > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5515) Support group by series in aggregation query.
yang caiyin created IOTDB-5515: -- Summary: Support group by series in aggregation query. Key: IOTDB-5515 URL: https://issues.apache.org/jira/browse/IOTDB-5515 Project: Apache IoTDB Issue Type: New Feature Reporter: yang caiyin user guide: https://apache-iotdb.feishu.cn/docx/NgCXdVmPSoTdZsx3TzNcF0J9n6d deign doc: https://apache-iotdb.feishu.cn/docx/N1Mmd3HWyoDjohxCO9ic6JO2nXc -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Reopened] (IOTDB-5287) [ConfigNode][3rep3C3D 1DataNode-ReadOnly] Create DataPartition failed
[
https://issues.apache.org/jira/browse/IOTDB-5287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
刘珍 reopened IOTDB-5287:
---
master 0210 87574002be7e9c774c136dd4ab4f949a9c7ee2ec
> [ConfigNode][3rep3C3D 1DataNode-ReadOnly] Create DataPartition failed
> -
>
> Key: IOTDB-5287
> URL: https://issues.apache.org/jira/browse/IOTDB-5287
> Project: Apache IoTDB
> Issue Type: Bug
> Components: mpp-cluster
>Affects Versions: master branch, 1.0.0
>Reporter: 刘珍
>Assignee: 陈哲涵
>Priority: Major
> Labels: pull-request-available
> Attachments: iotdb_5287.conf
>
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> master_1226_30335b3
> 问题描述：
> 3副本3C3D集群，BM写入数据过程中，1节点readonly（手动set），
> 当写入的数据触发创建新的时间分区时，ConfigNode报错（写入的数据若在已有时间分区范围，可继续写入，没有报错）
> 2022-12-26 19:35:59,489 [pool-12-IoTDB-ConfigNodeRPC-Processor-37] ERROR
> o.a.i.c.m.p.PartitionManager:307 - Create DataPartition failed because:
> org.apache.iotdb.confignode.exception.NoAvailableRegionGroupException:
> {color:#DE350B}*There are no available DataRegionGroup RegionGroups
> currently, please use "show cluster"
> or "show regions" to check the cluster status*{color}
> at
> org.apache.iotdb.confignode.manager.partition.PartitionManager.getSortedRegionGroupSlotsCounter(PartitionManager.java:598)
> at
> org.apache.iotdb.confignode.manager.load.balancer.partition.GreedyPartitionAllocator.allocateDataPartition(GreedyPartitionAllocator.java:101)
> at
> org.apache.iotdb.confignode.manager.load.balancer.PartitionBalancer.allocateDataPartition(PartitionBalancer.java:66)
> at
> org.apache.iotdb.confignode.manager.load.LoadManager.allocateDataPartition(LoadManager.java:139)
> at
> org.apache.iotdb.confignode.manager.partition.PartitionManager.getOrCreateDataPartition(PartitionManager.java:305)
> at
> org.apache.iotdb.confignode.manager.ConfigManager.getOrCreateDataPartition(ConfigManager.java:676)
> at
> org.apache.iotdb.confignode.service.thrift.ConfigNodeRPCServiceProcessor.getOrCreateDataPartitionTable(ConfigNodeRPCServiceProcessor.java:389)
> at
> org.apache.iotdb.confignode.rpc.thrift.IConfigNodeRPCService$Processor$getOrCreateDataPartitionTable.getResult(IConfigNodeRPCService.java:5916)
> at
> org.apache.iotdb.confignode.rpc.thrift.IConfigNodeRPCService$Processor$getOrCreateDataPartitionTable.getResult(IConfigNodeRPCService.java:5896)
> 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)
> 测试环境
> 1. 192.168.10.72/73/74 48CPU384GB
> ConfigNode配置
> MAX_HEAP_SIZE="8G"
> DataNode配置
> MAX_HEAP_SIZE="192G"
> MAX_DIRECT_MEMORY_SIZE="32G"
> Common配置
> schema_replication_factor=3
> data_replication_factor=3
> time_partition_interval=360
> query_timeout_threshold=3600
> 2. 运行BM （附件中的配置）
> 刚开始写入数据的时候，就手动设置（IP72）datanode为readonly
> cli -e "set system to readonly on local"
> 3. 产生新的时间分区时，confignode报错
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Reopened] (IOTDB-4936) 1 datanode READONLY, create schema：“ConfigNode failed to extend Region because there are not enough DataNodes”
[
https://issues.apache.org/jira/browse/IOTDB-4936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
刘珍 reopened IOTDB-4936:
---
master 0210 87574002be7e9c774c136dd4ab4f949a9c7ee2ec
> 1 datanode READONLY, create schema：“ConfigNode failed to extend Region
> because there are not enough DataNodes”
> ---
>
> Key: IOTDB-4936
> URL: https://issues.apache.org/jira/browse/IOTDB-4936
> Project: Apache IoTDB
> Issue Type: Bug
> Components: mpp-cluster
>Affects Versions: 0.14.0-SNAPSHOT, 1.0.0
>Reporter: 刘珍
>Assignee: 陈哲涵
>Priority: Major
> Fix For: 0.14.0-SNAPSHOT
>
> Attachments: config-leader_logs.tar.gz, iotdb_4936.conf
>
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> rel/1.0 2022-12-07_67bbd2e
> 3副本3C3D ，其中1个datanode 设置为READONLY后，创建元数据，confignode报错，创建元数据失败。
> 1. 启动3副本3C3D 集群
> 2. benchmark 创建元数据配置见附件
> bm运行起来后，立即执行./sbin/start-cli.sh -h 172.16.2.6 -e "SET SYSTEM TO READONLY ON
> LOCAL"
> 3.confignode 报错
> 2022-12-08 11:41:48,223 [pool-12-IoTDB-ConfigNodeRPC-Processor-11] ERROR
> o.a.i.c.m.p.PartitionManager:365 - ConfigNode failed to extend Region because
> there are not enough DataNodes
> 2022-12-08 11:41:48,224 [pool-12-IoTDB-ConfigNodeRPC-Processor-12] ERROR
> o.a.i.c.m.p.PartitionManager:365 - ConfigNode failed to extend Region because
> there are not enough DataNodes {color:#FF}【TODO：Add more description
> about the error reason】{color}
> 测试环境
> 1. 启动3副本3C3D 集群
> config,schema ,data 分别是ratis，ratis ，IoT协议。
> 2. ConfigNode leader 的日志见附件
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IOTDB-5514) Fix MemoryPool race condition on clearMemoryReservationMap()
Eric Pai created IOTDB-5514: --- Summary: Fix MemoryPool race condition on clearMemoryReservationMap() Key: IOTDB-5514 URL: https://issues.apache.org/jira/browse/IOTDB-5514 Project: Apache IoTDB Issue Type: Bug Components: Core/Engine Reporter: Eric Pai Assignee: Eric Pai Fix For: master branch Attachments: image-2023-02-10-15-04-24-660.png The method clearMemoryReservationMap() is not surrounded by synchronized block, which will cause !image-2023-02-10-15-04-24-660.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-5472) [Atmos]The number of tsfiles went up between db6f17e 【02/01】and 5602d0e【02/05】
[ https://issues.apache.org/jira/browse/IOTDB-5472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jialin Qiao reassigned IOTDB-5472: -- Assignee: (was: Haonan Hou) > [Atmos]The number of tsfiles went up between db6f17e 【02/01】and 5602d0e【02/05】 > -- > > Key: IOTDB-5472 > URL: https://issues.apache.org/jira/browse/IOTDB-5472 > Project: Apache IoTDB > Issue Type: Improvement > Components: Core/Engine >Reporter: Qingxin Feng >Priority: Minor > Attachments: image-2023-02-06-09-18-27-596.png, > image-2023-02-06-09-22-50-304.png, image-2023-02-08-08-41-55-425.png, > image-2023-02-10-08-55-18-990.png > > > The number of tsfiles went up between db6f17e 【02/01】and 5602d0e【02/05】 > Please refer to below picture. > > !image-2023-02-06-09-22-50-304.png|width=661,height=380! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-5472) [Atmos]The number of tsfiles went up between db6f17e 【02/01】and 5602d0e【02/05】
[ https://issues.apache.org/jira/browse/IOTDB-5472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jialin Qiao reassigned IOTDB-5472: -- Assignee: Haonan Hou (was: Jialin Qiao) > [Atmos]The number of tsfiles went up between db6f17e 【02/01】and 5602d0e【02/05】 > -- > > Key: IOTDB-5472 > URL: https://issues.apache.org/jira/browse/IOTDB-5472 > Project: Apache IoTDB > Issue Type: Improvement > Components: Core/Engine >Reporter: Qingxin Feng >Assignee: Haonan Hou >Priority: Minor > Attachments: image-2023-02-06-09-18-27-596.png, > image-2023-02-06-09-22-50-304.png, image-2023-02-08-08-41-55-425.png, > image-2023-02-10-08-55-18-990.png > > > The number of tsfiles went up between db6f17e 【02/01】and 5602d0e【02/05】 > Please refer to below picture. > > !image-2023-02-06-09-22-50-304.png|width=661,height=380! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [iotdb-client-go] iotopo opened a new issue, #74: 连续执行 2 次查询后报错
iotopo opened a new issue, #74: URL: https://github.com/apache/iotdb-client-go/issues/74  如图所示 -- 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.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (IOTDB-5513) Duplicate LastQueryNode due to change of partition slot algorithm
[ https://issues.apache.org/jira/browse/IOTDB-5513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17686859#comment-17686859 ] liaolanyu commented on IOTDB-5513: -- We expect only one LastQueryNode in each FI, LastQuery-9 is not expected. > Duplicate LastQueryNode due to change of partition slot algorithm > - > > Key: IOTDB-5513 > URL: https://issues.apache.org/jira/browse/IOTDB-5513 > Project: Apache IoTDB > Issue Type: Bug >Reporter: liaolanyu >Assignee: liaolanyu >Priority: Major > Attachments: image-2023-02-10-11-39-23-284.png > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IOTDB-5513) Duplicate LastQueryNode due to change of partition slot algorithm
[ https://issues.apache.org/jira/browse/IOTDB-5513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17686858#comment-17686858 ] liaolanyu commented on IOTDB-5513: -- !image-2023-02-10-11-39-23-284.png! > Duplicate LastQueryNode due to change of partition slot algorithm > - > > Key: IOTDB-5513 > URL: https://issues.apache.org/jira/browse/IOTDB-5513 > Project: Apache IoTDB > Issue Type: Bug >Reporter: liaolanyu >Assignee: liaolanyu >Priority: Major > Attachments: image-2023-02-10-11-39-23-284.png > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5513) Duplicate LastQueryNode due to change of partition slot algorithm
liaolanyu created IOTDB-5513: Summary: Duplicate LastQueryNode due to change of partition slot algorithm Key: IOTDB-5513 URL: https://issues.apache.org/jira/browse/IOTDB-5513 Project: Apache IoTDB Issue Type: Bug Reporter: liaolanyu Assignee: liaolanyu -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Reopened] (IOTDB-5504) IllegalArgumentException occurs when scheduling compaction
[ https://issues.apache.org/jira/browse/IOTDB-5504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Liuxuxin reopened IOTDB-5504: - > IllegalArgumentException occurs when scheduling compaction > -- > > Key: IOTDB-5504 > URL: https://issues.apache.org/jira/browse/IOTDB-5504 > Project: Apache IoTDB > Issue Type: Bug >Affects Versions: master branch, 0.13.4, 1.0.1 >Reporter: Liuxuxin >Assignee: Liuxuxin >Priority: Major > Labels: pull-request-available > Attachments: image-2023-02-09-09-32-01-814.png > > > !image-2023-02-09-09-32-01-814.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IOTDB-5507) [start] It's not a good idea to wait 20s to restart a datanode
[ https://issues.apache.org/jira/browse/IOTDB-5507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17686833#comment-17686833 ] changxue commented on IOTDB-5507: - restart: stop-datanode.sh start-datanode.sh > [start] It's not a good idea to wait 20s to restart a datanode > --- > > Key: IOTDB-5507 > URL: https://issues.apache.org/jira/browse/IOTDB-5507 > Project: Apache IoTDB > Issue Type: Improvement >Reporter: changxue >Assignee: Xinyu Tan >Priority: Major > Attachments: image-2023-02-09-11-43-44-065.png > > > [start] It's not a good idea to wait 20s to restart a datanode > !image-2023-02-09-11-43-44-065.png|width=800! > suppose: > I change some configurations and need to restart to make sense, then I want > to restart immediately, rather than waiting 20s > It's not a good designation. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IOTDB-5472) [Atmos]The number of tsfiles went up between db6f17e 【02/01】and 5602d0e【02/05】
[ https://issues.apache.org/jira/browse/IOTDB-5472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17686820#comment-17686820 ] Qingxin Feng commented on IOTDB-5472: - https://github.com/apache/iotdb/commit/a0c7c0bbe74594678be0b81f4b9a4ce69048d855 !image-2023-02-10-08-55-18-990.png|width=386,height=269! > [Atmos]The number of tsfiles went up between db6f17e 【02/01】and 5602d0e【02/05】 > -- > > Key: IOTDB-5472 > URL: https://issues.apache.org/jira/browse/IOTDB-5472 > Project: Apache IoTDB > Issue Type: Improvement > Components: Core/Engine >Reporter: Qingxin Feng >Assignee: Jialin Qiao >Priority: Minor > Attachments: image-2023-02-06-09-18-27-596.png, > image-2023-02-06-09-22-50-304.png, image-2023-02-08-08-41-55-425.png, > image-2023-02-10-08-55-18-990.png > > > The number of tsfiles went up between db6f17e 【02/01】and 5602d0e【02/05】 > Please refer to below picture. > > !image-2023-02-06-09-22-50-304.png|width=661,height=380! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5512) [ IoTConsensus Resend log ] The unsequence tsfile is generated after the cluster is restarted (
刘珍 created IOTDB-5512: - Summary: [ IoTConsensus Resend log ] The unsequence tsfile is generated after the cluster is restarted ( Key: IOTDB-5512 URL: https://issues.apache.org/jira/browse/IOTDB-5512 Project: Apache IoTDB Issue Type: Improvement Components: mpp-cluster Reporter: 刘珍 Assignee: Xinyu Tan Attachments: image-2023-02-09-15-45-05-253.png, image-2023-02-09-15-52-51-085.png, insert_no_overflow.config.properties 测试版本：rc/1.0.1 20230202 63b16f2 问题描述： 3副本3节点集群，benchmark写入顺序数据，重启前检查data 为全顺序，重启集群后，会生成部分乱序tsfile。 重启集群前查看所有dataregion的log同步情况，已同步完成： !image-2023-02-09-15-45-05-253.png! consensus 文件记录的已同步的log index是10 !image-2023-02-09-15-52-51-085.png! 重启集群后，这90条log会重发，导致有乱序tsfile生成，可以优化一下，解决这个问题。 测试流程： 1. 私有云3期 1ConfigNode 172.20.70.5 3DataNode 172.20.70.2/4/14 benchmark 在172.20.70.13 （配置见附件） 集群配置参数 ConfigNode MAX_HEAP_SIZE="20G" MAX_DIRECT_MEMORY_SIZE="6G" DataNode MAX_HEAP_SIZE="20G" MAX_DIRECT_MEMORY_SIZE="6G" dn_max_connection_for_internal_service=300 common文件 schema_replication_factor=3 data_replication_factor=3 enable_seq_space_compaction=false enable_unseq_space_compaction=false enable_cross_space_compaction=false config_node_consensus_protocol_class=org.apache.iotdb.consensus.ratis.RatisConsensus schema_region_consensus_protocol_class=org.apache.iotdb.consensus.ratis.RatisConsensus data_region_consensus_protocol_class=org.apache.iotdb.consensus.iot.IoTConsensus 2. 运行benchmark 3. 写入完成，检查data ，无乱序tsfile，log同步完成，重启集群。 预期结果，重启后，无乱序tsfile。 -- This message was sent by Atlassian Jira (v8.20.10#820010)
