[jira] [Assigned] (IOTDB-4072) Updated the ConfigNode Dashboard to add a display of node online and offline information and the distribution of leaders
[ https://issues.apache.org/jira/browse/IOTDB-4072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sixing Wu reassigned IOTDB-4072: Assignee: Sixing Wu > Updated the ConfigNode Dashboard to add a display of node online and offline > information and the distribution of leaders > > > Key: IOTDB-4072 > URL: https://issues.apache.org/jira/browse/IOTDB-4072 > Project: Apache IoTDB > Issue Type: Improvement >Reporter: Sixing Wu >Assignee: Sixing Wu >Priority: Minor > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-4072) Updated the ConfigNode Dashboard to add a display of node online and offline information and the distribution of leaders
Sixing Wu created IOTDB-4072: Summary: Updated the ConfigNode Dashboard to add a display of node online and offline information and the distribution of leaders Key: IOTDB-4072 URL: https://issues.apache.org/jira/browse/IOTDB-4072 Project: Apache IoTDB Issue Type: Improvement Reporter: Sixing Wu -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-4071) Msg: 303: Timeseries under path [root.sg1.d1] is not aligned , please set InsertPlan.isAligned() = false
zhenqqiang created IOTDB-4071: - Summary: Msg: 303: Timeseries under path [root.sg1.d1] is not aligned , please set InsertPlan.isAligned() = false Key: IOTDB-4071 URL: https://issues.apache.org/jira/browse/IOTDB-4071 Project: Apache IoTDB Issue Type: Bug Affects Versions: 0.13.2 Reporter: zhenqqiang Assignee: 刘俊男 Fix For: 0.13.2 Attachments: image-2022-08-09-10-05-54-623.png, image-2022-08-09-10-06-33-192.png !image-2022-08-09-10-05-54-623.png! !image-2022-08-09-10-06-33-192.png! 请跑一下测试用例了来，把测试用例的错误解决了来，做好自测。 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-3867) Change the write lock of each DataRegion to device level
[ https://issues.apache.org/jira/browse/IOTDB-3867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] fuliwen reassigned IOTDB-3867: -- Assignee: fuliwen > Change the write lock of each DataRegion to device level > > > Key: IOTDB-3867 > URL: https://issues.apache.org/jira/browse/IOTDB-3867 > Project: Apache IoTDB > Issue Type: Improvement >Reporter: Jialin Qiao >Assignee: fuliwen >Priority: Major > > Currently, we have a write lock in each DataRegion, which limit the write > throughput in the standalone version. We'd better change this lock to a lower > level. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-3924) [rewriteFileTool][0.13] rewrite-file-tool.sh does not support change ports
[ https://issues.apache.org/jira/browse/IOTDB-3924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haonan Hou reassigned IOTDB-3924: - Assignee: Quan Siyi > [rewriteFileTool][0.13] rewrite-file-tool.sh does not support change ports > -- > > Key: IOTDB-3924 > URL: https://issues.apache.org/jira/browse/IOTDB-3924 > Project: Apache IoTDB > Issue Type: Improvement >Reporter: ZhangZhengming >Assignee: Quan Siyi >Priority: Major > Fix For: 0.13.0-SNAPSHOT > > Attachments: image-2022-07-21-20-30-51-978.png > > > !image-2022-07-21-20-30-51-978.png|width=722,height=102! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IOTDB-4069) Design the details for Memory control of query processing
[ https://issues.apache.org/jira/browse/IOTDB-4069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17577060#comment-17577060 ] Yuan Tian commented on IOTDB-4069: -- https://apache-iotdb.feishu.cn/docx/doxcn4G2OIhmrEc2yoPxmGC67cc > Design the details for Memory control of query processing > - > > Key: IOTDB-4069 > URL: https://issues.apache.org/jira/browse/IOTDB-4069 > Project: Apache IoTDB > Issue Type: Improvement >Reporter: Yuan Tian >Assignee: Yuan Tian >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-4070) Implemation of partial operators for memory control
Yuan Tian created IOTDB-4070: Summary: Implemation of partial operators for memory control Key: IOTDB-4070 URL: https://issues.apache.org/jira/browse/IOTDB-4070 Project: Apache IoTDB Issue Type: Improvement Reporter: Yuan Tian Assignee: Yuan Tian * FillOperator (org.apache.iotdb.db.mpp.execution.operator.process) * LastQueryCollectOperator (org.apache.iotdb.db.mpp.execution.operator.process.last) * LastQueryMergeOperator (org.apache.iotdb.db.mpp.execution.operator.process.last) * LastQueryOperator (org.apache.iotdb.db.mpp.execution.operator.process.last) * LastQuerySortOperator (org.apache.iotdb.db.mpp.execution.operator.process.last) * LimitOperator (org.apache.iotdb.db.mpp.execution.operator.process) * OffsetOperator (org.apache.iotdb.db.mpp.execution.operator.process) * RowBasedTimeJoinOperator (org.apache.iotdb.db.mpp.execution.operator.process.join) * SortOperator (org.apache.iotdb.db.mpp.execution.operator.process) * TimeJoinOperator (org.apache.iotdb.db.mpp.execution.operator.process.join) * UpdateLastCacheOperator (org.apache.iotdb.db.mpp.execution.operator.process.last) * LinearFillOperator (org.apache.iotdb.db.mpp.execution.operator.process) ** 需要单独讨论，是否需要加上限制，最多往后探多少个TsBlock，如果还未遇到非空的，则报错 * AlignedSeriesScanOperator (org.apache.iotdb.db.mpp.execution.operator.source) * SeriesScanOperator (org.apache.iotdb.db.mpp.execution.operator.source) * ExchangeOperator (org.apache.iotdb.db.mpp.execution.operator.source) * LastCacheScanOperator (org.apache.iotdb.db.mpp.execution.operator.source) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-4069) Design the details for Memory control of query processing
Yuan Tian created IOTDB-4069: Summary: Design the details for Memory control of query processing Key: IOTDB-4069 URL: https://issues.apache.org/jira/browse/IOTDB-4069 Project: Apache IoTDB Issue Type: Improvement Reporter: Yuan Tian Assignee: Yuan Tian -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-4068) Control the total memory in each DataNode for query processing
[ https://issues.apache.org/jira/browse/IOTDB-4068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yuan Tian reassigned IOTDB-4068: Assignee: Yuan Tian > Control the total memory in each DataNode for query processing > -- > > Key: IOTDB-4068 > URL: https://issues.apache.org/jira/browse/IOTDB-4068 > Project: Apache IoTDB > Issue Type: Epic >Reporter: Yuan Tian >Assignee: Yuan Tian >Priority: Major > Labels: 2022-8-cluster > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-4068) Control
Yuan Tian created IOTDB-4068: Summary: Control Key: IOTDB-4068 URL: https://issues.apache.org/jira/browse/IOTDB-4068 Project: Apache IoTDB Issue Type: Epic Reporter: Yuan Tian -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-3808) Support count(time) to get the total number in aligned timeseries
[ https://issues.apache.org/jira/browse/IOTDB-3808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yuan Tian reassigned IOTDB-3808: Assignee: 李伟豪 > Support count(time) to get the total number in aligned timeseries > -- > > Key: IOTDB-3808 > URL: https://issues.apache.org/jira/browse/IOTDB-3808 > Project: Apache IoTDB > Issue Type: New Feature > Components: Core/Cluster >Affects Versions: 0.13.1 >Reporter: 刘俊男 >Assignee: 李伟豪 >Priority: Major > Attachments: image-2022-07-12-18-47-19-176.png > > > * !image-2022-07-12-18-47-19-176.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-4062) [ raft log & MetaData ] raft log recovery should not redo MeasurementAlreadyExist operation
[ https://issues.apache.org/jira/browse/IOTDB-4062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jialin Qiao reassigned IOTDB-4062: -- Assignee: Yukun Zhou (was: Jialin Qiao) > [ raft log & MetaData ] raft log recovery should not redo > MeasurementAlreadyExist operation > > > Key: IOTDB-4062 > URL: https://issues.apache.org/jira/browse/IOTDB-4062 > Project: Apache IoTDB > Issue Type: Improvement > Components: mpp-cluster >Reporter: 刘珍 >Assignee: Yukun Zhou >Priority: Major > Attachments: config_raft_log_recovery.properties > > > raft log恢复，会重做所有MetaData的写操作，对于失败的元数据写操作比如序列已存在： > [192.168.10.62_50010@group-0002-StateMachineUpdater] ERROR > o.a.i.d.m.v.SchemaExecutionVisitor:108 - IoTDB: MetaData error: > org.apache.iotdb.db.exception.metadata.MeasurementAlreadyExistException: Path > [root.bm68_dn62.g_0.d_0.s_1] already exist > 不需要重做。 > 完整的异常： > 2022-08-08 17:46:29,045 > [192.168.10.62_50010@group-0002-StateMachineUpdater] ERROR > o.a.i.d.m.v.SchemaExecutionVisitor:108 - IoTDB: MetaData error: > org.apache.iotdb.db.exception.metadata.MeasurementAlreadyExistException: Path > [root.bm68_dn62.g_0.d_0.s_2] already exist > at > org.apache.iotdb.db.metadata.mtree.MTreeBelowSGMemoryImpl.createTimeseries(MTreeBelowSGMemoryImpl.java:213) > at > org.apache.iotdb.db.metadata.schemaregion.SchemaRegionMemoryImpl.createTimeseries(SchemaRegionMemoryImpl.java:589) > at > org.apache.iotdb.db.metadata.visitor.SchemaExecutionVisitor.visitCreateMultiTimeSeries(SchemaExecutionVisitor.java:105) > at > org.apache.iotdb.db.metadata.visitor.SchemaExecutionVisitor.visitCreateMultiTimeSeries(SchemaExecutionVisitor.java:62) > 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:68) > at > org.apache.iotdb.consensus.ratis.ApplicationStateMachineProxy.applyTransaction(ApplicationStateMachineProxy.java:121) > 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. benchmark重复执行附件中的脚本 > 2.再重启恢复，datanode有error -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IOTDB-4062) [ raft log & MetaData ] raft log recovery should not redo MeasurementAlreadyExist operation
[ https://issues.apache.org/jira/browse/IOTDB-4062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17576776#comment-17576776 ] Jialin Qiao commented on IOTDB-4062: After the schema creation operation is sent to the DataNode that manage the SchemaRegion. We could check metadata(call API locally) before putting the metadata log into the consensus layer. For those duplicated creating, we could report errors, then stop executing in consensus layer. > [ raft log & MetaData ] raft log recovery should not redo > MeasurementAlreadyExist operation > > > Key: IOTDB-4062 > URL: https://issues.apache.org/jira/browse/IOTDB-4062 > Project: Apache IoTDB > Issue Type: Improvement > Components: mpp-cluster >Reporter: 刘珍 >Assignee: Jialin Qiao >Priority: Major > Attachments: config_raft_log_recovery.properties > > > raft log恢复，会重做所有MetaData的写操作，对于失败的元数据写操作比如序列已存在： > [192.168.10.62_50010@group-0002-StateMachineUpdater] ERROR > o.a.i.d.m.v.SchemaExecutionVisitor:108 - IoTDB: MetaData error: > org.apache.iotdb.db.exception.metadata.MeasurementAlreadyExistException: Path > [root.bm68_dn62.g_0.d_0.s_1] already exist > 不需要重做。 > 完整的异常： > 2022-08-08 17:46:29,045 > [192.168.10.62_50010@group-0002-StateMachineUpdater] ERROR > o.a.i.d.m.v.SchemaExecutionVisitor:108 - IoTDB: MetaData error: > org.apache.iotdb.db.exception.metadata.MeasurementAlreadyExistException: Path > [root.bm68_dn62.g_0.d_0.s_2] already exist > at > org.apache.iotdb.db.metadata.mtree.MTreeBelowSGMemoryImpl.createTimeseries(MTreeBelowSGMemoryImpl.java:213) > at > org.apache.iotdb.db.metadata.schemaregion.SchemaRegionMemoryImpl.createTimeseries(SchemaRegionMemoryImpl.java:589) > at > org.apache.iotdb.db.metadata.visitor.SchemaExecutionVisitor.visitCreateMultiTimeSeries(SchemaExecutionVisitor.java:105) > at > org.apache.iotdb.db.metadata.visitor.SchemaExecutionVisitor.visitCreateMultiTimeSeries(SchemaExecutionVisitor.java:62) > 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:68) > at > org.apache.iotdb.consensus.ratis.ApplicationStateMachineProxy.applyTransaction(ApplicationStateMachineProxy.java:121) > 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. benchmark重复执行附件中的脚本 > 2.再重启恢复，datanode有error -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-4067) handle null pointer issue of getRegisteredNodeInfoList in NodeManager
伊丹翔 created IOTDB-4067: -- Summary: handle null pointer issue of getRegisteredNodeInfoList in NodeManager Key: IOTDB-4067 URL: https://issues.apache.org/jira/browse/IOTDB-4067 Project: Apache IoTDB Issue Type: Improvement Reporter: 伊丹翔 Assignee: 伊丹翔 it will throw an error when nodeCache didn't find the key -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IOTDB-4056) [ remove-confignode.sh ] Error: Could not find or load main class org.apache.iotdb.confignode.service.ConfigNode
[
https://issues.apache.org/jira/browse/IOTDB-4056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17576750#comment-17576750
]
Gaofei Cao commented on IOTDB-4056:
---
see pr: https://github.com/apache/iotdb/pull/6916/files
The problem is that the directory is different in `confignode` and
`distribution`.
> [ remove-confignode.sh ] Error: Could not find or load main class
> org.apache.iotdb.confignode.service.ConfigNode
>
>
> Key: IOTDB-4056
> URL: https://issues.apache.org/jira/browse/IOTDB-4056
> Project: Apache IoTDB
> Issue Type: Bug
> Components: mpp-cluster
>Affects Versions: 0.14.0-SNAPSHOT
>Reporter: 刘珍
>Assignee: Gaofei Cao
>Priority: Major
> Labels: pull-request-available
>
> [cluster@i-r0x6sjak confignode]$ ./sbin/remove-confignode.sh 172.20.70.31
>
> Starting to remove IoTDB ConfigNode
>
> WARN:
> WARN: the value of net.core.somaxconn (=128) is too small, please set it to a
> larger value using the following command.
> WARN: sudo sysctl -w net.core.somaxconn=65535
> WARN: The original net.core.somaxconn value will be set back when the os
> reboots.
> WARN:
> setting local JMX...
> Maximum memory allocation pool = 16GB, initial memory allocation pool = 800MB
> If you want to change this configuration, please check
> conf/confignode-env.sh(Unix or OS X, if you use Windows, check
> conf/confignode-env.bat).
> {color:#DE350B}*Error: Could not find or load main class
> org.apache.iotdb.confignode.service.ConfigNode*{color}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IOTDB-4065) IoTDB can not support negative timestamp (i.e. before 1970 year.)
[
https://issues.apache.org/jira/browse/IOTDB-4065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17576743#comment-17576743
]
Bo Zhang commented on IOTDB-4065:
-
I have alreay discussed this with QiaoJiaLin.
Current conslusion is that this issue is not urget and we may fix it when some
customer need it in the future.
> IoTDB can not support negative timestamp (i.e. before 1970 year.)
> -
>
> Key: IOTDB-4065
> URL: https://issues.apache.org/jira/browse/IOTDB-4065
> Project: Apache IoTDB
> Issue Type: Bug
> Components: Core/Others
>Reporter: Bo Zhang
>Assignee: Bo Zhang
>Priority: Minor
> Attachments: image-2022-08-08-18-01-38-540.png,
> image-2022-08-08-20-14-04-730.png
>
>
> Now, IoTDB can not supoort negative timestamp. (i.e. before 1970 year.)
> For example, below is supported by IoTDB
> !image-2022-08-08-18-01-38-540.png!
>
> But, if customer want to use negative timestamp for the date before 1970,
> it is not accepted.
> {color:#de350b}insert into root.sg1.d1(time, s1) values({*}-{*}31536000,
> 77);{color}
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IOTDB-4066) The allocation of regions and data needs to consider the available disk space of the node
刘珍 created IOTDB-4066: - Summary: The allocation of regions and data needs to consider the available disk space of the node Key: IOTDB-4066 URL: https://issues.apache.org/jira/browse/IOTDB-4066 Project: Apache IoTDB Issue Type: Improvement Components: mpp-cluster Reporter: 刘珍 Assignee: Yongzao Dan Attachments: image-2022-08-08-18-13-49-091.png, image-2022-08-08-18-15-39-357.png region 和数据的分配，需要考虑节点磁盘空间： 如下启动测试前，各节点的磁盘空间信息，ip4的可用磁盘空间少： !image-2022-08-08-18-13-49-091.png! 3副本*3 dataregion ，7datanode，会多出来2个副本，其中的1个副本，分配给了可用磁盘少的ip4，写入数据一段时间后ip4发生磁盘空间不足： !image-2022-08-08-18-15-39-357.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-4065) IoTDB can not support negative timestamp (i.e. before 1970 year.)
[
https://issues.apache.org/jira/browse/IOTDB-4065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bo Zhang reassigned IOTDB-4065:
---
Assignee: Bo Zhang
> IoTDB can not support negative timestamp (i.e. before 1970 year.)
> -
>
> Key: IOTDB-4065
> URL: https://issues.apache.org/jira/browse/IOTDB-4065
> Project: Apache IoTDB
> Issue Type: Bug
> Components: Core/Others
>Reporter: Bo Zhang
>Assignee: Bo Zhang
>Priority: Major
>
> Now, IoTDB can not supoort negative timestamp. (i.e. before 1970 year.)
> For example, below is supported by IoTDB
> {color:#de350b}IoTDB> insert into root.sg1.d1(time, s1) values(0, 1);{color}
> {color:#de350b}IoTDB> select ** from root slimit 10;{color}
> {color:#de350b}+-+--+{color}
> {color:#de350b}| Time|root.sg1.d1.s1|{color}
> {color:#de350b}+-+--+{color}
> {color:#de350b}|1970-01-01T08:00:00.000+08:00| 1.0|{color}
> {color:#de350b}+-+--+{color}
>
> But, if customer want to use negative timestamp for the date before 1970,
> it is not accepted.
> insert into root.sg1.d1(time, s1) values(-31536000, 77);
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IOTDB-4065) IoTDB can not support negative timestamp (i.e. before 1970 year.)
Bo Zhang created IOTDB-4065:
---
Summary: IoTDB can not support negative timestamp (i.e. before
1970 year.)
Key: IOTDB-4065
URL: https://issues.apache.org/jira/browse/IOTDB-4065
Project: Apache IoTDB
Issue Type: Bug
Components: Core/Others
Reporter: Bo Zhang
Now, IoTDB can not supoort negative timestamp. (i.e. before 1970 year.)
For example, below is supported by IoTDB
{color:#de350b}IoTDB> insert into root.sg1.d1(time, s1) values(0, 1);{color}
{color:#de350b}IoTDB> select ** from root slimit 10;{color}
{color:#de350b}+-+--+{color}
{color:#de350b}| Time|root.sg1.d1.s1|{color}
{color:#de350b}+-+--+{color}
{color:#de350b}|1970-01-01T08:00:00.000+08:00| 1.0|{color}
{color:#de350b}+-+--+{color}
But, if customer want to use negative timestamp for the date before 1970, it
is not accepted.
insert into root.sg1.d1(time, s1) values(-31536000, 77);
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IOTDB-4064) The data of the character string type fails to be imported
[ https://issues.apache.org/jira/browse/IOTDB-4064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17576674#comment-17576674 ] Chao Wang commented on IOTDB-4064: -- The character string must be enclosed in double quotation marks. > The data of the character string type fails to be imported > -- > > Key: IOTDB-4064 > URL: https://issues.apache.org/jira/browse/IOTDB-4064 > Project: Apache IoTDB > Issue Type: Bug > Components: Tools/Others >Reporter: Chao Wang >Priority: Major > Fix For: 0.14.0 > > > ./import-csv.sh -h XXX -p XXX > > !https://clouddevops.huawei.com/vision-file-storage/api/file/download/upload-v2/2022/6/26/zwx1110563/4b65df7c735c411c86811334ba4ece73/image.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-4046) Enhance pipedata.PipeData related serialize()/deserialize() codes
[ https://issues.apache.org/jira/browse/IOTDB-4046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bo Zhang reassigned IOTDB-4046: --- Assignee: Bo Zhang > Enhance pipedata.PipeData related serialize()/deserialize() codes > - > > Key: IOTDB-4046 > URL: https://issues.apache.org/jira/browse/IOTDB-4046 > Project: Apache IoTDB > Issue Type: Improvement > Components: Tools/Sync >Reporter: Bo Zhang >Assignee: Bo Zhang >Priority: Major > Labels: pull-request-available > > *org.apache.iotdb.db.sync.pipedata.PipeData* and its child class's > serialize()/deserialize() codes are not reasonable。 > !https://aone.alibaba-inc.com/v2/api/workitem/adapter/file/url?fileIdentifier=workitem%2Falibaba%2Fdefault%2F1659684536506image.png! > > Use DeletionPipeData codes as example. > Some field's serializing codes are in parent class , but the same > field's deserializing codes are in children class。 So we creat this Jira to > enhance it. > !https://aone.alibaba-inc.com/v2/api/workitem/adapter/file/url?fileIdentifier=workitem%2Falibaba%2Fdefault%2F1659684671023image.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-4064) The data of the character string type fails to be imported
Chao Wang created IOTDB-4064: Summary: The data of the character string type fails to be imported Key: IOTDB-4064 URL: https://issues.apache.org/jira/browse/IOTDB-4064 Project: Apache IoTDB Issue Type: Bug Components: Tools/Others Reporter: Chao Wang Fix For: 0.14.0 ./import-csv.sh -h XXX -p XXX !https://clouddevops.huawei.com/vision-file-storage/api/file/download/upload-v2/2022/6/26/zwx1110563/4b65df7c735c411c86811334ba4ece73/image.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-4063) An error is reported when data from version 0.12 is exported to version 0.14.
Chao Wang created IOTDB-4063: Summary: An error is reported when data from version 0.12 is exported to version 0.14. Key: IOTDB-4063 URL: https://issues.apache.org/jira/browse/IOTDB-4063 Project: Apache IoTDB Issue Type: Bug Components: Tools/Others Reporter: Chao Wang Fix For: 0.14.0 1. execute in 0.12 version INSERT INTO root.sgcc.wf01.wt01(timestamp, ts0, ts1, ts2, ts3, ts4, ts5) VALUES (2022-05-27T23:50:00.000+08:00, true, 5, 23, 15.88, .88, "IOTDB!IOTDB12345"); INSERT INTO root.sgcc.wf01.wt01(timestamp, ts0, ts1, ts2, ts3, ts4, ts5) VALUES (2022-05-26T23:50:00.000+08:00, 1, 11, 8, 88.88, .88, "IOTDB!@#B12345"); INSERT INTO root.sgcc.wf01.wt01(timestamp, ts0, ts1, ts2, ts3, ts4, ts5) VALUES (2022-05-22T00:00:00.000+08:00, true, 12, 25, 88.88, .88, "12345"); INSERT INTO root.sgcc.wf01.wt01(timestamp, ts0, ts1, ts2, ts3, ts4, ts5) VALUES (2022-05-20T23:01:14.857+08:00, 0, 3, 15, 88.88, .88, "@#$%IOTDB"); INSERT INTO root.sgcc.wf01.wt01(timestamp, ts0, ts1, ts2, ts3, ts4, ts5) VALUES (2022-05-20T16:05:02.001+08:00, 1, 7, 88, 83.08, .88, "IOTDB!@#$%IOTDB!@#$%IOTDB12345"); INSERT INTO root.sgcc.wf01.wt01(timestamp, ts0, ts1, ts2, ts3, ts4, ts5) VALUES (2022-05-21T01:05:02.258+08:00, false, 9, 24, 88.88, .88, "@#$%!@#$%12345"); INSERT INTO root.sgcc.wf01.wt01(timestamp, ts0, ts1, ts2, ts3, ts4, ts5) VALUES (2022-05-21T08:40:04.147+08:00, true, 10, 36, 88.88, .88, "IOTDB!@#$%!@#$%IOTDB12345"); INSERT INTO root.sgcc.wf01.wt01(timestamp, ts0, ts1, ts2, ts3, ts4, ts5) VALUES (2022-05-21T08:39:04.147+08:00, false, 2, 36, 88.88, .88, "IOTDBexcellent"); INSERT INTO root.sgcc.wf01.wt01(timestamp, ts0, ts1, ts2, ts3, ts4, ts5) VALUES (2022-05-21T08:40:25.976+08:00, false, 7, 36, 88.88, .88, "GoodIOTDB12345"); INSERT INTO root.sgcc.wf01.wt01(timestamp, ts0, ts1, ts2, ts3, ts4, ts5) VALUES (2022-05-21T08:56:56.249+08:00, true, 14, 36, 88.88, .88, "Hello_word"); INSERT INTO root.sgcc.wf01.wt01(timestamp, ts0, ts1, ts2, ts3, ts4, ts5) VALUES (2022-05-21T08:57:40.256+08:00, true, 14, 36, 88.88, .88, "Nihao!"); INSERT INTO root.sgcc.wf01.wt01(timestamp, ts0, ts1, ts2, ts3, ts4, ts5) VALUES (2022-05-21T08:58:55.260+08:00, true, 14, 36, 88.88, .88, "My"); 2. ./export-csv.sh -h -p 3. in 0.14 version ./import-csv.sh -h -p Import the data created in 313 to 320. The data is incompatible. The data type and encoding mode are changed. The data type changes from float to double and text to int32. The encoding mode is changed from PLAIN to RLE. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-4062) [ raft log & MetaData ] raft log recovery should not redo MeasurementAlreadyExist operation
刘珍 created IOTDB-4062: - Summary: [ raft log & MetaData ] raft log recovery should not redo MeasurementAlreadyExist operation Key: IOTDB-4062 URL: https://issues.apache.org/jira/browse/IOTDB-4062 Project: Apache IoTDB Issue Type: Improvement Components: mpp-cluster Reporter: 刘珍 Assignee: Jialin Qiao raft log恢复，会重做所有MetaData的写操作，对于失败的元数据写操作比如序列已存在： [192.168.10.62_50010@group-0002-StateMachineUpdater] ERROR o.a.i.d.m.v.SchemaExecutionVisitor:108 - IoTDB: MetaData error: org.apache.iotdb.db.exception.metadata.MeasurementAlreadyExistException: Path [root.bm68_dn62.g_0.d_0.s_1] already exist 不需要重做。 完整的异常： 2022-08-08 17:46:29,045 [192.168.10.62_50010@group-0002-StateMachineUpdater] ERROR o.a.i.d.m.v.SchemaExecutionVisitor:108 - IoTDB: MetaData error: org.apache.iotdb.db.exception.metadata.MeasurementAlreadyExistException: Path [root.bm68_dn62.g_0.d_0.s_2] already exist at org.apache.iotdb.db.metadata.mtree.MTreeBelowSGMemoryImpl.createTimeseries(MTreeBelowSGMemoryImpl.java:213) at org.apache.iotdb.db.metadata.schemaregion.SchemaRegionMemoryImpl.createTimeseries(SchemaRegionMemoryImpl.java:589) at org.apache.iotdb.db.metadata.visitor.SchemaExecutionVisitor.visitCreateMultiTimeSeries(SchemaExecutionVisitor.java:105) at org.apache.iotdb.db.metadata.visitor.SchemaExecutionVisitor.visitCreateMultiTimeSeries(SchemaExecutionVisitor.java:62) 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:68) at org.apache.iotdb.consensus.ratis.ApplicationStateMachineProxy.applyTransaction(ApplicationStateMachineProxy.java:121) 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. benchmark重复执行附件中的脚本 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-4061) Support hot configuration of data_dirs
Jialin Qiao created IOTDB-4061: -- Summary: Support hot configuration of data_dirs Key: IOTDB-4061 URL: https://issues.apache.org/jira/browse/IOTDB-4061 Project: Apache IoTDB Issue Type: New Feature Reporter: Jialin Qiao Assignee: Liuxuxin When the disk is nearly full, we need add more disks on the server and config the data_dirs, this needs to be hot-loaded. The data_dirs only support adding for new TsFile allocation, do not support removing currently. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IOTDB-3950) Transport layer optimization for sync modules
[ https://issues.apache.org/jira/browse/IOTDB-3950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17576658#comment-17576658 ] yanze chen commented on IOTDB-3950: --- No more rpc in sync, use InternalService（see review comment of https://github.com/apache/iotdb/pull/6817） > Transport layer optimization for sync modules > - > > Key: IOTDB-3950 > URL: https://issues.apache.org/jira/browse/IOTDB-3950 > Project: Apache IoTDB > Issue Type: Improvement >Reporter: yanze chen >Assignee: yanze chen >Priority: Major > > [https://apache-iotdb.feishu.cn/docx/doxcnVFJaPxG9bHQo2K5Y10sHxh] > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-4057) Support aligned timeseries in rewriteTsFileTool in 0.13
[ https://issues.apache.org/jira/browse/IOTDB-4057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jialin Qiao reassigned IOTDB-4057: -- Assignee: (was: Quan Siyi) > Support aligned timeseries in rewriteTsFileTool in 0.13 > --- > > Key: IOTDB-4057 > URL: https://issues.apache.org/jira/browse/IOTDB-4057 > Project: Apache IoTDB > Issue Type: New Feature >Reporter: Jialin Qiao >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-4057) Support aligned timeseries in rewriteTsFileTool in 0.13
[ https://issues.apache.org/jira/browse/IOTDB-4057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jialin Qiao reassigned IOTDB-4057: -- Assignee: Quan Siyi > Support aligned timeseries in rewriteTsFileTool in 0.13 > --- > > Key: IOTDB-4057 > URL: https://issues.apache.org/jira/browse/IOTDB-4057 > Project: Apache IoTDB > Issue Type: New Feature >Reporter: Jialin Qiao >Assignee: Quan Siyi >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-4056) [ remove-confignode.sh ] Error: Could not find or load main class org.apache.iotdb.confignode.service.ConfigNode
[
https://issues.apache.org/jira/browse/IOTDB-4056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jialin Qiao reassigned IOTDB-4056:
--
Assignee: Gaofei Cao (was: Chao Wang)
> [ remove-confignode.sh ] Error: Could not find or load main class
> org.apache.iotdb.confignode.service.ConfigNode
>
>
> Key: IOTDB-4056
> URL: https://issues.apache.org/jira/browse/IOTDB-4056
> Project: Apache IoTDB
> Issue Type: Bug
> Components: mpp-cluster
>Affects Versions: 0.14.0-SNAPSHOT
>Reporter: 刘珍
>Assignee: Gaofei Cao
>Priority: Major
>
> [cluster@i-r0x6sjak confignode]$ ./sbin/remove-confignode.sh 172.20.70.31
>
> Starting to remove IoTDB ConfigNode
>
> WARN:
> WARN: the value of net.core.somaxconn (=128) is too small, please set it to a
> larger value using the following command.
> WARN: sudo sysctl -w net.core.somaxconn=65535
> WARN: The original net.core.somaxconn value will be set back when the os
> reboots.
> WARN:
> setting local JMX...
> Maximum memory allocation pool = 16GB, initial memory allocation pool = 800MB
> If you want to change this configuration, please check
> conf/confignode-env.sh(Unix or OS X, if you use Windows, check
> conf/confignode-env.bat).
> {color:#DE350B}*Error: Could not find or load main class
> org.apache.iotdb.confignode.service.ConfigNode*{color}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (IOTDB-4060) [ raits ] mpp-cluster writing is getting slower and slower
[ https://issues.apache.org/jira/browse/IOTDB-4060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haonan Hou reassigned IOTDB-4060: - Assignee: Song Ziyang (was: Haonan Hou) > [ raits ] mpp-cluster writing is getting slower and slower > -- > > Key: IOTDB-4060 > URL: https://issues.apache.org/jira/browse/IOTDB-4060 > Project: Apache IoTDB > Issue Type: Bug > Components: mpp-cluster >Affects Versions: 0.14.0-SNAPSHOT >Reporter: 刘珍 >Assignee: Song Ziyang >Priority: Major > Attachments: image-2022-08-08-16-29-33-443.png, > image-2022-08-08-16-34-05-354.png, image-2022-08-08-16-35-40-320.png, > image-2022-08-08-16-35-48-119.png > > > m_0805_d037f1b > 3副本3C3D，长测配置，写入性能越来越慢 > 远程测试，1个datanode的网络监控： > !image-2022-08-08-16-29-33-443.png! > 测试过程中的结果记录到iotdb，统计1小时的写入的count(batch)和平均写入延时avg(latency): > !image-2022-08-08-16-34-05-354.png! > !image-2022-08-08-16-35-48-119.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-4060) [ raits ] mpp-cluster writing is getting slower and slower
刘珍 created IOTDB-4060: - Summary: [ raits ] mpp-cluster writing is getting slower and slower Key: IOTDB-4060 URL: https://issues.apache.org/jira/browse/IOTDB-4060 Project: Apache IoTDB Issue Type: Bug Components: mpp-cluster Affects Versions: 0.14.0-SNAPSHOT Reporter: 刘珍 Assignee: Haonan Hou Attachments: image-2022-08-08-16-29-33-443.png, image-2022-08-08-16-34-05-354.png, image-2022-08-08-16-35-40-320.png, image-2022-08-08-16-35-48-119.png m_0805_d037f1b 3副本3C3D，长测配置，写入性能越来越慢 远程测试，1个datanode的网络监控： !image-2022-08-08-16-29-33-443.png! 测试过程中的结果记录到iotdb，统计1小时的写入的count(batch)和平均写入延时avg(latency): !image-2022-08-08-16-34-05-354.png! !image-2022-08-08-16-35-48-119.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-4059) IoTDBDatabaseMetaData call getCatalogs Fail
[ https://issues.apache.org/jira/browse/IOTDB-4059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haonan Hou reassigned IOTDB-4059: - Assignee: rongli > IoTDBDatabaseMetaData call getCatalogs Fail > --- > > Key: IOTDB-4059 > URL: https://issues.apache.org/jira/browse/IOTDB-4059 > Project: Apache IoTDB > Issue Type: Bug >Reporter: Haonan Hou >Assignee: rongli >Priority: Major > > Exception in thread "main" java.lang.NullPointerException > at > org.apache.iotdb.jdbc.GroupedLSBWatermarkEncoder.(GroupedLSBWatermarkEncoder.java:44) > at > org.apache.iotdb.jdbc.IoTDBDatabaseMetadata.getWatermarkEncoder(IoTDBDatabaseMetadata.java:295) > at > org.apache.iotdb.jdbc.IoTDBDatabaseMetadata.getCatalogs(IoTDBDatabaseMetadata.java:498) > [!https://user-images.githubusercontent.com/59213908/178395526-08cb58ef-8c7e-4b0b-8188-52adea6c232e.png!|https://user-images.githubusercontent.com/59213908/178395526-08cb58ef-8c7e-4b0b-8188-52adea6c232e.png] > [!https://user-images.githubusercontent.com/59213908/178395554-928af446-03cb-4280-9086-f73027cfd3ca.png!|https://user-images.githubusercontent.com/59213908/178395554-928af446-03cb-4280-9086-f73027cfd3ca.png] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-4059) IoTDBDatabaseMetaData call getCatalogs Fail
Haonan Hou created IOTDB-4059: - Summary: IoTDBDatabaseMetaData call getCatalogs Fail Key: IOTDB-4059 URL: https://issues.apache.org/jira/browse/IOTDB-4059 Project: Apache IoTDB Issue Type: Bug Reporter: Haonan Hou Exception in thread "main" java.lang.NullPointerException at org.apache.iotdb.jdbc.GroupedLSBWatermarkEncoder.(GroupedLSBWatermarkEncoder.java:44) at org.apache.iotdb.jdbc.IoTDBDatabaseMetadata.getWatermarkEncoder(IoTDBDatabaseMetadata.java:295) at org.apache.iotdb.jdbc.IoTDBDatabaseMetadata.getCatalogs(IoTDBDatabaseMetadata.java:498) [!https://user-images.githubusercontent.com/59213908/178395526-08cb58ef-8c7e-4b0b-8188-52adea6c232e.png!|https://user-images.githubusercontent.com/59213908/178395526-08cb58ef-8c7e-4b0b-8188-52adea6c232e.png] [!https://user-images.githubusercontent.com/59213908/178395554-928af446-03cb-4280-9086-f73027cfd3ca.png!|https://user-images.githubusercontent.com/59213908/178395554-928af446-03cb-4280-9086-f73027cfd3ca.png] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [iotdb-client-go] HTHou merged pull request #49: [To rel/0.13][IOTDB-4009] Add aligned timeseries APIs for go client
HTHou merged PR #49: URL: https://github.com/apache/iotdb-client-go/pull/49 -- 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
[GitHub] [iotdb-client-go] HTHou merged pull request #47: [IOTDB-4009] Add aligned timeseries APIs for go client
HTHou merged PR #47: URL: https://github.com/apache/iotdb-client-go/pull/47 -- 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
[GitHub] [iotdb-client-go] 2b3c511 closed pull request #48: [IOTDB-4009] Add aligned timeseries APIs for go client
2b3c511 closed pull request #48: [IOTDB-4009] Add aligned timeseries APIs for go client URL: https://github.com/apache/iotdb-client-go/pull/48 -- 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
[jira] [Created] (IOTDB-4058) DataPartition inheritance policy
Yongzao Dan created IOTDB-4058: -- Summary: DataPartition inheritance policy Key: IOTDB-4058 URL: https://issues.apache.org/jira/browse/IOTDB-4058 Project: Apache IoTDB Issue Type: Improvement Reporter: Yongzao Dan Assignee: Yongzao Dan Fix For: 0.14.0 Currently, the GreedyPartitionAllocator always allocate new DataPartitions to the DataRegion who has the lowest PartitionSlots. However, it's better to allocate those DataPartitions with the same SeriesPartitionSlots and continuous TimePartitionSlots to a consistent DataRegion. Because the query efficiency will be improved -- This message was sent by Atlassian Jira (v8.20.10#820010)
