[jira] [Created] (IOTDB-4750) Refactor the configuration file
Jialin Qiao created IOTDB-4750: -- Summary: Refactor the configuration file Key: IOTDB-4750 URL: https://issues.apache.org/jira/browse/IOTDB-4750 Project: Apache IoTDB Issue Type: Improvement Reporter: Jialin Qiao Assignee: Haonan Hou Introduce iotdb-common.properties. Details see: https://apache-iotdb.feishu.cn/docx/doxcnjzB2xd9sScIlkNYJUJA1zb -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [iotdb-client-go] qiaojialin merged pull request #55: Use 1c1d docker to run go client IT
qiaojialin merged PR #55: URL: https://github.com/apache/iotdb-client-go/pull/55 -- 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] [Assigned] (IOTDB-4673) [ confignode/datanode configuration parameters ] Removes the space character from both the start and the end of the parameter value
[
https://issues.apache.org/jira/browse/IOTDB-4673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jialin Qiao reassigned IOTDB-4673:
--
Assignee: Gaofei Cao (was: Jialin Qiao)
> [ confignode/datanode configuration parameters ] Removes the space character
> from both the start and the end of the parameter value
> ---
>
> Key: IOTDB-4673
> URL: https://issues.apache.org/jira/browse/IOTDB-4673
> Project: Apache IoTDB
> Issue Type: Improvement
> Components: mpp-cluster
>Reporter: 刘珍
>Assignee: Gaofei Cao
>Priority: Minor
>
> 举个例子
> data_region_ratis_max_retry_attempts = 2
> confignode配置文件中的这个参数值后面不小心多了1个空格"2 " ，启动confignode报错
> confignode/datanode配置参数在代码里需要过滤掉空格。
> 2022-10-18 09:31:12,529 [main] INFO o.a.i.m.c.MetricConfigDescriptor:54 -
> Start to read config file ./confignode/sbin/../conf/iotdb-metric.yml
> Exception in thread "main" java.lang.ExceptionInInitializerError
> at
> org.apache.iotdb.confignode.conf.ConfigNodeDescriptor.getInstance(ConfigNodeDescriptor.java:491)
> at
> org.apache.iotdb.confignode.service.ConfigNode.(ConfigNode.java:55)
> {color:#DE350B}*Caused by: java.lang.NumberFormatException: For input string:
> "2 "*{color}
> at
> java.base/java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
> at java.base/java.lang.Integer.parseInt(Integer.java:652)
> at java.base/java.lang.Integer.parseInt(Integer.java:770)
> at
> org.apache.iotdb.confignode.conf.ConfigNodeDescriptor.loadRatisConsensusConfig(ConfigNodeDescriptor.java:446)
> at
> org.apache.iotdb.confignode.conf.ConfigNodeDescriptor.loadProps(ConfigNodeDescriptor.java:272)
> at
> org.apache.iotdb.confignode.conf.ConfigNodeDescriptor.(ConfigNodeDescriptor.java:47)
> at
> org.apache.iotdb.confignode.conf.ConfigNodeDescriptor.(ConfigNodeDescriptor.java:39)
> at
> org.apache.iotdb.confignode.conf.ConfigNodeDescriptor$ConfigNodeDescriptorHolder.(ConfigNodeDescriptor.java:496)
> ... 2 more
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IOTDB-4749) [0.14][standalone] restart confignode, large logs are generated
ZhangZhengming created IOTDB-4749:
-
Summary: [0.14][standalone] restart confignode, large logs are
generated
Key: IOTDB-4749
URL: https://issues.apache.org/jira/browse/IOTDB-4749
Project: Apache IoTDB
Issue Type: Bug
Reporter: ZhangZhengming
Assignee: Jialin Qiao
Attachments: image-2022-10-25-11-54-03-093.png,
image-2022-10-25-11-57-26-222.png, image-2022-10-25-11-58-35-600.png
1C3D, I write 10,000,000,000 points in benchmark
(Client=10 sg=20, device=100, sensor=1000)
data/confignode size is 4M
!image-2022-10-25-11-57-26-222.png|width=498,height=50!
restart confignode generate {color:#de350b}118M logs{color}
!image-2022-10-25-11-58-35-600.png|width=541,height=367!
See attachment for log..
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IOTDB-4748) Give Storage Group another name: Database
Jialin Qiao created IOTDB-4748: -- Summary: Give Storage Group another name: Database Key: IOTDB-4748 URL: https://issues.apache.org/jira/browse/IOTDB-4748 Project: Apache IoTDB Issue Type: Improvement Reporter: Jialin Qiao enable create database root.db which equals to create storage group root.db -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IOTDB-4745) Execute start-confignode.sh third times simultaneously meets error that one confignode cannot startup successflly
[ https://issues.apache.org/jira/browse/IOTDB-4745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17623537#comment-17623537 ] Yongzao Dan commented on IOTDB-4745: I'll fix this after [IOTDB-4742|https://github.com/apache/iotdb/pull/7712] is merged. > Execute start-confignode.sh third times simultaneously meets error that one > confignode cannot startup successflly > - > > Key: IOTDB-4745 > URL: https://issues.apache.org/jira/browse/IOTDB-4745 > Project: Apache IoTDB > Issue Type: Bug >Reporter: Gaofei Cao >Assignee: Yongzao Dan >Priority: Major > Attachments: confignode1.log, confignode2.log, confignode3.log, > image-2022-10-25-10-43-17-883.png, image-2022-10-25-10-43-37-807.png > > > !image-2022-10-25-10-43-37-807.png|width=947,height=275! > > !image-2022-10-25-10-43-17-883.png|width=1148,height=414! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-4745) Execute start-confignode.sh third times simultaneously meets error that one confignode cannot startup successflly
[ https://issues.apache.org/jira/browse/IOTDB-4745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yongzao Dan reassigned IOTDB-4745: -- Assignee: Yongzao Dan (was: Song Ziyang) > Execute start-confignode.sh third times simultaneously meets error that one > confignode cannot startup successflly > - > > Key: IOTDB-4745 > URL: https://issues.apache.org/jira/browse/IOTDB-4745 > Project: Apache IoTDB > Issue Type: Bug >Reporter: Gaofei Cao >Assignee: Yongzao Dan >Priority: Major > Attachments: confignode1.log, confignode2.log, confignode3.log, > image-2022-10-25-10-43-17-883.png, image-2022-10-25-10-43-37-807.png > > > !image-2022-10-25-10-43-37-807.png|width=947,height=275! > > !image-2022-10-25-10-43-17-883.png|width=1148,height=414! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-4745) Execute start-confignode.sh third times simultaneously meets error that one confignode cannot startup successflly
[ https://issues.apache.org/jira/browse/IOTDB-4745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yongzao Dan reassigned IOTDB-4745: -- Assignee: Song Ziyang (was: Yongzao Dan) > Execute start-confignode.sh third times simultaneously meets error that one > confignode cannot startup successflly > - > > Key: IOTDB-4745 > URL: https://issues.apache.org/jira/browse/IOTDB-4745 > Project: Apache IoTDB > Issue Type: Bug >Reporter: Gaofei Cao >Assignee: Song Ziyang >Priority: Major > Attachments: confignode1.log, confignode2.log, confignode3.log, > image-2022-10-25-10-43-17-883.png, image-2022-10-25-10-43-37-807.png > > > !image-2022-10-25-10-43-37-807.png|width=947,height=275! > > !image-2022-10-25-10-43-17-883.png|width=1148,height=414! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-4747) 区分系统storage
xuan.wang created IOTDB-4747: Summary: 区分系统storage Key: IOTDB-4747 URL: https://issues.apache.org/jira/browse/IOTDB-4747 Project: Apache IoTDB Issue Type: Improvement Components: Core/Others Reporter: xuan.wang 目前会有一些系统内置的storage、比如：root._metric（监控）、root.system.audit（系统审计日志）等。 当做一些统计业务存储组、业务测点数量时，必须手动过滤这些非业务数据。但是目前并没有统一的前缀，是否可以为系统内置的storage统一前缀、或指定某些规则 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-4746) 支持对不固定子节点的函数运算
xuan.wang created IOTDB-4746:
Summary: 支持对不固定子节点的函数运算
Key: IOTDB-4746
URL: https://issues.apache.org/jira/browse/IOTDB-4746
Project: Apache IoTDB
Issue Type: Improvement
Components: Core/Query
Reporter: xuan.wang
*Is your feature request related to a problem? Please describe.*
当我查询一些最新数据时，比如查询最新的10条，可以通过order by time desc limit 10。
但是有时候需要对查询回来的每一行的数据做运算，比如求和、取平均值等等。
当子节点明确时 可以通过 select s1+s2+s3 from root.data.g_0.d_0 order by time desc limit 10;
但现实的场景中子节点是不固定的，名称也是未知的。
可以通过目前的group by对子节点进行聚合后进行函数运算，但是无法支持取最近10个时间序列每一个时间点的单独计算。
_现在可以查询出来后通过遍历每一行、每一个子节点来进行计算。_
_或者通过采集间隔，计算出时间点 结合 group by (),level=来进行查询，_
_比如： 5s采集一次，取最近10条，当前时间为2022-10-18T17:23:54，则50s前为2022-10-18T17:23:04_
_select * from root.data.g_0.d_0._ where time > 2022-10-18T17:23:04 group by
([2022-10-18T17:23:04, 2022-10-18T17:23:54), 5s),level=1,2,3
*Describe the solution you'd like*
是否可以增加一些函数用来对子节点的值进行计算。比如 增加 node_sum 函数
比如 {{select node_sum(*) from root.data.g_0.d_0.* order by time desc limit 10;}}
+-+---+
| Time| node_sum(root.data.g_0.d_0.{_})|{_}
_+-+---+_
_|2022-10-18T16:41:24.195+08:00| 0.0|_
_|2022-10-18T16:41:09.195+08:00| 0.0|_
_|2022-10-18T16:40:54.195+08:00| 0.0|_
_|2022-10-18T16:40:39.195+08:00| 0.0|_
_|2022-10-18T16:40:24.195+08:00| 0.0|_
_|2022-10-18T16:40:09.195+08:00| 0.0|_
_|2022-10-18T16:39:54.195+08:00| 5.36E8|_
_|2022-10-18T16:39:39.822+08:00| 5.82E8|_
_|2022-10-18T16:39:24.195+08:00| 0.0|_
_|2022-10-18T16:39:09.195+08:00| 0.0|_
_+++_
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IOTDB-4745) Execute start-confignode.sh third times simultaneously meets error that one confignode cannot startup successflly
Gaofei Cao created IOTDB-4745: - Summary: Execute start-confignode.sh third times simultaneously meets error that one confignode cannot startup successflly Key: IOTDB-4745 URL: https://issues.apache.org/jira/browse/IOTDB-4745 Project: Apache IoTDB Issue Type: Bug Reporter: Gaofei Cao Assignee: Yongzao Dan Attachments: confignode1.log, confignode2.log, confignode3.log, image-2022-10-25-10-43-17-883.png, image-2022-10-25-10-43-37-807.png !image-2022-10-25-10-43-37-807.png|width=947,height=275! !image-2022-10-25-10-43-17-883.png|width=1148,height=414! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-4744) [DispatchFailed] java.lang.IndexOutOfBoundsException: Index: 3, Size: 3
刘珍 created IOTDB-4744:
-
Summary: [DispatchFailed] java.lang.IndexOutOfBoundsException:
Index: 3, Size: 3
Key: IOTDB-4744
URL: https://issues.apache.org/jira/browse/IOTDB-4744
Project: Apache IoTDB
Issue Type: Bug
Components: mpp-cluster
Affects Versions: 0.14.0-SNAPSHOT
Reporter: 刘珍
Assignee: Jinrui Zhang
master_1023_2fea011
schema region : ratis
data region : multiLeader
3rep , 3C3D .
benchmark：
IS_DELETE_DATA=false
CREATE_SCHEMA=true
benchmark runs the metadata creation operation twice, (ip62） datanode ERROR LOG
:
2022-10-25 09:53:12,210
[pool-26-IoTDB-ClientRPC-Processor-8$20221025_015312_00103_3]
{color:#DE350B}*ERROR o.a.i.d.m.p.s.FragmentInstanceDispatcherImpl:123 -
[DispatchFailed]
java.lang.IndexOutOfBoundsException: Index: 3, Size: 3*{color}
at java.util.ArrayList.rangeCheck(ArrayList.java:659)
at java.util.ArrayList.remove(ArrayList.java:498)
at
org.apache.iotdb.db.mpp.plan.planner.plan.node.metedata.write.MeasurementGroup.removeMeasurement(MeasurementGroup.java:122)
at
org.apache.iotdb.db.mpp.execution.executor.RegionWriteExecutor$WritePlanNodeExecutionVisitor.visitCreateMultiTimeSeries(RegionWriteExecutor.java:349)
at
org.apache.iotdb.db.mpp.execution.executor.RegionWriteExecutor$WritePlanNodeExecutionVisitor.visitCreateMultiTimeSeries(RegionWriteExecutor.java:113)
at
org.apache.iotdb.db.mpp.plan.planner.plan.node.metedata.write.CreateMultiTimeSeriesNode.accept(CreateMultiTimeSeriesNode.java:141)
at
org.apache.iotdb.db.mpp.execution.executor.RegionWriteExecutor.execute(RegionWriteExecutor.java:79)
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:277)
at
org.apache.iotdb.db.mpp.plan.execution.QueryExecution.start(QueryExecution.java:195)
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.createMultiTimeseries(ClientRPCServiceImpl.java:467)
at
org.apache.iotdb.service.rpc.thrift.IClientRPCService$Processor$createMultiTimeseries.getResult(IClientRPCService.java:3387)
at
org.apache.iotdb.service.rpc.thrift.IClientRPCService$Processor$createMultiTimeseries.getResult(IClientRPCService.java:3367)
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.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)
Test environment ：
1. 192.168.10.62 / 66 /68 72CPU 256GB
benchmark : ip64 /data/liuzhen_test/weektest/benchmark_tool
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
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"
MAX_DIRECT_MEMORY_SIZE="32G"
query_timeout_threshold=3600
2. benchmark configuration
see attachment .
Run twice
3. View ip62 datanode logs
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IOTDB-4743) [sync] OperatePipeProcedure support rollback
yanze chen created IOTDB-4743: - Summary: [sync] OperatePipeProcedure support rollback Key: IOTDB-4743 URL: https://issues.apache.org/jira/browse/IOTDB-4743 Project: Apache IoTDB Issue Type: New Feature Reporter: yanze chen Assignee: yanze chen OperatePipeProcedure support rollback -- 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=17623497#comment-17623497 ] 刘珍 commented on IOTDB-4632: --- master_1023_2fea011 ，加大ratis request timeout ，依然有大量元数据path已存在的ERROR 2022-10-25 09:30:21,874 [5@group-00020006-StateMachineUpdater] ERROR o.a.i.d.m.v.SchemaExecutionVisitor:105 - IoTDB: MetaData error: org.apache.iotdb.db.exception.metadata.MeasurementAlreadyExistException: Path [root.test.g_6.d_106.s_48388] already exist !screenshot-1.png! > [ 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] [Commented] (IOTDB-3624) Meet error when inserting data in SQL without timestamp
[
https://issues.apache.org/jira/browse/IOTDB-3624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17623482#comment-17623482
]
Minghui Liu commented on IOTDB-3624:
We need to cherry-pick this PR to rel/0.13.
> Meet error when inserting data in SQL without timestamp
> ---
>
> Key: IOTDB-3624
> URL: https://issues.apache.org/jira/browse/IOTDB-3624
> Project: Apache IoTDB
> Issue Type: Bug
> Components: Core/Server
>Affects Versions: 0.13.0, 0.14.0-SNAPSHOT
>Reporter: xiaozhihong
>Assignee: liuyu
>Priority: Minor
> Labels: pull-request-available
> Fix For: master branch
>
> Attachments: image-2022-06-23-10-43-49-858.png,
> image-2022-09-14-11-27-49-721.png
>
>
> The replay scenario is: There are two time series, one is text data type, the
> other is float data type. Default system time, inserted data at the same
> time, then there is a metadata error: the measurementList's size is not
> consistent with the valueList's size.
> {code:java}
> IoTDB> set storage group to root.sg;
> Msg: The statement is executed successfully.
> IoTDB> create timeseries root.sg.d1.s1 with datatype=FLOAT,encoding=RLE;
> Msg: The statement is executed successfully.
> IoTDB> create timeseries root.sg.d1.s2 with datatype=TEXT,encoding=RLE;
> Msg: 303: encoding RLE does not support TEXT
> IoTDB> create timeseries root.sg.d1.s2 with datatype=TEXT,encoding=PLAIN;
> Msg: The statement is executed successfully.
> IoTDB> show timeseries root.**;
> +-+-+-+++---++--+
> | timeseries|alias|storage
> group|dataType|encoding|compression|tags|attributes|
> +-+-+-+++---++--+
> |root.sg.d1.s1| null| root.sg| FLOAT| RLE| SNAPPY|null|
> null|
> |root.sg.d1.s2| null| root.sg| TEXT| PLAIN| SNAPPY|null|
> null|
> +-+-+-+++---++--+
> Total line number = 2
> It costs 0.072s
> IoTDB> insert into root.sg.d1(s1,s2) values(25,'test');
> Msg: 303: Check metadata error: the measurementList's size is not consistent
> with the valueList's size
> {code}
> The log picture is as follow:
> !image-2022-06-23-10-43-49-858.png|width=557,height=226!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Reopened] (IOTDB-3624) Meet error when inserting data in SQL without timestamp
[
https://issues.apache.org/jira/browse/IOTDB-3624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Minghui Liu reopened IOTDB-3624:
> Meet error when inserting data in SQL without timestamp
> ---
>
> Key: IOTDB-3624
> URL: https://issues.apache.org/jira/browse/IOTDB-3624
> Project: Apache IoTDB
> Issue Type: Bug
> Components: Core/Server
>Affects Versions: 0.13.0, 0.14.0-SNAPSHOT
>Reporter: xiaozhihong
>Assignee: liuyu
>Priority: Minor
> Labels: pull-request-available
> Fix For: master branch
>
> Attachments: image-2022-06-23-10-43-49-858.png,
> image-2022-09-14-11-27-49-721.png
>
>
> The replay scenario is: There are two time series, one is text data type, the
> other is float data type. Default system time, inserted data at the same
> time, then there is a metadata error: the measurementList's size is not
> consistent with the valueList's size.
> {code:java}
> IoTDB> set storage group to root.sg;
> Msg: The statement is executed successfully.
> IoTDB> create timeseries root.sg.d1.s1 with datatype=FLOAT,encoding=RLE;
> Msg: The statement is executed successfully.
> IoTDB> create timeseries root.sg.d1.s2 with datatype=TEXT,encoding=RLE;
> Msg: 303: encoding RLE does not support TEXT
> IoTDB> create timeseries root.sg.d1.s2 with datatype=TEXT,encoding=PLAIN;
> Msg: The statement is executed successfully.
> IoTDB> show timeseries root.**;
> +-+-+-+++---++--+
> | timeseries|alias|storage
> group|dataType|encoding|compression|tags|attributes|
> +-+-+-+++---++--+
> |root.sg.d1.s1| null| root.sg| FLOAT| RLE| SNAPPY|null|
> null|
> |root.sg.d1.s2| null| root.sg| TEXT| PLAIN| SNAPPY|null|
> null|
> +-+-+-+++---++--+
> Total line number = 2
> It costs 0.072s
> IoTDB> insert into root.sg.d1(s1,s2) values(25,'test');
> Msg: 303: Check metadata error: the measurementList's size is not consistent
> with the valueList's size
> {code}
> The log picture is as follow:
> !image-2022-06-23-10-43-49-858.png|width=557,height=226!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IOTDB-4628) [sync] Do not store pipe infomation after drop
[ https://issues.apache.org/jira/browse/IOTDB-4628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17623479#comment-17623479 ] yanze chen commented on IOTDB-4628: --- https://github.com/apache/iotdb/pull/7581 > [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 >Priority: Major > > 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-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
]
Jinrui Zhang reassigned IOTDB-4508:
---
Assignee: Jinrui Zhang (was: Haiming Zhu)
> [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, image-2022-10-13-08-52-13-345.png,
> iotdb-confignode.properties, iotdb-datanode.properties,
> log-all-20221012.0.log.gz, log-all-20221012.1.log.gz,
> log-error-20221012.0.log.gz, 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 09:08:23,478
> [pool-22-IoTDB-ClientRPC-Processor-37$20220923_010343_02955_5]
[jira] [Assigned] (IOTDB-4622) Show regions command meets error when data region is not created completely.
[ https://issues.apache.org/jira/browse/IOTDB-4622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaofei Cao reassigned IOTDB-4622: - Assignee: Gaofei Cao > Show regions command meets error when data region is not created completely. > > > Key: IOTDB-4622 > URL: https://issues.apache.org/jira/browse/IOTDB-4622 > 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-4742) Ratis: add new API (addNewNodeToExistedGroup)
[ https://issues.apache.org/jira/browse/IOTDB-4742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Song Ziyang reassigned IOTDB-4742: -- Sprint: 2022-10-Cluster Assignee: Song Ziyang > Ratis: add new API (addNewNodeToExistedGroup) > - > > Key: IOTDB-4742 > URL: https://issues.apache.org/jira/browse/IOTDB-4742 > Project: Apache IoTDB > Issue Type: Improvement >Reporter: Song Ziyang >Assignee: Song Ziyang >Priority: Major > > Ratis should call addPeer before createPeer -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-4742) Ratis: add new API (addNewNodeToExistedGroup)
Song Ziyang created IOTDB-4742: -- Summary: Ratis: add new API (addNewNodeToExistedGroup) Key: IOTDB-4742 URL: https://issues.apache.org/jira/browse/IOTDB-4742 Project: Apache IoTDB Issue Type: Improvement Reporter: Song Ziyang Ratis should call addPeer before createPeer -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-4741) deprecate sessionId in all rpc requests
Xiangdong Huang created IOTDB-4741: -- Summary: deprecate sessionId in all rpc requests Key: IOTDB-4741 URL: https://issues.apache.org/jira/browse/IOTDB-4741 Project: Apache IoTDB Issue Type: Task Reporter: Xiangdong Huang Letting client claim its sessionId is not a good practice. Using and manage a ClientSession to describe each connection on the server side is more safe. Besides, Current timeout connection can not be closed by the server side, which may lead resource leakage if clients forget to close their connections. Therefore, we can close the socket connection to notify Thrift close the session. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [iotdb-client-go] HTHou merged pull request #54: Bump github.com/stretchr/testify from 1.8.0 to 1.8.1
HTHou merged PR #54: URL: https://github.com/apache/iotdb-client-go/pull/54 -- 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] [Assigned] (IOTDB-4740) Modify interface of Create UDF and UDFInformation
[ https://issues.apache.org/jira/browse/IOTDB-4740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] 李伟豪 reassigned IOTDB-4740: -- Assignee: 李伟豪 > Modify interface of Create UDF and UDFInformation > - > > Key: IOTDB-4740 > URL: https://issues.apache.org/jira/browse/IOTDB-4740 > Project: Apache IoTDB > Issue Type: Task >Reporter: 李伟豪 >Assignee: 李伟豪 >Priority: Major > > refers to > [here|https://apache-iotdb.feishu.cn/docx/XHved9iUao6AyfxulKOcYw1sntg] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-4740) Modify interface of Create UDF and UDFInformation
李伟豪 created IOTDB-4740: -- Summary: Modify interface of Create UDF and UDFInformation Key: IOTDB-4740 URL: https://issues.apache.org/jira/browse/IOTDB-4740 Project: Apache IoTDB Issue Type: Task Reporter: 李伟豪 refers to [here|https://apache-iotdb.feishu.cn/docx/XHved9iUao6AyfxulKOcYw1sntg] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-4712) Add size limit of trigger jar on ConfigNode
[ https://issues.apache.org/jira/browse/IOTDB-4712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] 李伟豪 reassigned IOTDB-4712: -- Assignee: 李伟豪 > Add size limit of trigger jar on ConfigNode > --- > > Key: IOTDB-4712 > URL: https://issues.apache.org/jira/browse/IOTDB-4712 > Project: Apache IoTDB > Issue Type: Sub-task >Reporter: 李伟豪 >Assignee: 李伟豪 >Priority: Major > Labels: pull-request-available > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-4739) [compression algorithm] Implement a new compression algorithm: Zstandard
GuanChu Shen created IOTDB-4739: --- Summary: [compression algorithm] Implement a new compression algorithm: Zstandard Key: IOTDB-4739 URL: https://issues.apache.org/jira/browse/IOTDB-4739 Project: Apache IoTDB Issue Type: New Feature Components: TsFile Reporter: GuanChu Shen Assignee: GuanChu Shen Zstandard, or zstd as short version, is a fast lossless compression algorithm. Zstd can trade compression speed for stronger compression ratios. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IOTDB-4739) [compression algorithm] Implement a new compression algorithm: Zstandard
[ https://issues.apache.org/jira/browse/IOTDB-4739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17623078#comment-17623078 ] GuanChu Shen commented on IOTDB-4739: - I'm doing this. > [compression algorithm] Implement a new compression algorithm: Zstandard > > > Key: IOTDB-4739 > URL: https://issues.apache.org/jira/browse/IOTDB-4739 > Project: Apache IoTDB > Issue Type: New Feature > Components: TsFile >Reporter: GuanChu Shen >Assignee: GuanChu Shen >Priority: Major > Original Estimate: 1m > Remaining Estimate: 1m > > Zstandard, or zstd as short version, is a fast lossless compression > algorithm. Zstd can trade compression speed for stronger compression ratios. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IOTDB-4738) TsFile damaged after writing empty value pages
[ https://issues.apache.org/jira/browse/IOTDB-4738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17623033#comment-17623033 ] 周沛辰 commented on IOTDB-4738: Write a value page first, which has no statistics, and then write an empty value page. When reading this file, the system will think that these two pages have their own statistic, but they do not, so an error will be reported. > TsFile damaged after writing empty value pages > -- > > Key: IOTDB-4738 > URL: https://issues.apache.org/jira/browse/IOTDB-4738 > Project: Apache IoTDB > Issue Type: Bug >Reporter: 周沛辰 >Assignee: 周沛辰 >Priority: Major > Attachments: image-2022-10-24-16-06-23-790.png > > Original Estimate: 24h > Remaining Estimate: 24h > > java.io.IOException: FAILED_TO_UNCOMPRESS(5) > at org.xerial.snappy.SnappyNative.throw_error(SnappyNative.java:112) > at org.xerial.snappy.SnappyNative.rawUncompress(Native Method) > at org.xerial.snappy.Snappy.rawUncompress(Snappy.java:478) > at org.xerial.snappy.Snappy.uncompress(Snappy.java:517) > at > org.apache.iotdb.tsfile.compress.IUnCompressor$SnappyUnCompressor.uncompress(IUnCompressor.java:168) > at > org.apache.iotdb.tsfile.read.TsFileSequenceReader.readPage(TsFileSequenceReader.java:1295) > at > org.apache.iotdb.db.tools.validate.TsFileValidationTool.findUncorrectFiles(TsFileValidationTool.java:245) > at > org.apache.iotdb.db.engine.compaction.FastAlignedCrossCompactionTest.validateSeqFiles(FastAlignedCrossCompactionTest.java:5215) > at > org.apache.iotdb.db.engine.compaction.FastAlignedCrossCompactionTest.test9(FastAlignedCrossCompactionTest.java:2737) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59) > at > org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at > org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56) > at > org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) > at > org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) > at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) > at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306) > at > org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366) > at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103) > at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63) > at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329) > at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293) > at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306) > at org.junit.runners.ParentRunner.run(ParentRunner.java:413) > at org.junit.runner.JUnitCore.run(JUnitCore.java:137) > at > com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:69) > at > com.intellij.rt.junit.IdeaTestRunner$Repeater$1.execute(IdeaTestRunner.java:38) > at com.intellij.rt.execution.junit.TestsRepeater.repeat(TestsRepeater.java:11) > at > com.intellij.rt.junit.IdeaTestRunner$Repeater.startRunnerWithArgs(IdeaTestRunner.java:35) > at > com.intellij.rt.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:235) > at com.intellij.rt.junit.JUnitStarter.main(JUnitStarter.java:54) > -- Meet errors in reading file > /Users/bensonchou/PersonalFiles/IOTDB/projects/choubenson/iotdb/server/target/data/sequence/root.compactionTest/0/0/1666596230093-2-0-1.tsfile, > tsfile may be corrupted. > !image-2022-10-24-16-06-23-790.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-4738) TsFile damaged after writing empty pages
周沛辰 created IOTDB-4738: -- Summary: TsFile damaged after writing empty pages Key: IOTDB-4738 URL: https://issues.apache.org/jira/browse/IOTDB-4738 Project: Apache IoTDB Issue Type: Bug Reporter: 周沛辰 Assignee: 周沛辰 Attachments: image-2022-10-24-16-06-23-790.png java.io.IOException: FAILED_TO_UNCOMPRESS(5) at org.xerial.snappy.SnappyNative.throw_error(SnappyNative.java:112) at org.xerial.snappy.SnappyNative.rawUncompress(Native Method) at org.xerial.snappy.Snappy.rawUncompress(Snappy.java:478) at org.xerial.snappy.Snappy.uncompress(Snappy.java:517) at org.apache.iotdb.tsfile.compress.IUnCompressor$SnappyUnCompressor.uncompress(IUnCompressor.java:168) at org.apache.iotdb.tsfile.read.TsFileSequenceReader.readPage(TsFileSequenceReader.java:1295) at org.apache.iotdb.db.tools.validate.TsFileValidationTool.findUncorrectFiles(TsFileValidationTool.java:245) at org.apache.iotdb.db.engine.compaction.FastAlignedCrossCompactionTest.validateSeqFiles(FastAlignedCrossCompactionTest.java:5215) at org.apache.iotdb.db.engine.compaction.FastAlignedCrossCompactionTest.test9(FastAlignedCrossCompactionTest.java:2737) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306) at org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100) at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63) at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329) at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293) at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306) at org.junit.runners.ParentRunner.run(ParentRunner.java:413) at org.junit.runner.JUnitCore.run(JUnitCore.java:137) at com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:69) at com.intellij.rt.junit.IdeaTestRunner$Repeater$1.execute(IdeaTestRunner.java:38) at com.intellij.rt.execution.junit.TestsRepeater.repeat(TestsRepeater.java:11) at com.intellij.rt.junit.IdeaTestRunner$Repeater.startRunnerWithArgs(IdeaTestRunner.java:35) at com.intellij.rt.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:235) at com.intellij.rt.junit.JUnitStarter.main(JUnitStarter.java:54) -- Meet errors in reading file /Users/bensonchou/PersonalFiles/IOTDB/projects/choubenson/iotdb/server/target/data/sequence/root.compactionTest/0/0/1666596230093-2-0-1.tsfile, tsfile may be corrupted. !image-2022-10-24-16-06-23-790.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-4737) [UDF] Modify user doc of UDF
liaolanyu created IOTDB-4737: Summary: [UDF] Modify user doc of UDF Key: IOTDB-4737 URL: https://issues.apache.org/jira/browse/IOTDB-4737 Project: Apache IoTDB Issue Type: Improvement Reporter: liaolanyu Assignee: liaolanyu -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-4736) [UDF] Refactor process of show function
liaolanyu created IOTDB-4736: Summary: [UDF] Refactor process of show function Key: IOTDB-4736 URL: https://issues.apache.org/jira/browse/IOTDB-4736 Project: Apache IoTDB Issue Type: Improvement Reporter: liaolanyu Assignee: liaolanyu Show function task should retrieve all UDFs from confignode instead of returning the information on datanode. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-4735) [UDF] Refactor process of drop function
liaolanyu created IOTDB-4735: Summary: [UDF] Refactor process of drop function Key: IOTDB-4735 URL: https://issues.apache.org/jira/browse/IOTDB-4735 Project: Apache IoTDB Issue Type: Improvement Reporter: liaolanyu Assignee: liaolanyu -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-4734) [UDF] Modify create function grammaer and process
liaolanyu created IOTDB-4734: Summary: [UDF] Modify create function grammaer and process Key: IOTDB-4734 URL: https://issues.apache.org/jira/browse/IOTDB-4734 Project: Apache IoTDB Issue Type: Improvement Reporter: liaolanyu Assignee: liaolanyu Now, we need to specify the path of jar file when creating UDF. DBA need not to put jar into specified dir manually after this pr. We will transfer the jar to nodes in the cluster. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-4733) [UDF] Modify register-UDF.bat/sh to adapt to new UDF grammar
liaolanyu created IOTDB-4733: Summary: [UDF] Modify register-UDF.bat/sh to adapt to new UDF grammar Key: IOTDB-4733 URL: https://issues.apache.org/jira/browse/IOTDB-4733 Project: Apache IoTDB Issue Type: Improvement Reporter: liaolanyu Assignee: liaolanyu After changing UDF grammar, this should be modified to adapt to the changes. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-4731) [ remove datanode ] Data is inconsistent （ remove datanode before the synchronization is complete ）
[
https://issues.apache.org/jira/browse/IOTDB-4731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
刘珍 reassigned IOTDB-4731:
-
Attachment: image-2022-10-24-15-22-17-729.png
image-2022-10-24-15-13-45-086.png
Component/s: mpp-cluster
Sprint: 2022-10-Cluster
Assignee: Jinrui Zhang
Description:
master_1023_2fea011
3rep ， 3C3D ，benchmark write done .
Start the fourth datanode (ip64).
ip68 : SET SYSTEM TO READONLY ON LOCAL
remove datanode(ip68).
before remove , ip68 is DataRegion[14]' Leader , there is unsynchronized data:
!image-2022-10-24-15-13-45-086.png!
When ip68 is in the removing state ， datanode error log :
2022-10-24 14:18:18,092 [pool-49-IoTDB-LogDispatcher-DataRegion[14]-3] ERROR
o.a.i.d.w.n.WALNode$PlanNodeIterator:590 - Fail to read wal from wal file
/data/liuzhen_test/master_1023_2fea011/sbin/../data/datanode/wal/root.test.g_4-14/_150-200-1.wal,
skip this file.
java.nio.channels.ClosedByInterruptException: null
at
java.nio.channels.spi.AbstractInterruptibleChannel.end(AbstractInterruptibleChannel.java:202)
at sun.nio.ch.FileChannelImpl.size(FileChannelImpl.java:315)
at
org.apache.iotdb.db.wal.io.WALByteBufReader.(WALByteBufReader.java:47)
at
org.apache.iotdb.db.wal.node.WALNode$PlanNodeIterator.hasNext(WALNode.java:552)
at
org.apache.iotdb.db.wal.node.WALNode$PlanNodeIterator.next(WALNode.java:683)
at
org.apache.iotdb.consensus.multileader.logdispatcher.LogDispatcher$LogDispatcherThread.constructBatchFromWAL(LogDispatcher.java:438)
at
org.apache.iotdb.consensus.multileader.logdispatcher.LogDispatcher$LogDispatcherThread.getBatch(LogDispatcher.java:348)
at
org.apache.iotdb.consensus.multileader.logdispatcher.LogDispatcher$LogDispatcherThread.run(LogDispatcher.java:274)
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-10-24 14:18:18,093 [pool-49-IoTDB-LogDispatcher-DataRegion[14]-3] ERROR
o.a.i.d.w.n.WALNode$PlanNodeIterator:590 - Fail to read wal from wal file
/data/liuzhen_test/master_1023_2fea011/sbin/../data/datanode/wal/root.test.g_4-14/_151-204-1.wal,
skip this file.
java.nio.channels.ClosedByInterruptException: null
at
java.nio.channels.spi.AbstractInterruptibleChannel.end(AbstractInterruptibleChannel.java:202)
at sun.nio.ch.FileChannelImpl.size(FileChannelImpl.java:315)
at
org.apache.iotdb.db.wal.io.WALByteBufReader.(WALByteBufReader.java:47)
at
org.apache.iotdb.db.wal.node.WALNode$PlanNodeIterator.hasNext(WALNode.java:552)
at
org.apache.iotdb.db.wal.node.WALNode$PlanNodeIterator.hasNext(WALNode.java:597)
at
org.apache.iotdb.db.wal.node.WALNode$PlanNodeIterator.next(WALNode.java:683)
at
org.apache.iotdb.consensus.multileader.logdispatcher.LogDispatcher$LogDispatcherThread.constructBatchFromWAL(LogDispatcher.java:438)
at
org.apache.iotdb.consensus.multileader.logdispatcher.LogDispatcher$LogDispatcherThread.getBatch(LogDispatcher.java:348)
at
org.apache.iotdb.consensus.multileader.logdispatcher.LogDispatcher$LogDispatcherThread.run(LogDispatcher.java:274)
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-10-24 14:18:18,093 [pool-49-IoTDB-LogDispatcher-DataRegion[14]-3] ERROR
o.a.i.c.m.l.LogDispatcher$LogDispatcherThread:294 - Unexpected error in
logDispatcher for peer Peer{groupId=DataRegion[14],
endpoint=TEndPoint(ip:192.168.10.64, port:40010), nodeId=6}
java.lang.ArrayIndexOutOfBoundsException: 29
at
org.apache.iotdb.db.wal.node.WALNode$PlanNodeIterator.hasNext(WALNode.java:530)
at
org.apache.iotdb.db.wal.node.WALNode$PlanNodeIterator.hasNext(WALNode.java:597)
at
org.apache.iotdb.db.wal.node.WALNode$PlanNodeIterator.hasNext(WALNode.java:597)
at
org.apache.iotdb.db.wal.node.WALNode$PlanNodeIterator.next(WALNode.java:683)
at
org.apache.iotdb.consensus.multileader.logdispatcher.LogDispatcher$LogDispatcherThread.constructBatchFromWAL(LogDispatcher.java:438)
at
org.apache.iotdb.consensus.multileader.logdispatcher.LogDispatcher$LogDispatcherThread.getBatch(LogDispatcher.java:348)
at
org.apache.iotdb.consensus.multileader.logdispatcher.LogDispatcher$LogDispatcherThread.run(LogDispatcher.java:274)
[jira] [Created] (IOTDB-4732) Object has already been returned to this pool or is invalid error in CI
Yuan Tian created IOTDB-4732: Summary: Object has already been returned to this pool or is invalid error in CI Key: IOTDB-4732 URL: https://issues.apache.org/jira/browse/IOTDB-4732 Project: Apache IoTDB Issue Type: Bug Reporter: Yuan Tian Assignee: Yongzao Dan Attachments: image-2022-10-24-15-14-01-894.png There are a lot of error logs like the following while running CI. !image-2022-10-24-15-14-01-894.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-4731) [ remove
刘珍 created IOTDB-4731: - Summary: [ remove Key: IOTDB-4731 URL: https://issues.apache.org/jira/browse/IOTDB-4731 Project: Apache IoTDB Issue Type: Bug Reporter: 刘珍 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-4730) [deleteStorageGroups]failed with 500 when contains empty string
changxue created IOTDB-4730: --- Summary: [deleteStorageGroups]failed with 500 when contains empty string Key: IOTDB-4730 URL: https://issues.apache.org/jira/browse/IOTDB-4730 Project: Apache IoTDB Issue Type: Bug Components: Client/Java Affects Versions: 0.14.0-SNAPSHOT Reporter: changxue Assignee: Haonan Hou Attachments: image-2022-10-24-10-42-56-262.png [deleteStorageGroups]failed with 500 when contains empty string environment: 3C3D cluster detail: 将一个空字符串 和 4个正常storage group 构成的 array list, 作为参数传入deleteStorageGroups, 执行后，如下： !image-2022-10-24-10-42-56-262.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
