[jira] [Commented] (IOTDB-5441) [session]insert data failed to timeseries using aligned template when the data schema is more than template define, MetadataException: nullnull
[
https://issues.apache.org/jira/browse/IOTDB-5441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17682366#comment-17682366
]
changxue commented on IOTDB-5441:
-
The same error occurred on non aligned template and timeseries.
> [session]insert data failed to timeseries using aligned template when the
> data schema is more than template define, MetadataException: nullnull
> ---
>
> Key: IOTDB-5441
> URL: https://issues.apache.org/jira/browse/IOTDB-5441
> Project: Apache IoTDB
> Issue Type: Bug
> Components: Client/Java
>Affects Versions: 1.1.0
>Reporter: changxue
>Assignee: Yukun Zhou
>Priority: Major
> Attachments: IOTDB5441.tar.gz
>
>
> build:
> master branch
> commit 315d6526fae06b634e99a4dbe0e3a3127163c8f1
> Date: Sun Jan 29 23:58:36 2023 +0800
> Use gitbox to accelerate the picture loading (#8918)
> reproduction:
> 1. start a standalone service with default config
> 2. execute the java test ng codes . notice this method of
> testUpdateAfterAddTS_alignedTemp
> notice:
> the inserting data schema is more than template defied: appendFloat
> datanode error log:
> {code}
> 2023-01-30 17:56:39,584 [1@group-000200C6-LeaderElection13] INFO
> o.a.r.s.r.s.SegmentedRaftLogWorker:452 -
> 1@group-000200C6-SegmentedRaftLogWorker: Starting segment from index:0
> 2023-01-30 17:56:39,587 [1@group-000200C6-LeaderElection13] INFO
> o.a.r.s.impl.ServerState:430 - 1@group-000200C6: set configuration 0:
> peers:[1|rpc:127.0.0.1:10750|admin:|client:|dataStream:|priority:0|startupRole:FOLLOWER]|listeners:[],
> old=null
> 2023-01-30 17:56:39,588 [1@group-000200C6-SegmentedRaftLogWorker] INFO
> o.a.r.s.r.s.SegmentedRaftLogWorker$StartLogSegment:656 -
> 1@group-000200C6-SegmentedRaftLogWorker: created new log segment
> /Users/changxue/work/soft/apache-iotdb-1.1.0-SNAPSHOT-all-bin/sbin/./../data/datanode/consensus/schema_region/47474747-4747-4747-4747-000200c6/current/log_inprogress_0
>
> 2023-01-30 17:56:39,722
> [pool-25-IoTDB-ClientRPC-Processor-8$20230130_080023_01035_1.1.0] INFO
> o.a.i.d.e.s.TsFileProcessor:193 - create a new tsfile processor
> /Users/changxue/work/soft/apache-iotdb-1.1.0-SNAPSHOT-all-bin/sbin/./../data/datanode/data/sequence/root.blendAddTS/197/2759/1675072599720-1-0-0.tsfile
>
> 2023-01-30 17:56:39,821 [Query-Worker-Thread-1$20230130_080023_01041_1.1.0.0]
> ERROR o.a.i.d.m.e.o.s.SchemaFetchScanOperator:92 - Error occurred during
> execute SchemaFetchOperator 3
> org.apache.iotdb.commons.exception.MetadataException: nullnull
> at
> org.apache.iotdb.db.metadata.mtree.traverser.Traverser.traverse(Traverser.java:95)
> at
> org.apache.iotdb.db.metadata.mtree.MTreeBelowSGMemoryImpl.fetchSchema(MTreeBelowSGMemoryImpl.java:648)
> at
> org.apache.iotdb.db.metadata.schemaregion.SchemaRegionMemoryImpl.fetchSchema(SchemaRegionMemoryImpl.java:841)
> at
> org.apache.iotdb.db.mpp.execution.operator.schema.SchemaFetchScanOperator.fetchSchema(SchemaFetchScanOperator.java:116)
> at
> org.apache.iotdb.db.mpp.execution.operator.schema.SchemaFetchScanOperator.next(SchemaFetchScanOperator.java:90)
> at
> org.apache.iotdb.db.mpp.execution.operator.Operator.nextWithTimer(Operator.java:46)
> at
> org.apache.iotdb.db.mpp.execution.operator.schema.SchemaFetchMergeOperator.next(SchemaFetchMergeOperator.java:76)
> at
> org.apache.iotdb.db.mpp.execution.operator.Operator.nextWithTimer(Operator.java:46)
> at
> org.apache.iotdb.db.mpp.execution.driver.Driver.processInternal(Driver.java:204)
> at
> org.apache.iotdb.db.mpp.execution.driver.Driver.lambda$processFor$1(Driver.java:136)
> at
> org.apache.iotdb.db.mpp.execution.driver.Driver.tryWithLock(Driver.java:291)
> at
> org.apache.iotdb.db.mpp.execution.driver.Driver.processFor(Driver.java:117)
> at
> org.apache.iotdb.db.mpp.execution.schedule.DriverTaskThread.execute(DriverTaskThread.java:69)
> at
> org.apache.iotdb.db.mpp.execution.schedule.AbstractDriverThread.run(AbstractDriverThread.java:73)
> 2023-01-30 17:56:39,826 [Query-Worker-Thread-1$20230130_080023_01041_1.1.0.0]
> WARN o.a.i.d.m.e.s.AbstractDriverThread:79 - [ExecuteFailed]
> java.lang.RuntimeException:
> org.apache.iotdb.commons.exception.MetadataException: nullnull
> at
> org.apache.iotdb.db.mpp.execution.operator.schema.SchemaFetchScanOperator.next(SchemaFetchScanOperator.java:93)
> at
> org.apache.iotdb.db.mpp.execution.operator.Operator.nextWithTimer(Operator.java:46)
> at
> org.apache.iotdb.db.mpp.execution.operator.schema.SchemaFetchMergeOperator.next(SchemaFetchMergeOperator.java:76)
> at
>
[jira] [Commented] (IOTDB-5441) [session]insert data failed to timeseries using aligned template when the data schema is more than template define, MetadataException: nullnull
[
https://issues.apache.org/jira/browse/IOTDB-5441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17682355#comment-17682355
]
changxue commented on IOTDB-5441:
-
1. 我定义了一个aligned template: aligned_template, 绑定到
root.blendAddTS.alignedUsingTemp
2. insert tablet 成功， schema 与定义的一致
3. 再次insert data，数据结构比定义的多一个 float ，报错。
下列方法我都使用过，代码中有，表现一致：
1. 使用 insertAlignedStringRecordsOfOneDevice
2. 使用 insertAlignedRecord
3. 使用tablet
> [session]insert data failed to timeseries using aligned template when the
> data schema is more than template define, MetadataException: nullnull
> ---
>
> Key: IOTDB-5441
> URL: https://issues.apache.org/jira/browse/IOTDB-5441
> Project: Apache IoTDB
> Issue Type: Bug
> Components: Client/Java
>Affects Versions: 1.1.0
>Reporter: changxue
>Assignee: Yukun Zhou
>Priority: Major
> Attachments: IOTDB5441.tar.gz
>
>
> build:
> master branch
> commit 315d6526fae06b634e99a4dbe0e3a3127163c8f1
> Date: Sun Jan 29 23:58:36 2023 +0800
> Use gitbox to accelerate the picture loading (#8918)
> reproduction:
> 1. start a standalone service with default config
> 2. execute the java test ng codes . notice this method of
> testUpdateAfterAddTS_alignedTemp
> notice:
> the inserting data schema is more than template defied: appendFloat
> datanode error log:
> {code}
> 2023-01-30 17:56:39,584 [1@group-000200C6-LeaderElection13] INFO
> o.a.r.s.r.s.SegmentedRaftLogWorker:452 -
> 1@group-000200C6-SegmentedRaftLogWorker: Starting segment from index:0
> 2023-01-30 17:56:39,587 [1@group-000200C6-LeaderElection13] INFO
> o.a.r.s.impl.ServerState:430 - 1@group-000200C6: set configuration 0:
> peers:[1|rpc:127.0.0.1:10750|admin:|client:|dataStream:|priority:0|startupRole:FOLLOWER]|listeners:[],
> old=null
> 2023-01-30 17:56:39,588 [1@group-000200C6-SegmentedRaftLogWorker] INFO
> o.a.r.s.r.s.SegmentedRaftLogWorker$StartLogSegment:656 -
> 1@group-000200C6-SegmentedRaftLogWorker: created new log segment
> /Users/changxue/work/soft/apache-iotdb-1.1.0-SNAPSHOT-all-bin/sbin/./../data/datanode/consensus/schema_region/47474747-4747-4747-4747-000200c6/current/log_inprogress_0
>
> 2023-01-30 17:56:39,722
> [pool-25-IoTDB-ClientRPC-Processor-8$20230130_080023_01035_1.1.0] INFO
> o.a.i.d.e.s.TsFileProcessor:193 - create a new tsfile processor
> /Users/changxue/work/soft/apache-iotdb-1.1.0-SNAPSHOT-all-bin/sbin/./../data/datanode/data/sequence/root.blendAddTS/197/2759/1675072599720-1-0-0.tsfile
>
> 2023-01-30 17:56:39,821 [Query-Worker-Thread-1$20230130_080023_01041_1.1.0.0]
> ERROR o.a.i.d.m.e.o.s.SchemaFetchScanOperator:92 - Error occurred during
> execute SchemaFetchOperator 3
> org.apache.iotdb.commons.exception.MetadataException: nullnull
> at
> org.apache.iotdb.db.metadata.mtree.traverser.Traverser.traverse(Traverser.java:95)
> at
> org.apache.iotdb.db.metadata.mtree.MTreeBelowSGMemoryImpl.fetchSchema(MTreeBelowSGMemoryImpl.java:648)
> at
> org.apache.iotdb.db.metadata.schemaregion.SchemaRegionMemoryImpl.fetchSchema(SchemaRegionMemoryImpl.java:841)
> at
> org.apache.iotdb.db.mpp.execution.operator.schema.SchemaFetchScanOperator.fetchSchema(SchemaFetchScanOperator.java:116)
> at
> org.apache.iotdb.db.mpp.execution.operator.schema.SchemaFetchScanOperator.next(SchemaFetchScanOperator.java:90)
> at
> org.apache.iotdb.db.mpp.execution.operator.Operator.nextWithTimer(Operator.java:46)
> at
> org.apache.iotdb.db.mpp.execution.operator.schema.SchemaFetchMergeOperator.next(SchemaFetchMergeOperator.java:76)
> at
> org.apache.iotdb.db.mpp.execution.operator.Operator.nextWithTimer(Operator.java:46)
> at
> org.apache.iotdb.db.mpp.execution.driver.Driver.processInternal(Driver.java:204)
> at
> org.apache.iotdb.db.mpp.execution.driver.Driver.lambda$processFor$1(Driver.java:136)
> at
> org.apache.iotdb.db.mpp.execution.driver.Driver.tryWithLock(Driver.java:291)
> at
> org.apache.iotdb.db.mpp.execution.driver.Driver.processFor(Driver.java:117)
> at
> org.apache.iotdb.db.mpp.execution.schedule.DriverTaskThread.execute(DriverTaskThread.java:69)
> at
> org.apache.iotdb.db.mpp.execution.schedule.AbstractDriverThread.run(AbstractDriverThread.java:73)
> 2023-01-30 17:56:39,826 [Query-Worker-Thread-1$20230130_080023_01041_1.1.0.0]
> WARN o.a.i.d.m.e.s.AbstractDriverThread:79 - [ExecuteFailed]
> java.lang.RuntimeException:
> org.apache.iotdb.commons.exception.MetadataException: nullnull
> at
> org.apache.iotdb.db.mpp.execution.operator.schema.SchemaFetchScanOperator.next(SchemaFetchScanOperator.java:93)
> at
>
[jira] [Created] (IOTDB-5444) [1.0] Cannot deserialize CreateTimeSeriesNode
ZhangZhengming created IOTDB-5444:
-
Summary: [1.0] Cannot deserialize CreateTimeSeriesNode
Key: IOTDB-5444
URL: https://issues.apache.org/jira/browse/IOTDB-5444
Project: Apache IoTDB
Issue Type: Bug
Affects Versions: 1.1.0
Reporter: ZhangZhengming
Assignee: Yukun Zhou
Attachments: image-2023-01-31-10-10-53-252.png,
image-2023-01-31-10-12-12-898.png, image-2023-01-31-10-13-01-418.png,
image-2023-01-31-10-14-56-914.png
I start iotdb cluster of 1C3D use the default configuration.
* {color:#172b4d}node1: confignode + datanode-1 {color}
* {color:#172b4d}node2: datanode-2{color}
* {color:#172b4d}node3: datanode-3{color}
execute sql statement in {color:#de350b}node-2{color} or
{color:#de350b}node-3{color}:
{code:java}
create timeseries root.szg.d1.`1S` with datatype=BOOLEAN,encoding=PLAIN" {code}
report error:
!image-2023-01-31-10-10-53-252.png|width=990,height=59!
error log in {color:#de350b}node-2 {color:#172b4d}or{color} node-3{color}:
!image-2023-01-31-10-12-12-898.png|width=2295,height=1070!
error log in node-1:
!image-2023-01-31-10-13-01-418.png|width=1668,height=422!
execute sql statement in {color:#de350b}node-1{color} was succeed.
!image-2023-01-31-10-14-56-914.png|width=1020,height=53!
iotdb version:
version 1.1.0-SNAPSHOT (Build: c130222)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IOTDB-5443) CHIMP encoding
Haonan Hou created IOTDB-5443: - Summary: CHIMP encoding Key: IOTDB-5443 URL: https://issues.apache.org/jira/browse/IOTDB-5443 Project: Apache IoTDB Issue Type: New Feature Reporter: Haonan Hou Chimp was presented in VLDB 2022 ([https://www.vldb.org/pvldb/vol15/p3058-liakos.pdf]). Implement it in IoTDB -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5442) Standardising the use of CachedMTreeStore read/write locks
yanze chen created IOTDB-5442: - Summary: Standardising the use of CachedMTreeStore read/write locks Key: IOTDB-5442 URL: https://issues.apache.org/jira/browse/IOTDB-5442 Project: Apache IoTDB Issue Type: Improvement Reporter: yanze chen Assignee: yanze chen https://apache-iotdb.feishu.cn/docx/WwdAd6SYLofsAHxEJeRcDuWBnPh -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5441) [session]insert data to a using template timeseries when the
changxue created IOTDB-5441:
---
Summary: [session]insert data to a using template timeseries when
the
Key: IOTDB-5441
URL: https://issues.apache.org/jira/browse/IOTDB-5441
Project: Apache IoTDB
Issue Type: Bug
Components: Client/Java
Affects Versions: 1.1.0
Reporter: changxue
Assignee: Yukun Zhou
Attachments: TestBlendScenarioAddTS.java
build:
master branch
commit 315d6526fae06b634e99a4dbe0e3a3127163c8f1
Date: Sun Jan 29 23:58:36 2023 +0800
Use gitbox to accelerate the picture loading (#8918)
reproduction:
1. start a standalone service with default config
2. execute the java test ng codes . notice this method of
testUpdateAfterAddTS_alignedTemp
datanode error log:
{code}
2023-01-30 17:56:39,584 [1@group-000200C6-LeaderElection13] INFO
o.a.r.s.r.s.SegmentedRaftLogWorker:452 -
1@group-000200C6-SegmentedRaftLogWorker: Starting segment from index:0
2023-01-30 17:56:39,587 [1@group-000200C6-LeaderElection13] INFO
o.a.r.s.impl.ServerState:430 - 1@group-000200C6: set configuration 0:
peers:[1|rpc:127.0.0.1:10750|admin:|client:|dataStream:|priority:0|startupRole:FOLLOWER]|listeners:[],
old=null
2023-01-30 17:56:39,588 [1@group-000200C6-SegmentedRaftLogWorker] INFO
o.a.r.s.r.s.SegmentedRaftLogWorker$StartLogSegment:656 -
1@group-000200C6-SegmentedRaftLogWorker: created new log segment
/Users/changxue/work/soft/apache-iotdb-1.1.0-SNAPSHOT-all-bin/sbin/./../data/datanode/consensus/schema_region/47474747-4747-4747-4747-000200c6/current/log_inprogress_0
2023-01-30 17:56:39,722
[pool-25-IoTDB-ClientRPC-Processor-8$20230130_080023_01035_1.1.0] INFO
o.a.i.d.e.s.TsFileProcessor:193 - create a new tsfile processor
/Users/changxue/work/soft/apache-iotdb-1.1.0-SNAPSHOT-all-bin/sbin/./../data/datanode/data/sequence/root.blendAddTS/197/2759/1675072599720-1-0-0.tsfile
2023-01-30 17:56:39,821 [Query-Worker-Thread-1$20230130_080023_01041_1.1.0.0]
ERROR o.a.i.d.m.e.o.s.SchemaFetchScanOperator:92 - Error occurred during
execute SchemaFetchOperator 3
org.apache.iotdb.commons.exception.MetadataException: nullnull
at
org.apache.iotdb.db.metadata.mtree.traverser.Traverser.traverse(Traverser.java:95)
at
org.apache.iotdb.db.metadata.mtree.MTreeBelowSGMemoryImpl.fetchSchema(MTreeBelowSGMemoryImpl.java:648)
at
org.apache.iotdb.db.metadata.schemaregion.SchemaRegionMemoryImpl.fetchSchema(SchemaRegionMemoryImpl.java:841)
at
org.apache.iotdb.db.mpp.execution.operator.schema.SchemaFetchScanOperator.fetchSchema(SchemaFetchScanOperator.java:116)
at
org.apache.iotdb.db.mpp.execution.operator.schema.SchemaFetchScanOperator.next(SchemaFetchScanOperator.java:90)
at
org.apache.iotdb.db.mpp.execution.operator.Operator.nextWithTimer(Operator.java:46)
at
org.apache.iotdb.db.mpp.execution.operator.schema.SchemaFetchMergeOperator.next(SchemaFetchMergeOperator.java:76)
at
org.apache.iotdb.db.mpp.execution.operator.Operator.nextWithTimer(Operator.java:46)
at
org.apache.iotdb.db.mpp.execution.driver.Driver.processInternal(Driver.java:204)
at
org.apache.iotdb.db.mpp.execution.driver.Driver.lambda$processFor$1(Driver.java:136)
at
org.apache.iotdb.db.mpp.execution.driver.Driver.tryWithLock(Driver.java:291)
at
org.apache.iotdb.db.mpp.execution.driver.Driver.processFor(Driver.java:117)
at
org.apache.iotdb.db.mpp.execution.schedule.DriverTaskThread.execute(DriverTaskThread.java:69)
at
org.apache.iotdb.db.mpp.execution.schedule.AbstractDriverThread.run(AbstractDriverThread.java:73)
2023-01-30 17:56:39,826 [Query-Worker-Thread-1$20230130_080023_01041_1.1.0.0]
WARN o.a.i.d.m.e.s.AbstractDriverThread:79 - [ExecuteFailed]
java.lang.RuntimeException:
org.apache.iotdb.commons.exception.MetadataException: nullnull
at
org.apache.iotdb.db.mpp.execution.operator.schema.SchemaFetchScanOperator.next(SchemaFetchScanOperator.java:93)
at
org.apache.iotdb.db.mpp.execution.operator.Operator.nextWithTimer(Operator.java:46)
at
org.apache.iotdb.db.mpp.execution.operator.schema.SchemaFetchMergeOperator.next(SchemaFetchMergeOperator.java:76)
at
org.apache.iotdb.db.mpp.execution.operator.Operator.nextWithTimer(Operator.java:46)
at
org.apache.iotdb.db.mpp.execution.driver.Driver.processInternal(Driver.java:204)
at
org.apache.iotdb.db.mpp.execution.driver.Driver.lambda$processFor$1(Driver.java:136)
at
org.apache.iotdb.db.mpp.execution.driver.Driver.tryWithLock(Driver.java:291)
at
org.apache.iotdb.db.mpp.execution.driver.Driver.processFor(Driver.java:117)
at
org.apache.iotdb.db.mpp.execution.schedule.DriverTaskThread.execute(DriverTaskThread.java:69)
at
org.apache.iotdb.db.mpp.execution.schedule.AbstractDriverThread.run(AbstractDriverThread.java:73)
Caused by:
[jira] [Created] (IOTDB-5440) Enable metric and write to IOTDB, then start confignode and datanode with exceptions
xiaozhihong created IOTDB-5440: -- Summary: Enable metric and write to IOTDB, then start confignode and datanode with exceptions Key: IOTDB-5440 URL: https://issues.apache.org/jira/browse/IOTDB-5440 Project: Apache IoTDB Issue Type: Bug Components: mpp-cluster Affects Versions: 1.0.1 Reporter: xiaozhihong Assignee: Gaofei Cao Attachments: conf.zip, image-2023-01-30-18-04-29-195.png, logs.zip V1.0.0 commit : 573097a Enable metric，and write to iotdb, then start confignode and datanode failed. !image-2023-01-30-18-04-29-195.png|width=509,height=219! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IOTDB-5140) Add metrics for compaction deserializing pages or writing chunks
[ https://issues.apache.org/jira/browse/IOTDB-5140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17681995#comment-17681995 ] Jinrui Zhang commented on IOTDB-5140: - PR towards rel/1.0 is not merged > Add metrics for compaction deserializing pages or writing chunks > > > Key: IOTDB-5140 > URL: https://issues.apache.org/jira/browse/IOTDB-5140 > Project: Apache IoTDB > Issue Type: Improvement >Reporter: Liuxuxin >Assignee: Liuxuxin >Priority: Major > Labels: pull-request-available > Original Estimate: 24h > Remaining Estimate: 24h > > We want to trace the count of deserlializing chunk or pages during compaction. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IOTDB-5206) Fix when target file is deleted in Compaction exception handler and recover
[ https://issues.apache.org/jira/browse/IOTDB-5206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17681993#comment-17681993 ] Jinrui Zhang commented on IOTDB-5206: - The fix is approved but not merged because of IT failures > Fix when target file is deleted in Compaction exception handler and recover > --- > > Key: IOTDB-5206 > URL: https://issues.apache.org/jira/browse/IOTDB-5206 > Project: Apache IoTDB > Issue Type: Bug >Affects Versions: master branch, 1.0.0 >Reporter: 周沛辰 >Assignee: 周沛辰 >Priority: Major > Labels: pull-request-available > Original Estimate: 72h > Remaining Estimate: 72h > > *Description* > After compaction, if the target file is empty, its corresponding disk file > will be deleted. If an exception or system interruption occurs, there will be > problems in restart recovery and set allowCompaction to false. > 2022-12-20 09:23:53,086 [pool-12-IoTDB-Recovery-Thread-Pool-1] ERROR > o.a.i.d.e.c.t.CompactionRecoverTask:300 - root.iot-0 > [Compaction][ExceptionHandler] target file > sequence/root.iot/0/0/1670572962795-1051-2-1.inner is not complete, and some > source files is lost, do nothing. Set allowCompaction to false > 2022-12-20 09:23:53,087 [pool-12-IoTDB-Recovery-Thread-Pool-1] ERROR > o.a.i.d.e.c.t.CompactionRecoverTask:133 - root.iot-0 [Compaction][Recover] > Failed to recover compaction, set allowCompaction to false > *Reason* > Empty target files will be deleted in compaction. In recovery, system will > report source files are lost and empty target file has been deleted. > *Solution* > Empty target files are not deleted during the compaction until the end of the > compaction. However, after recovery, the empty target file will not be > deleted, but it will not affect the correctness of the system. -- This message was sent by Atlassian Jira (v8.20.10#820010)
