[jira] [Created] (IOTDB-2927) [Metric] remove useless metric related dependency.
张洪胤 created IOTDB-2927: -- Summary: [Metric] remove useless metric related dependency. Key: IOTDB-2927 URL: https://issues.apache.org/jira/browse/IOTDB-2927 Project: Apache IoTDB Issue Type: Improvement Reporter: 张洪胤 Assignee: 张洪胤 Remove useless metric related dependency. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (IOTDB-2926) [Doc] finish the diagram of some operations.
张洪胤 created IOTDB-2926: -- Summary: [Doc] finish the diagram of some operations. Key: IOTDB-2926 URL: https://issues.apache.org/jira/browse/IOTDB-2926 Project: Apache IoTDB Issue Type: Improvement Reporter: 张洪胤 Assignee: 张洪胤 Finish the diagram of some operations: set storage group and create timeseries. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (IOTDB-2925) Sketch tool of SchemaFile
Jialin Qiao created IOTDB-2925: -- Summary: Sketch tool of SchemaFile Key: IOTDB-2925 URL: https://issues.apache.org/jira/browse/IOTDB-2925 Project: Apache IoTDB Issue Type: New Feature Reporter: Jialin Qiao Assignee: ZhaoXin A tool to visualize schema file. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (IOTDB-2924) UDF Framework: index overflow while iterating sliding windows
[ https://issues.apache.org/jira/browse/IOTDB-2924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Yurong Su reassigned IOTDB-2924: -- Sprint: 2022-4-Su Assignee: Steve Yurong Su > UDF Framework: index overflow while iterating sliding windows > - > > Key: IOTDB-2924 > URL: https://issues.apache.org/jira/browse/IOTDB-2924 > Project: Apache IoTDB > Issue Type: Bug >Reporter: Steve Yurong Su >Assignee: Steve Yurong Su >Priority: Major > > 2022-04-14 09:37:58,757 [pool-43-IoTDB-RPC-Client-2] WARN > o.a.i.d.u.ErrorHandlingUtils:61 - Status code: INTERNAL_SERVER_ERROR(500), > operation: "select sample((`"PI.u_s"`),'method'='isometric','k'='500') from > root.zoujm.d30344 where Time >= 0". executeStatement failed > java.util.concurrent.ExecutionException: java.lang.IndexOutOfBoundsException: > Index: 19884, Size: 1 > at java.util.concurrent.FutureTask.report(FutureTask.java:122) > at java.util.concurrent.FutureTask.get(FutureTask.java:192) > at > org.apache.iotdb.db.service.thrift.impl.TSServiceImpl.submitQueryTask(TSServiceImpl.java:785) > at > org.apache.iotdb.db.service.thrift.impl.TSServiceImpl.executeStatement(TSServiceImpl.java:619) > at > org.apache.iotdb.service.rpc.thrift.TSIService$Processor$executeStatement.getResult(TSIService.java:2853) > at > org.apache.iotdb.service.rpc.thrift.TSIService$Processor$executeStatement.getResult(TSIService.java:2833) > 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:1142) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.lang.IndexOutOfBoundsException: Index: 19884, Size: 1 > at java.util.ArrayList.rangeCheck(ArrayList.java:653) > at java.util.ArrayList.get(ArrayList.java:429) > at > org.apache.iotdb.db.query.udf.datastructure.tv.ElasticSerializableTVList$LRUCache.get(ElasticSerializableTVList.java:365) > at > org.apache.iotdb.db.query.udf.datastructure.tv.ElasticSerializableTVList.getTime(ElasticSerializableTVList.java:117) > at > org.apache.iotdb.db.query.udf.core.layer.SingleInputColumnSingleReferenceIntermediateLayer$2.next(SingleInputColumnSingleReferenceIntermediateLayer.java:151) > at > org.apache.iotdb.db.query.udf.core.transformer.UDFQueryRowWindowTransformer.executeUDFOnce(UDFQueryRowWindowTransformer.java:40) > at > org.apache.iotdb.db.query.udf.core.transformer.UDFQueryTransformer.cacheValue(UDFQueryTransformer.java:54) > at > org.apache.iotdb.db.query.udf.core.transformer.Transformer.next(Transformer.java:49) > at > org.apache.iotdb.db.query.dataset.UDTFAlignByTimeDataSet.iterateReaderToNextValid(UDTFAlignByTimeDataSet.java:348) > at > org.apache.iotdb.db.query.dataset.UDTFAlignByTimeDataSet.fillBuffer(UDTFAlignByTimeDataSet.java:216) > at > org.apache.iotdb.db.service.thrift.impl.TSServiceImpl.fillRpcReturnData(TSServiceImpl.java:1020) > at > org.apache.iotdb.db.service.thrift.impl.TSServiceImpl.executeQueryPlan(TSServiceImpl.java:841) > at > org.apache.iotdb.db.service.thrift.impl.TSServiceImpl.access$000(TSServiceImpl.java:163) > at > org.apache.iotdb.db.service.thrift.impl.TSServiceImpl$QueryTask.call(TSServiceImpl.java:221) > at > org.apache.iotdb.db.service.thrift.impl.TSServiceImpl$QueryTask.call(TSServiceImpl.java:165) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > ... 3 common frames omitted -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (IOTDB-2924) UDF Framework: index overflow while iterating sliding windows
Steve Yurong Su created IOTDB-2924: -- Summary: UDF Framework: index overflow while iterating sliding windows Key: IOTDB-2924 URL: https://issues.apache.org/jira/browse/IOTDB-2924 Project: Apache IoTDB Issue Type: Bug Reporter: Steve Yurong Su 2022-04-14 09:37:58,757 [pool-43-IoTDB-RPC-Client-2] WARN o.a.i.d.u.ErrorHandlingUtils:61 - Status code: INTERNAL_SERVER_ERROR(500), operation: "select sample((`"PI.u_s"`),'method'='isometric','k'='500') from root.zoujm.d30344 where Time >= 0". executeStatement failed java.util.concurrent.ExecutionException: java.lang.IndexOutOfBoundsException: Index: 19884, Size: 1 at java.util.concurrent.FutureTask.report(FutureTask.java:122) at java.util.concurrent.FutureTask.get(FutureTask.java:192) at org.apache.iotdb.db.service.thrift.impl.TSServiceImpl.submitQueryTask(TSServiceImpl.java:785) at org.apache.iotdb.db.service.thrift.impl.TSServiceImpl.executeStatement(TSServiceImpl.java:619) at org.apache.iotdb.service.rpc.thrift.TSIService$Processor$executeStatement.getResult(TSIService.java:2853) at org.apache.iotdb.service.rpc.thrift.TSIService$Processor$executeStatement.getResult(TSIService.java:2833) 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:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Caused by: java.lang.IndexOutOfBoundsException: Index: 19884, Size: 1 at java.util.ArrayList.rangeCheck(ArrayList.java:653) at java.util.ArrayList.get(ArrayList.java:429) at org.apache.iotdb.db.query.udf.datastructure.tv.ElasticSerializableTVList$LRUCache.get(ElasticSerializableTVList.java:365) at org.apache.iotdb.db.query.udf.datastructure.tv.ElasticSerializableTVList.getTime(ElasticSerializableTVList.java:117) at org.apache.iotdb.db.query.udf.core.layer.SingleInputColumnSingleReferenceIntermediateLayer$2.next(SingleInputColumnSingleReferenceIntermediateLayer.java:151) at org.apache.iotdb.db.query.udf.core.transformer.UDFQueryRowWindowTransformer.executeUDFOnce(UDFQueryRowWindowTransformer.java:40) at org.apache.iotdb.db.query.udf.core.transformer.UDFQueryTransformer.cacheValue(UDFQueryTransformer.java:54) at org.apache.iotdb.db.query.udf.core.transformer.Transformer.next(Transformer.java:49) at org.apache.iotdb.db.query.dataset.UDTFAlignByTimeDataSet.iterateReaderToNextValid(UDTFAlignByTimeDataSet.java:348) at org.apache.iotdb.db.query.dataset.UDTFAlignByTimeDataSet.fillBuffer(UDTFAlignByTimeDataSet.java:216) at org.apache.iotdb.db.service.thrift.impl.TSServiceImpl.fillRpcReturnData(TSServiceImpl.java:1020) at org.apache.iotdb.db.service.thrift.impl.TSServiceImpl.executeQueryPlan(TSServiceImpl.java:841) at org.apache.iotdb.db.service.thrift.impl.TSServiceImpl.access$000(TSServiceImpl.java:163) at org.apache.iotdb.db.service.thrift.impl.TSServiceImpl$QueryTask.call(TSServiceImpl.java:221) at org.apache.iotdb.db.service.thrift.impl.TSServiceImpl$QueryTask.call(TSServiceImpl.java:165) at java.util.concurrent.FutureTask.run(FutureTask.java:266) ... 3 common frames omitted -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (IOTDB-2923) fix CI IoTDBSyncReceiverIT.testReceiveDataAndLoad
yanze chen created IOTDB-2923: - Summary: fix CI IoTDBSyncReceiverIT.testReceiveDataAndLoad Key: IOTDB-2923 URL: https://issues.apache.org/jira/browse/IOTDB-2923 Project: Apache IoTDB Issue Type: Bug Components: Tools/Sync Reporter: yanze chen Assignee: yanze chen -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (IOTDB-2922) Null pointer exception occurs in compaction
Liuxuxin created IOTDB-2922: --- Summary: Null pointer exception occurs in compaction Key: IOTDB-2922 URL: https://issues.apache.org/jira/browse/IOTDB-2922 Project: Apache IoTDB Issue Type: Bug Reporter: Liuxuxin Assignee: Liuxuxin Fix For: 0.14.0 Attachments: image-2022-04-14-18-52-36-274.png !image-2022-04-14-18-52-36-274.png! -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (IOTDB-2921) WALNodeTest is unstable because of list concurrent updating
Eric Pai created IOTDB-2921:
---
Summary: WALNodeTest is unstable because of list concurrent
updating
Key: IOTDB-2921
URL: https://issues.apache.org/jira/browse/IOTDB-2921
Project: Apache IoTDB
Issue Type: Bug
Components: Core/WAL
Reporter: Eric Pai
Assignee: Eric Pai
Fix For: master branch
See the error of tests
{code:java}
(17:20:08) [INFO] Running org.apache.iotdb.db.wal.node.WALNodeTest
(17:20:10) [ERROR] Tests run: 3, Failures: 0, Errors: 1, Skipped: 0, Time
elapsed: 2.624 s <<< FAILURE! - in org.apache.iotdb.db.wal.node.WALNodeTest
(17:20:10) [ERROR]
testConcurrentWrite(org.apache.iotdb.db.wal.node.WALNodeTest) Time elapsed:
2.051 s <<< ERROR!
(17:20:10) java.lang.NullPointerException
(17:20:10) at
org.apache.iotdb.db.wal.node.WALNodeTest.testConcurrentWrite(WALNodeTest.java:126)
{code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (IOTDB-2920) Need to develop an assistance tool to print schema_file.pst file data
xiaozhihong created IOTDB-2920: -- Summary: Need to develop an assistance tool to print schema_file.pst file data Key: IOTDB-2920 URL: https://issues.apache.org/jira/browse/IOTDB-2920 Project: Apache IoTDB Issue Type: New Feature Components: Core/Schema Manager Reporter: xiaozhihong Assignee: Yukun Zhou After the persistence is turned on, the schema_file.pst is generated, and the data cannot be viewed at present. It needs to be viewed with the help of auxiliary tools. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (IOTDB-2919) Delete storage group
Chao Wang created IOTDB-2919: Summary: Delete storage group Key: IOTDB-2919 URL: https://issues.apache.org/jira/browse/IOTDB-2919 Project: Apache IoTDB Issue Type: Improvement Components: Core/Cluster Reporter: Chao Wang Assignee: LuMing confignode manage delete storage group in new cluster. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (IOTDB-2918) [ wal_buffer_queue_capacity ] Default Settings
刘珍 created IOTDB-2918: - Summary: [ wal_buffer_queue_capacity ] Default Settings Key: IOTDB-2918 URL: https://issues.apache.org/jira/browse/IOTDB-2918 Project: Apache IoTDB Issue Type: Improvement Components: Core/WAL Reporter: 刘珍 Assignee: Haiming Zhu Attachments: image-2022-04-14-17-01-03-201.png master 9e1a508be4d335d9ccac6f90b7c568bc5c5fe182 问题描述： wal_buffer_queue_capacity现在的默认值是1（这个参数应该在iotdb-engine.properties可见，目前不可见），私有云长测配置，async模式fsync_wal_delay_in_ms=10，会有很多system rejected（failOperation=942，总operation是5,314,940），wal_buffer_queue_capacity为1000，system rejected减少，failOperation=5，但是对async 普通序列的写入性能影响大，比1慢约1倍。 这个参数的默认值，需要重新考虑。 !image-2022-04-14-17-01-03-201.png! -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (IOTDB-2915) MLogTxtWriter error while parsing CreateAlignedTimeseriesPlan
[ https://issues.apache.org/jira/browse/IOTDB-2915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17522154#comment-17522154 ] ZhaoXin commented on IOTDB-2915: To rel/0.13 https://github.com/apache/iotdb/pull/5533 > MLogTxtWriter error while parsing CreateAlignedTimeseriesPlan > - > > Key: IOTDB-2915 > URL: https://issues.apache.org/jira/browse/IOTDB-2915 > Project: Apache IoTDB > Issue Type: Improvement >Reporter: Yukun Zhou >Assignee: Yukun Zhou >Priority: Major > Labels: pull-request-available > Fix For: master branch, 0.14.0-SNAPSHOT > > > MLogTxtWriter will serialize wrong plan name and schema while paring > CreateAlignedTimeseriesPlan -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (IOTDB-2917) [ flush ] Wal one node has one RESIDUAL WAL file
刘珍 created IOTDB-2917: - Summary: [ flush ] Wal one node has one RESIDUAL WAL file Key: IOTDB-2917 URL: https://issues.apache.org/jira/browse/IOTDB-2917 Project: Apache IoTDB Issue Type: Bug Components: Core/WAL Affects Versions: 0.14.0-SNAPSHOT Reporter: 刘珍 Assignee: Haiming Zhu Attachments: general.properties, image-2022-04-14-15-45-44-815.png, iotdb-engine.properties.async10ms, stop_db.sh master 9e1a508be4d335d9ccac6f90b7c568bc5c5fe182 问题描述 手动flush，wal 有1个node下 残留1个wal文件（非空） 测试环境 1. 私有云机器，长测配置 benchmark运行完之后，手动执行flush，备份data ，system ，wal。 查看wal下，node 1有1个残留wal文件。 172.20.70.2 是iotdb机器， 数据备份 /data/iotdb_data/wal_buffer_queue_capacity-default-1 下的bk_2022-04-12_17_45_12_async10ms_general !image-2022-04-14-15-45-44-815.png! benchmark机器是172.20.70.16，在/data/benchmark/bm_20220322。 2. 数据库配置文件 benchmark配置文件见附件。 [^iotdb-engine.properties.sync10ms] -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (IOTDB-2916) After enabling persistence, the enabling parameters are not written in system.properties
[
https://issues.apache.org/jira/browse/IOTDB-2916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
xiaozhihong reassigned IOTDB-2916:
--
Assignee: Yukun Zhou
> After enabling persistence, the enabling parameters are not written in
> system.properties
>
>
> Key: IOTDB-2916
> URL: https://issues.apache.org/jira/browse/IOTDB-2916
> Project: Apache IoTDB
> Issue Type: Bug
> Components: Core/Schema Manager
>Affects Versions: master branch
>Reporter: xiaozhihong
>Assignee: Yukun Zhou
>Priority: Major
>
> Step 1:In iotdb-engine.properties, change schema_engine_mode from Memory to
> Schema_File
> {code:java}
>
> ### Schema Engine Configuration
>
> # Choose the mode of schema engine. The value could be Memory,Schema_File and
> Rocksdb_based. If the provided value doesn't match any pre-defined value,
> Memory mode will be used as default.
> # Datatype: string
> schema_engine_mode=Schema_File
> {code}
> Step 2: start iotdb
> Step 3:
> {code:java}
> cd data/system/schema/
> cat system.properties{code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (IOTDB-2916) After enabling persistence, the enabling parameters are not written in system.properties
xiaozhihong created IOTDB-2916:
--
Summary: After enabling persistence, the enabling parameters are
not written in system.properties
Key: IOTDB-2916
URL: https://issues.apache.org/jira/browse/IOTDB-2916
Project: Apache IoTDB
Issue Type: Bug
Components: Core/Schema Manager
Affects Versions: master branch
Reporter: xiaozhihong
Step 1:In iotdb-engine.properties, change schema_engine_mode from Memory to
Schema_File
{code:java}
### Schema Engine Configuration
# Choose the mode of schema engine. The value could be Memory,Schema_File and
Rocksdb_based. If the provided value doesn't match any pre-defined value,
Memory mode will be used as default.
# Datatype: string
schema_engine_mode=Schema_File
{code}
Step 2: start iotdb
Step 3:
{code:java}
cd data/system/schema/
cat system.properties{code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Assigned] (IOTDB-2913) Add InfluxDB Protocol Test
[ https://issues.apache.org/jira/browse/IOTDB-2913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haonan Hou reassigned IOTDB-2913: - Assignee: Liu Wei > Add InfluxDB Protocol Test > -- > > Key: IOTDB-2913 > URL: https://issues.apache.org/jira/browse/IOTDB-2913 > Project: Apache IoTDB > Issue Type: Task >Reporter: xieqijun >Assignee: Liu Wei >Priority: Major > > Currently, because the server turns off InfluxDB server by default, the test > of InfluxDB-Protocol module has been skipped. So we need to complete the > following work: > # build new docker-influxdb image, this image will open InfluxDB server. > # don't skip influxdb test in influxdb-protocol.yam by maven command line > mode > > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (IOTDB-2915) MLogTxtWriter error while parsing CreateAlignedTimeseriesPlan
[ https://issues.apache.org/jira/browse/IOTDB-2915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17522076#comment-17522076 ] Jialin Qiao commented on IOTDB-2915: https://github.com/apache/iotdb/pull/5525 > MLogTxtWriter error while parsing CreateAlignedTimeseriesPlan > - > > Key: IOTDB-2915 > URL: https://issues.apache.org/jira/browse/IOTDB-2915 > Project: Apache IoTDB > Issue Type: Improvement >Reporter: Yukun Zhou >Assignee: Yukun Zhou >Priority: Major > Fix For: master branch, 0.14.0-SNAPSHOT > > > MLogTxtWriter will serialize wrong plan name and schema while paring > CreateAlignedTimeseriesPlan -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (IOTDB-2915) MLogTxtWriter error while parsing CreateAlignedTimeseriesPlan
Yukun Zhou created IOTDB-2915: - Summary: MLogTxtWriter error while parsing CreateAlignedTimeseriesPlan Key: IOTDB-2915 URL: https://issues.apache.org/jira/browse/IOTDB-2915 Project: Apache IoTDB Issue Type: Improvement Reporter: Yukun Zhou Assignee: Yukun Zhou Fix For: master branch, 0.14.0-SNAPSHOT MLogTxtWriter will serialize wrong plan name and schema while paring CreateAlignedTimeseriesPlan -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (IOTDB-2914) NPE of MLog force during killing system
Yukun Zhou created IOTDB-2914: - Summary: NPE of MLog force during killing system Key: IOTDB-2914 URL: https://issues.apache.org/jira/browse/IOTDB-2914 Project: Apache IoTDB Issue Type: Improvement Reporter: Yukun Zhou Assignee: Yukun Zhou Fix For: master branch, 0.14.0-SNAPSHOT ### Problem When kill system, the hook will be invoke before killing the mlog force thread and the npe was produced when the thread invoke a cleared schemaRegion ### Solution Shutdown the thread in hook before region clear. -- This message was sent by Atlassian Jira (v8.20.1#820001)
