[jira] [Assigned] (IOTDB-3450) Support new path pattern: 0 or more layers
[
https://issues.apache.org/jira/browse/IOTDB-3450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
huaxin reassigned IOTDB-3450:
-
Assignee: 高希鸣 (was: huaxin)
> Support new path pattern: 0 or more layers
> --
>
> Key: IOTDB-3450
> URL: https://issues.apache.org/jira/browse/IOTDB-3450
> Project: Apache IoTDB
> Issue Type: New Feature
>Reporter: Guanfei Guo
>Assignee: 高希鸣
>Priority: Major
> Fix For: 0.13.1
>
>
> Now IoTDB supports the following path patterns:
> # * (1 asterisk) - one layer
> # ** (2 asterisks) - one or more layers
>
> We need to support a new path pattern: 0 or one or more layers, with the
> following syntax:
> *** (3 asterisks) -{color:#172b4d} 0 or one or more layers{color}
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (IOTDB-3450) Support new path pattern: 0 or more layers
[
https://issues.apache.org/jira/browse/IOTDB-3450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17552576#comment-17552576
]
huaxin commented on IOTDB-3450:
---
I'm doing this
> Support new path pattern: 0 or more layers
> --
>
> Key: IOTDB-3450
> URL: https://issues.apache.org/jira/browse/IOTDB-3450
> Project: Apache IoTDB
> Issue Type: New Feature
>Reporter: Guanfei Guo
>Assignee: huaxin
>Priority: Major
> Fix For: 0.13.1
>
>
> Now IoTDB supports the following path patterns:
> # * (1 asterisk) - one layer
> # ** (2 asterisks) - one or more layers
>
> We need to support a new path pattern: 0 or one or more layers, with the
> following syntax:
> *** (3 asterisks) -{color:#172b4d} 0 or one or more layers{color}
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Assigned] (IOTDB-3450) Support new path pattern: 0 or more layers
[
https://issues.apache.org/jira/browse/IOTDB-3450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
huaxin reassigned IOTDB-3450:
-
Assignee: huaxin
> Support new path pattern: 0 or more layers
> --
>
> Key: IOTDB-3450
> URL: https://issues.apache.org/jira/browse/IOTDB-3450
> Project: Apache IoTDB
> Issue Type: New Feature
>Reporter: Guanfei Guo
>Assignee: huaxin
>Priority: Major
> Fix For: 0.13.1
>
>
> Now IoTDB supports path patterns as follows:
> # * (1 asterisk) - one layer
> # ** (2 asterisks) - one or more layers
>
> We need to support a new path pattern: 0 or one or more layers, with the
> following syntax:
> * (3 asterisks) -{color:#172b4d} ** 0 or one or more layers{color}
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Created] (IOTDB-3450) Support new path pattern: 0 or more layers
Guanfei Guo created IOTDB-3450:
--
Summary: Support new path pattern: 0 or more layers
Key: IOTDB-3450
URL: https://issues.apache.org/jira/browse/IOTDB-3450
Project: Apache IoTDB
Issue Type: New Feature
Reporter: Guanfei Guo
Fix For: 0.13.1
Now IoTDB supports path patterns as follows:
# * (1 asterisk) - one layer
# ** (2 asterisks) - one or more layers
We need to support a new path pattern: 0 or one or more layers, with the
following syntax:
* (3 asterisks) -{color:#172b4d} ** 0 or one or more layers{color}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (IOTDB-3437) Remove RegionReplicaSet in serialization of MPP
[ https://issues.apache.org/jira/browse/IOTDB-3437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17552566#comment-17552566 ] Jinrui Zhang commented on IOTDB-3437: - See this PR: https://github.com/apache/iotdb/pull/6217 > Remove RegionReplicaSet in serialization of MPP > --- > > Key: IOTDB-3437 > URL: https://issues.apache.org/jira/browse/IOTDB-3437 > Project: Apache IoTDB > Issue Type: Bug >Reporter: Jinrui Zhang >Assignee: Jinrui Zhang >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (IOTDB-3449) [ COUNT query ] executeStatement failed. error code: TSStatus(code:411, message:Fragment cannot be dispatched)
刘珍 created IOTDB-3449:
-
Summary: [ COUNT query ] executeStatement failed. error code:
TSStatus(code:411, message:Fragment cannot be dispatched)
Key: IOTDB-3449
URL: https://issues.apache.org/jira/browse/IOTDB-3449
Project: Apache IoTDB
Issue Type: Bug
Components: mpp-cluster
Affects Versions: 0.14.0-SNAPSHOT
Reporter: 刘珍
Assignee: Yuan Tian
Attachments: 101-200.sh, config.properties
master_0610_3766327
3节点3副本（COUNT大写），
select {color:red}COUNT{color}(s_4) from root.**;
Msg: 500: [INTERNAL_SERVER_ERROR(500)] Exception occurred: "select COUNT(s_4)
from root.**". executeStatement failed. error code: TSStatus(code:411,
message:Fragment cannot be dispatched)
2022-06-10 13:50:27,957 [20220610_055027_00087_2.1.0-304] ERROR
o.a.i.d.m.e.f.FragmentInstanceManager:113 - error when create
FragmentInstanceExecution.
org.apache.iotdb.db.exception.sql.StatementAnalyzeException: no data type found
for path: count(root.bm68_dn62.g_0.d116_0.s_4)
at
org.apache.iotdb.db.mpp.plan.analyze.TypeProvider.getType(TypeProvider.java:47)
at
java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:193)
at
java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1384)
at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:482)
at
java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:472)
at
java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:708)
at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
at
java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:499)
at
org.apache.iotdb.db.mpp.plan.planner.LocalExecutionPlanner$Visitor.getOutputColumnTypes(LocalExecutionPlanner.java:1324)
at
org.apache.iotdb.db.mpp.plan.planner.LocalExecutionPlanner$Visitor.visitTimeJoin(LocalExecutionPlanner.java:1010)
at
org.apache.iotdb.db.mpp.plan.planner.LocalExecutionPlanner$Visitor.visitTimeJoin(LocalExecutionPlanner.java:239)
at
org.apache.iotdb.db.mpp.plan.planner.plan.node.process.TimeJoinNode.accept(TimeJoinNode.java:91)
at
org.apache.iotdb.db.mpp.plan.planner.LocalExecutionPlanner$Visitor.visitFragmentSink(LocalExecutionPlanner.java:1070)
at
org.apache.iotdb.db.mpp.plan.planner.LocalExecutionPlanner$Visitor.visitFragmentSink(LocalExecutionPlanner.java:239)
at
org.apache.iotdb.db.mpp.plan.planner.plan.node.sink.FragmentSinkNode.accept(FragmentSinkNode.java:75)
at
org.apache.iotdb.db.mpp.plan.planner.LocalExecutionPlanner.plan(LocalExecutionPlanner.java:211)
at
org.apache.iotdb.db.mpp.execution.fragment.FragmentInstanceManager.lambda$execDataQueryFragmentInstance$1(FragmentInstanceManager.java:104)
at
java.util.concurrent.ConcurrentHashMap.computeIfAbsent(ConcurrentHashMap.java:1660)
at
org.apache.iotdb.db.mpp.execution.fragment.FragmentInstanceManager.execDataQueryFragmentInstance(FragmentInstanceManager.java:90)
at
org.apache.iotdb.db.consensus.statemachine.DataRegionStateMachine.read(DataRegionStateMachine.java:139)
at
org.apache.iotdb.consensus.ratis.ApplicationStateMachineProxy.query(ApplicationStateMachineProxy.java:139)
at
org.apache.ratis.statemachine.impl.BaseStateMachine.queryStale(BaseStateMachine.java:194)
at
org.apache.ratis.server.impl.RaftServerImpl.staleReadAsync(RaftServerImpl.java:881)
at
org.apache.ratis.server.impl.RaftServerImpl.submitClientRequestAsync(RaftServerImpl.java:797)
at
org.apache.ratis.server.impl.RaftServerImpl.submitClientRequest(RaftServerImpl.java:912)
at
org.apache.ratis.server.impl.RaftServerProxy.submitClientRequest(RaftServerProxy.java:431)
at
org.apache.iotdb.consensus.ratis.RatisConsensus.read(RatisConsensus.java:229)
at
org.apache.iotdb.db.service.thrift.impl.InternalServiceImpl.sendFragmentInstance(InternalServiceImpl.java:124)
at
org.apache.iotdb.mpp.rpc.thrift.InternalService$Processor$sendFragmentInstance.getResult(InternalService.java:1265)
at
org.apache.iotdb.mpp.rpc.thrift.InternalService$Processor$sendFragmentInstance.getResult(InternalService.java:1245)
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)
select count(s_4) from root.** ; // 结果正确
select COUNT(s_4) from root.** align by device; // COUNT
[jira] [Assigned] (IOTDB-3408) Snapshot error about MTreeAboveSG
[ https://issues.apache.org/jira/browse/IOTDB-3408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jialin Qiao reassigned IOTDB-3408: -- Assignee: Song Ziyang (was: Yukun Zhou) > Snapshot error about MTreeAboveSG > - > > Key: IOTDB-3408 > URL: https://issues.apache.org/jira/browse/IOTDB-3408 > Project: Apache IoTDB > Issue Type: Bug > Components: mpp-cluster >Affects Versions: 0.14.0-SNAPSHOT >Reporter: 刘珍 >Assignee: Song Ziyang >Priority: Major > Attachments: image-2022-06-07-10-16-17-643.png > > > master_0606_c2afca1 > 3confignode，3datanode，schemaRegion/dataRegion 3副本。 > Restart recovery, the third confignode error ： > 2022-06-07 09:28:37,926 [ForkJoinPool.commonPool-worker-43] ERROR > o.a.i.d.m.m.MTreeAboveSG:564 - Wrong node type. Cannot deserialize > MTreeAboveSG from given buffer > !image-2022-06-07-10-16-17-643.png! > 复现流程 > 1. 192.168.10.62/66/68 72C256G > bm 连ip-62 写数据 > 停止3个datanode，备份数据 > /data/liuzhen_test/master_0606_c2afca1/datanode/data_2022_06_07-08-55-06_for_rec > 停止3个confignode，备份数据/data/liuzhen_test/master_0606_c2afca1/confignode/data_2022_06_07-08-55-39_for_rec > 2. 顺序启动ip-62,66,68 > 只有68的confignode有error > 另：3个datanode启动失败 -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (IOTDB-3448) Migrate the logic of deleteRegion onto the consensus module
Xinyu Tan created IOTDB-3448: Summary: Migrate the logic of deleteRegion onto the consensus module Key: IOTDB-3448 URL: https://issues.apache.org/jira/browse/IOTDB-3448 Project: Apache IoTDB Issue Type: Improvement Reporter: Xinyu Tan Assignee: Xinyu Tan The deletion of a region is used as a raft log to synchronize inside the region. If the underlying state machine fails to recover to the previous state after the restart, NPE problems may occur during the restart. In addition, executing a raft log that removes itself is very strange for the consensus layer because we still end up removing the corresponding region in the consensus layer， which is not done in current implementation So we can move the deleteRegion operation above the consensus layer -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (IOTDB-3442) New Cluster IT will crash
[ https://issues.apache.org/jira/browse/IOTDB-3442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17552544#comment-17552544 ] Jialin Qiao commented on IOTDB-3442: Ratis needs hundred of milliseconds to init its state, so the election timeout should be larger. > New Cluster IT will crash > -- > > Key: IOTDB-3442 > URL: https://issues.apache.org/jira/browse/IOTDB-3442 > Project: Apache IoTDB > Issue Type: Bug >Reporter: Yuan Tian >Assignee: Tian Jiang >Priority: Major > Attachments: IoTDBAlignedSeriesQuery3IT.zip, > image-2022-06-09-21-02-26-617.png, image-2022-06-09-21-02-38-623.png, > image-2022-06-09-21-04-50-129.png > > > 详情见日志，下面是我对日志现象的简单说明： > Datanode14391在 20:41:14 开始向Datanode19031发送创建序列的fragment instance，20秒后（thrift > client的默认链接超时），即20:41:34，超时，CI挂掉。从Datanode19031里的日志可以看出，最后卡在了这一步 > !image-2022-06-09-21-02-26-617.png! > !image-2022-06-09-21-02-38-623.png! -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Assigned] (IOTDB-3418) [ benchmark + 3C3D ] Benchmark process disappears
[ https://issues.apache.org/jira/browse/IOTDB-3418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jialin Qiao reassigned IOTDB-3418: -- Assignee: 张洪胤 (was: Jialin Qiao) > [ benchmark + 3C3D ] Benchmark process disappears > -- > > Key: IOTDB-3418 > URL: https://issues.apache.org/jira/browse/IOTDB-3418 > Project: Apache IoTDB > Issue Type: Bug > Components: mpp-cluster >Affects Versions: 0.14.0-SNAPSHOT >Reporter: 刘珍 >Assignee: 张洪胤 >Priority: Major > Attachments: config.properties.first, ip62_log_all.zip, > ip66_log_all.log > > > master_0607_7cb2d3f > 3confignode ,3datanode ,副本数是3. > benchmark 连接其中1个datanode写数据，2小时后，benchmark进程消失( datanode日志最后的状态2022-06-07 > 13:44:56,814 [pool-7-IoTDB-RPC-Client-48] INFO > o.a.i.d.q.c.SessionManager:150 - Session-111 is closing） > os日志没有Out of memory / killed process 信息 > 再次启动benchmark连接相同的datanode（bm不创建元数据，START_TIME设置大一些，不产生乱序数据），datanode没有任何新的wal生成（第2次bm运行的datanode日志2022-06-07 > 15:49:19,507 [pool-7-IoTDB-RPC-Client-48] INFO > o.a.i.d.s.t.i.DataNodeTSIServiceImpl:174 - IoTDB: Login status: Login > successfully. User : root, opens Session-153） > 测试流程： > 1. 192.168.10.62/66/68 72C256G > 2. benchmark 配置见附件 > 2022-06-07 11:22:51,289 开始测试，2小时22分钟后，bm进程消失 > 2022-06-07 13:44:50,650 （bm最后1条日志） -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Assigned] (IOTDB-3447) Add show and set function with schema template function in python client
[ https://issues.apache.org/jira/browse/IOTDB-3447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lihui Deng reassigned IOTDB-3447: - Assignee: Lihui Deng > Add show and set function with schema template function in python client > > > Key: IOTDB-3447 > URL: https://issues.apache.org/jira/browse/IOTDB-3447 > Project: Apache IoTDB > Issue Type: New Feature >Reporter: Lihui Deng >Assignee: Lihui Deng >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (IOTDB-3447) Add show and set function with schema template function in python client
Lihui Deng created IOTDB-3447: - Summary: Add show and set function with schema template function in python client Key: IOTDB-3447 URL: https://issues.apache.org/jira/browse/IOTDB-3447 Project: Apache IoTDB Issue Type: New Feature Reporter: Lihui Deng -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Assigned] (IOTDB-3351) Imporving python client schema template functions
[ https://issues.apache.org/jira/browse/IOTDB-3351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lihui Deng reassigned IOTDB-3351: - Assignee: Lihui Deng > Imporving python client schema template functions > --- > > Key: IOTDB-3351 > URL: https://issues.apache.org/jira/browse/IOTDB-3351 > Project: Apache IoTDB > Issue Type: New Feature >Reporter: Lihui Deng >Assignee: Lihui Deng >Priority: Major > Labels: pull-request-available > > Finish python client schema template functions： > # create schema template function > # drop schema template function > In this pr, we add template class, subclass MeasurementNode, internalNode, > and a binary serialization method was added. > Add some template example -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Assigned] (IOTDB-3445) Deleting a storage group requires that datanode delete all metadata and meta directories related to the storage group
[ https://issues.apache.org/jira/browse/IOTDB-3445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jialin Qiao reassigned IOTDB-3445: -- Assignee: LuMing > Deleting a storage group requires that datanode delete all metadata and meta > directories related to the storage group > - > > Key: IOTDB-3445 > URL: https://issues.apache.org/jira/browse/IOTDB-3445 > Project: Apache IoTDB > Issue Type: Bug >Reporter: Xinyu Tan >Assignee: LuMing >Priority: Major > Attachments: image-2022-06-10-11-26-26-980.png > > > Currently, however, only files can be deleted, not directories > !image-2022-06-10-11-26-26-980.png! -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Assigned] (IOTDB-3446) Deleting a storage group requires that datanode delete all data and wal files and directories related to the storage group
[ https://issues.apache.org/jira/browse/IOTDB-3446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jialin Qiao reassigned IOTDB-3446: -- Assignee: LuMing > Deleting a storage group requires that datanode delete all data and wal > files and directories related to the storage group > --- > > Key: IOTDB-3446 > URL: https://issues.apache.org/jira/browse/IOTDB-3446 > Project: Apache IoTDB > Issue Type: Bug >Reporter: Xinyu Tan >Assignee: LuMing >Priority: Major > Attachments: image-2022-06-10-11-28-47-233.png > > > !image-2022-06-10-11-28-47-233.png! > Yet none of them have been deleted -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (IOTDB-3446) Deleting a storage group requires that datanode delete all data and wal files and directories related to the storage group
Xinyu Tan created IOTDB-3446: Summary: Deleting a storage group requires that datanode delete all data and wal files and directories related to the storage group Key: IOTDB-3446 URL: https://issues.apache.org/jira/browse/IOTDB-3446 Project: Apache IoTDB Issue Type: Bug Reporter: Xinyu Tan Attachments: image-2022-06-10-11-28-47-233.png !image-2022-06-10-11-28-47-233.png! Yet none of them have been deleted -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (IOTDB-3445) Deleting a storage group requires that datanode delete all metadata and directories related to the storage group
Xinyu Tan created IOTDB-3445: Summary: Deleting a storage group requires that datanode delete all metadata and directories related to the storage group Key: IOTDB-3445 URL: https://issues.apache.org/jira/browse/IOTDB-3445 Project: Apache IoTDB Issue Type: Bug Reporter: Xinyu Tan Attachments: image-2022-06-10-11-26-26-980.png Currently, however, only files can be deleted, not directories !image-2022-06-10-11-26-26-980.png! -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (IOTDB-3444) Make periodic serivces more flexible
Eric Pai created IOTDB-3444: --- Summary: Make periodic serivces more flexible Key: IOTDB-3444 URL: https://issues.apache.org/jira/browse/IOTDB-3444 Project: Apache IoTDB Issue Type: Sub-task Components: Core/Engine Reporter: Eric Pai Assignee: Eric Pai Fix For: master branch -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Assigned] (IOTDB-3427) Make snapshot thread-safely
[ https://issues.apache.org/jira/browse/IOTDB-3427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yongzao Dan reassigned IOTDB-3427: -- Assignee: Song Ziyang (was: Yongzao Dan) > Make snapshot thread-safely > --- > > Key: IOTDB-3427 > URL: https://issues.apache.org/jira/browse/IOTDB-3427 > Project: Apache IoTDB > Issue Type: Improvement >Reporter: Yongzao Dan >Assignee: Song Ziyang >Priority: Major > Fix For: 0.14.0 > > > Check if ratis has concurrency control of snapshot and write? -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Assigned] (IOTDB-3217) [ClientPool]java.lang.IllegalStateException: Client has an error!
[ https://issues.apache.org/jira/browse/IOTDB-3217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yongzao Dan reassigned IOTDB-3217: -- Assignee: Xinyu Tan (was: Yongzao Dan) > [ClientPool]java.lang.IllegalStateException: Client has an error! > - > > Key: IOTDB-3217 > URL: https://issues.apache.org/jira/browse/IOTDB-3217 > Project: Apache IoTDB > Issue Type: Bug > Components: Core/Cluster >Affects Versions: 0.14.0-SNAPSHOT >Reporter: FengQingxin >Assignee: Xinyu Tan >Priority: Critical > Attachments: image-2022-05-17-17-19-30-376.png, > image-2022-05-17-17-23-33-855.png > > > [ErrorMSG]When start a datanode，there is an error in the log of config node > 重现步骤： > 1.编译生成的distribution文件复制两份（默认配置） > 2.进入confignode文件夹下sbin目录使用start-confignode.sh启动 （正常） > 3.进入datanode文件夹下sbin目录使用start-datanode.sh启动（datanode日志正常）（confignode有error日志如下） > java.lang.IllegalStateException: Client has an error! > at > org.apache.thrift.async.TAsyncClient.checkReady(TAsyncClient.java:83) > at > org.apache.iotdb.commons.client.async.AsyncDataNodeInternalServiceClient.isReady(AsyncDataNodeInternalServiceClient.java:109) > at > org.apache.iotdb.commons.client.async.AsyncDataNodeInternalServiceClient$Factory.validateObject(AsyncDataNodeInternalServiceClient.java:154) > at > org.apache.iotdb.commons.client.async.AsyncDataNodeInternalServiceClient$Factory.validateObject(AsyncDataNodeInternalServiceClient.java:122) > at > org.apache.commons.pool2.impl.GenericKeyedObjectPool.returnObject(GenericKeyedObjectPool.java:1470) > at > org.apache.iotdb.commons.client.ClientManager.returnClient(ClientManager.java:70) > at > org.apache.iotdb.commons.client.async.AsyncDataNodeInternalServiceClient.returnSelf(AsyncDataNodeInternalServiceClient.java:83) > at > org.apache.iotdb.commons.client.async.AsyncDataNodeInternalServiceClient.onError(AsyncDataNodeInternalServiceClient.java:104) > at > org.apache.thrift.async.TAsyncMethodCall.onError(TAsyncMethodCall.java:215) > at > org.apache.thrift.async.TAsyncMethodCall.transition(TAsyncMethodCall.java:210) > at > org.apache.thrift.async.TAsyncClientManager$SelectThread.transitionMethods(TAsyncClientManager.java:143) > at > org.apache.thrift.async.TAsyncClientManager$SelectThread.run(TAsyncClientManager.java:113) > Caused by: java.net.ConnectException: Connection refused > at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method) > at > sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717) > at > org.apache.thrift.transport.TNonblockingSocket.finishConnect(TNonblockingSocket.java:217) > at > org.apache.thrift.async.TAsyncMethodCall.doConnecting(TAsyncMethodCall.java:279) > at > org.apache.thrift.async.TAsyncMethodCall.transition(TAsyncMethodCall.java:189) > ... 2 common frames omitted > !image-2022-05-17-17-19-30-376.png! > > 期望：无报错信息，正常启动 -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Assigned] (IOTDB-3409) Snapshot error about UDFInfo
[ https://issues.apache.org/jira/browse/IOTDB-3409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jialin Qiao reassigned IOTDB-3409: -- Assignee: Steve Yurong Su (was: Yongzao Dan) > Snapshot error about UDFInfo > > > Key: IOTDB-3409 > URL: https://issues.apache.org/jira/browse/IOTDB-3409 > Project: Apache IoTDB > Issue Type: Bug > Components: mpp-cluster >Affects Versions: 0.14.0-SNAPSHOT >Reporter: 刘珍 >Assignee: Steve Yurong Su >Priority: Major > Attachments: config.properties.first, > image-2022-06-07-10-24-31-654.png, screenshot-1.png, screenshot-2.png > > > master_0606_c2afca1 > 3confignode，3datanode，schemaRegion/dataRegion 3副本。 > Restart recovery, the third confignode error ： > 2022-06-07 09:28:38,086 [pool-2-thread-1] ERROR o.a.i.c.r.SnapshotStorage:108 > - read file info failed for snapshot file > java.io.FileNotFoundException: > /data/liuzhen_test/master_0606_c2afca1/confignode/sbin/../data/consensus/47474747-4747-4747-4747-/sm/1_7/udf > (Is a directory) > at java.io.FileInputStream.open0(Native Method) > at java.io.FileInputStream.open(FileInputStream.java:195) > at java.io.FileInputStream.(FileInputStream.java:138) > at > org.apache.ratis.util.MD5FileUtil.computeMd5ForFile(MD5FileUtil.java:125) > at > org.apache.iotdb.consensus.ratis.SnapshotStorage.getLatestSnapshot(SnapshotStorage.java:106) > at > org.apache.ratis.statemachine.impl.BaseStateMachine.getLatestSnapshot(BaseStateMachine.java:96) > at > org.apache.ratis.server.impl.ServerState.lambda$new$2(ServerState.java:145) > at > org.apache.ratis.server.raftlog.RaftLogBase.(RaftLogBase.java:87) > at > org.apache.ratis.server.raftlog.segmented.SegmentedRaftLog.(SegmentedRaftLog.java:194) > at > org.apache.ratis.server.impl.ServerState.initRaftLog(ServerState.java:205) > at > org.apache.ratis.server.impl.ServerState.(ServerState.java:152) > at > org.apache.ratis.server.impl.RaftServerImpl.(RaftServerImpl.java:201) > at > org.apache.ratis.server.impl.RaftServerProxy.lambda$newRaftServerImpl$5(RaftServerProxy.java:274) > at > java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java:1590) > 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-06-07 09:28:38,087 [pool-2-thread-1] ERROR o.a.i.c.r.SnapshotStorage:108 > - read file info failed for snapshot file > java.io.FileNotFoundException: > /data/liuzhen_test/master_0606_c2afca1/confignode/sbin/../data/consensus/47474747-4747-4747-4747-/sm/1_7/ext > (Is a directory) > at java.io.FileInputStream.open0(Native Method) > at java.io.FileInputStream.open(FileInputStream.java:195) > at java.io.FileInputStream.(FileInputStream.java:138) > at > org.apache.ratis.util.MD5FileUtil.computeMd5ForFile(MD5FileUtil.java:125) > at > org.apache.iotdb.consensus.ratis.SnapshotStorage.getLatestSnapshot(SnapshotStorage.java:106) > at > org.apache.ratis.statemachine.impl.BaseStateMachine.getLatestSnapshot(BaseStateMachine.java:96) > at > org.apache.ratis.server.impl.ServerState.lambda$new$2(ServerState.java:145) > at > org.apache.ratis.server.raftlog.RaftLogBase.(RaftLogBase.java:87) > at > org.apache.ratis.server.raftlog.segmented.SegmentedRaftLog.(SegmentedRaftLog.java:194) > at > org.apache.ratis.server.impl.ServerState.initRaftLog(ServerState.java:205) > at > org.apache.ratis.server.impl.ServerState.(ServerState.java:152) > at > org.apache.ratis.server.impl.RaftServerImpl.(RaftServerImpl.java:201) > at > org.apache.ratis.server.impl.RaftServerProxy.lambda$newRaftServerImpl$5(RaftServerProxy.java:274) > at > java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java:1590) > 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) > ~ > ~ > !image-2022-06-07-10-24-31-654.png! > 复现流程 > 1. 192.168.10.62/66/68 72C256G > bm 连ip-62 写数据 > 停止3个datanode，备份数据 > /data/liuzhen_test/master_0606_c2afca1/datanode/data_2022_06_07-08-55-06_for_rec > 停止3个confignode，备份数据/data/liuzhen_test/master_0606_c2afca1/confignode/data_2022_06_07-08-55-39_for_rec > 2. 顺序启动ip-62,66,68 > 只有68的confignode有error > 另：3个datanode启动失败 > - > master_0607_7cb2d3f 与上面相同配置，干净环境跑测试，有1个confignode > 共识组下存在下面的文件夹信息（另2个confignode相同sm下为空） > !sc
[jira] [Assigned] (IOTDB-3409) Snapshot error about UDFInfo
[ https://issues.apache.org/jira/browse/IOTDB-3409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jialin Qiao reassigned IOTDB-3409: -- Assignee: Song Ziyang (was: Steve Yurong Su) > Snapshot error about UDFInfo > > > Key: IOTDB-3409 > URL: https://issues.apache.org/jira/browse/IOTDB-3409 > Project: Apache IoTDB > Issue Type: Bug > Components: mpp-cluster >Affects Versions: 0.14.0-SNAPSHOT >Reporter: 刘珍 >Assignee: Song Ziyang >Priority: Major > Attachments: config.properties.first, > image-2022-06-07-10-24-31-654.png, screenshot-1.png, screenshot-2.png > > > master_0606_c2afca1 > 3confignode，3datanode，schemaRegion/dataRegion 3副本。 > Restart recovery, the third confignode error ： > 2022-06-07 09:28:38,086 [pool-2-thread-1] ERROR o.a.i.c.r.SnapshotStorage:108 > - read file info failed for snapshot file > java.io.FileNotFoundException: > /data/liuzhen_test/master_0606_c2afca1/confignode/sbin/../data/consensus/47474747-4747-4747-4747-/sm/1_7/udf > (Is a directory) > at java.io.FileInputStream.open0(Native Method) > at java.io.FileInputStream.open(FileInputStream.java:195) > at java.io.FileInputStream.(FileInputStream.java:138) > at > org.apache.ratis.util.MD5FileUtil.computeMd5ForFile(MD5FileUtil.java:125) > at > org.apache.iotdb.consensus.ratis.SnapshotStorage.getLatestSnapshot(SnapshotStorage.java:106) > at > org.apache.ratis.statemachine.impl.BaseStateMachine.getLatestSnapshot(BaseStateMachine.java:96) > at > org.apache.ratis.server.impl.ServerState.lambda$new$2(ServerState.java:145) > at > org.apache.ratis.server.raftlog.RaftLogBase.(RaftLogBase.java:87) > at > org.apache.ratis.server.raftlog.segmented.SegmentedRaftLog.(SegmentedRaftLog.java:194) > at > org.apache.ratis.server.impl.ServerState.initRaftLog(ServerState.java:205) > at > org.apache.ratis.server.impl.ServerState.(ServerState.java:152) > at > org.apache.ratis.server.impl.RaftServerImpl.(RaftServerImpl.java:201) > at > org.apache.ratis.server.impl.RaftServerProxy.lambda$newRaftServerImpl$5(RaftServerProxy.java:274) > at > java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java:1590) > 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-06-07 09:28:38,087 [pool-2-thread-1] ERROR o.a.i.c.r.SnapshotStorage:108 > - read file info failed for snapshot file > java.io.FileNotFoundException: > /data/liuzhen_test/master_0606_c2afca1/confignode/sbin/../data/consensus/47474747-4747-4747-4747-/sm/1_7/ext > (Is a directory) > at java.io.FileInputStream.open0(Native Method) > at java.io.FileInputStream.open(FileInputStream.java:195) > at java.io.FileInputStream.(FileInputStream.java:138) > at > org.apache.ratis.util.MD5FileUtil.computeMd5ForFile(MD5FileUtil.java:125) > at > org.apache.iotdb.consensus.ratis.SnapshotStorage.getLatestSnapshot(SnapshotStorage.java:106) > at > org.apache.ratis.statemachine.impl.BaseStateMachine.getLatestSnapshot(BaseStateMachine.java:96) > at > org.apache.ratis.server.impl.ServerState.lambda$new$2(ServerState.java:145) > at > org.apache.ratis.server.raftlog.RaftLogBase.(RaftLogBase.java:87) > at > org.apache.ratis.server.raftlog.segmented.SegmentedRaftLog.(SegmentedRaftLog.java:194) > at > org.apache.ratis.server.impl.ServerState.initRaftLog(ServerState.java:205) > at > org.apache.ratis.server.impl.ServerState.(ServerState.java:152) > at > org.apache.ratis.server.impl.RaftServerImpl.(RaftServerImpl.java:201) > at > org.apache.ratis.server.impl.RaftServerProxy.lambda$newRaftServerImpl$5(RaftServerProxy.java:274) > at > java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java:1590) > 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) > ~ > ~ > !image-2022-06-07-10-24-31-654.png! > 复现流程 > 1. 192.168.10.62/66/68 72C256G > bm 连ip-62 写数据 > 停止3个datanode，备份数据 > /data/liuzhen_test/master_0606_c2afca1/datanode/data_2022_06_07-08-55-06_for_rec > 停止3个confignode，备份数据/data/liuzhen_test/master_0606_c2afca1/confignode/data_2022_06_07-08-55-39_for_rec > 2. 顺序启动ip-62,66,68 > 只有68的confignode有error > 另：3个datanode启动失败 > - > master_0607_7cb2d3f 与上面相同配置，干净环境跑测试，有1个confignode > 共识组下存在下面的文件夹信息（另2个confignode相同sm下为空） > !screen
[jira] [Assigned] (IOTDB-3408) Snapshot error about MTreeAboveSG
[ https://issues.apache.org/jira/browse/IOTDB-3408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yongzao Dan reassigned IOTDB-3408: -- Assignee: Yukun Zhou (was: Yongzao Dan) > Snapshot error about MTreeAboveSG > - > > Key: IOTDB-3408 > URL: https://issues.apache.org/jira/browse/IOTDB-3408 > Project: Apache IoTDB > Issue Type: Bug > Components: mpp-cluster >Affects Versions: 0.14.0-SNAPSHOT >Reporter: 刘珍 >Assignee: Yukun Zhou >Priority: Major > Attachments: image-2022-06-07-10-16-17-643.png > > > master_0606_c2afca1 > 3confignode，3datanode，schemaRegion/dataRegion 3副本。 > Restart recovery, the third confignode error ： > 2022-06-07 09:28:37,926 [ForkJoinPool.commonPool-worker-43] ERROR > o.a.i.d.m.m.MTreeAboveSG:564 - Wrong node type. Cannot deserialize > MTreeAboveSG from given buffer > !image-2022-06-07-10-16-17-643.png! > 复现流程 > 1. 192.168.10.62/66/68 72C256G > bm 连ip-62 写数据 > 停止3个datanode，备份数据 > /data/liuzhen_test/master_0606_c2afca1/datanode/data_2022_06_07-08-55-06_for_rec > 停止3个confignode，备份数据/data/liuzhen_test/master_0606_c2afca1/confignode/data_2022_06_07-08-55-39_for_rec > 2. 顺序启动ip-62,66,68 > 只有68的confignode有error > 另：3个datanode启动失败 -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (IOTDB-3443) RatisConsensus写入性能测试
Song Ziyang created IOTDB-3443: -- Summary: RatisConsensus写入性能测试 Key: IOTDB-3443 URL: https://issues.apache.org/jira/browse/IOTDB-3443 Project: Apache IoTDB Issue Type: Improvement Reporter: Song Ziyang Assignee: Song Ziyang -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (IOTDB-3442) New Cluster IT will crash
[ https://issues.apache.org/jira/browse/IOTDB-3442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17552196#comment-17552196 ] Yuan Tian commented on IOTDB-3442: -- 复现步骤： 代码在CIBugTest分支下，启动CI的命令是mvn clean verify -Dsession.test.skip=true -Diotdb.test.skip=true -Dcluster.test.skip=true -Dtsfile.test.skip=true -Dcommons.test.skip=true -Dconfignode.test.skip=true -Dconsensus.test.skip=true -pl integration-test -am -PClusterIT 运行完这个命令后，会看到下面类似的错误输出： !image-2022-06-09-21-04-50-129.png! 然后去integration-test/target/cluster-logs目录下，找到对应的挂掉测试的configNode和DataNode日志 然后去integration-test/target/cluster-logs目录下，找到对应的挂掉测试的configNode和DataNode日志 > New Cluster IT will crash > -- > > Key: IOTDB-3442 > URL: https://issues.apache.org/jira/browse/IOTDB-3442 > Project: Apache IoTDB > Issue Type: Bug >Reporter: Yuan Tian >Assignee: Tian Jiang >Priority: Major > Attachments: IoTDBAlignedSeriesQuery3IT.zip, > image-2022-06-09-21-02-26-617.png, image-2022-06-09-21-02-38-623.png, > image-2022-06-09-21-04-50-129.png > > > 详情见日志，下面是我对日志现象的简单说明： > Datanode14391在 20:41:14 开始向Datanode19031发送创建序列的fragment instance，20秒后（thrift > client的默认链接超时），即20:41:34，超时，CI挂掉。从Datanode19031里的日志可以看出，最后卡在了这一步 > !image-2022-06-09-21-02-26-617.png! > !image-2022-06-09-21-02-38-623.png! -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (IOTDB-3442) New Cluster IT will crash
Yuan Tian created IOTDB-3442: Summary: New Cluster IT will crash Key: IOTDB-3442 URL: https://issues.apache.org/jira/browse/IOTDB-3442 Project: Apache IoTDB Issue Type: Bug Reporter: Yuan Tian Assignee: Tian Jiang Attachments: IoTDBAlignedSeriesQuery3IT.zip, image-2022-06-09-21-02-26-617.png, image-2022-06-09-21-02-38-623.png 详情见日志，下面是我对日志现象的简单说明： Datanode14391在 20:41:14 开始向Datanode19031发送创建序列的fragment instance，20秒后（thrift client的默认链接超时），即20:41:34，超时，CI挂掉。从Datanode19031里的日志可以看出，最后卡在了这一步 !image-2022-06-09-21-02-26-617.png! !image-2022-06-09-21-02-38-623.png! -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (IOTDB-3441) Implements executeStatement method for Python client
yanglei created IOTDB-3441: -- Summary: Implements executeStatement method for Python client Key: IOTDB-3441 URL: https://issues.apache.org/jira/browse/IOTDB-3441 Project: Apache IoTDB Issue Type: Improvement Components: Client/Python Reporter: yanglei Implements executeStatement method for Python client. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (IOTDB-3308) NPE while query a timeseries with no data
[ https://issues.apache.org/jira/browse/IOTDB-3308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17552147#comment-17552147 ] Jinrui Zhang commented on IOTDB-3308: - Fixed in this PR. https://github.com/apache/iotdb/pull/6211 > NPE while query a timeseries with no data > - > > Key: IOTDB-3308 > URL: https://issues.apache.org/jira/browse/IOTDB-3308 > Project: Apache IoTDB > Issue Type: Bug >Reporter: Yuan Tian >Assignee: Jinrui Zhang >Priority: Major > Attachments: image-2022-05-27-17-03-26-223.png > > > create timeseries root.sg1.d1.s1 with datatype=INT32,encoding=PLAIN; > insert into root.sg2.d(time,s1,s2) values(1, 1, 2); > select * from root.**; > !image-2022-05-27-17-03-26-223.png! -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (IOTDB-3440) Add description of compatibility between 0.13.x and 0.12.x / master and 0.13.x
[ https://issues.apache.org/jira/browse/IOTDB-3440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17552128#comment-17552128 ] liaolanyu commented on IOTDB-3440: -- add description in the download page !image-2022-06-09-19-20-06-697.png! > Add description of compatibility between 0.13.x and 0.12.x / master and 0.13.x > -- > > Key: IOTDB-3440 > URL: https://issues.apache.org/jira/browse/IOTDB-3440 > Project: Apache IoTDB > Issue Type: Improvement >Reporter: liaolanyu >Assignee: liaolanyu >Priority: Major > Attachments: image-2022-06-09-19-19-51-184.png, > image-2022-06-09-19-20-06-697.png > > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (IOTDB-3440) Add description of compatibility between 0.13.x and 0.12.x / master and 0.13.x
liaolanyu created IOTDB-3440: Summary: Add description of compatibility between 0.13.x and 0.12.x / master and 0.13.x Key: IOTDB-3440 URL: https://issues.apache.org/jira/browse/IOTDB-3440 Project: Apache IoTDB Issue Type: Improvement Reporter: liaolanyu Assignee: liaolanyu Attachments: image-2022-06-09-19-19-51-184.png -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Assigned] (IOTDB-3416) Abstract interface of ConfigTask Execution for standalone IoTDB
[ https://issues.apache.org/jira/browse/IOTDB-3416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] 任宇华 reassigned IOTDB-3416: -- Assignee: 任宇华 > Abstract interface of ConfigTask Execution for standalone IoTDB > --- > > Key: IOTDB-3416 > URL: https://issues.apache.org/jira/browse/IOTDB-3416 > Project: Apache IoTDB > Issue Type: Task >Reporter: Haonan Hou >Assignee: 任宇华 >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (IOTDB-3439) Move Setting up RPC Service to the last step of starting DataNode
Jialin Qiao created IOTDB-3439: -- Summary: Move Setting up RPC Service to the last step of starting DataNode Key: IOTDB-3439 URL: https://issues.apache.org/jira/browse/IOTDB-3439 Project: Apache IoTDB Issue Type: Improvement Reporter: Jialin Qiao Assignee: yanze chen When starting RPC service, we need to prepare IoTDB ready. The main startup steps: (1) start InternalService (2) recover local regions, recover consensus groups (3) join to cluster (config node) (4) start RPCService -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Assigned] (IOTDB-3299) Migrate udf api to a seperate module
[ https://issues.apache.org/jira/browse/IOTDB-3299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liaolanyu reassigned IOTDB-3299: Assignee: liaolanyu (was: Steve Yurong Su) > Migrate udf api to a seperate module > > > Key: IOTDB-3299 > URL: https://issues.apache.org/jira/browse/IOTDB-3299 > Project: Apache IoTDB > Issue Type: Task >Reporter: Steve Yurong Su >Assignee: liaolanyu >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (IOTDB-3438) [ MultiLeaderConsensus & WAL ] Wal file is empty
刘珍 created IOTDB-3438: - Summary: [ MultiLeaderConsensus & WAL ] Wal file is empty Key: IOTDB-3438 URL: https://issues.apache.org/jira/browse/IOTDB-3438 Project: Apache IoTDB Issue Type: Bug Components: mpp-cluster Affects Versions: 0.14.0-SNAPSHOT Reporter: 刘珍 Assignee: Haiming Zhu Attachments: 100client_0609.sh, config.properties, image-2022-06-09-16-14-56-441.png, image-2022-06-09-16-16-24-773.png master_0609_9855b36 data_region_consensus_protocol_class=org.apache.iotdb.consensus.ratis.RatisConsensus 3confignode，3datanode，3副本，100用户并发insert，生成的wal文件有空的： !image-2022-06-09-16-16-24-773.png! 测试流程 1. 192.168.10.62/66/68 72C256G data_region_consensus_protocol_class=org.apache.iotdb.consensus.ratis.RatisConsensus 2. benchmark 配置见附件 192.168.10.68 /data/benchmark/weekly_shell/bm_0527_e7b23aa -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (IOTDB-3437) Remove RegionReplicaSet in serialization of MPP
Jinrui Zhang created IOTDB-3437: --- Summary: Remove RegionReplicaSet in serialization of MPP Key: IOTDB-3437 URL: https://issues.apache.org/jira/browse/IOTDB-3437 Project: Apache IoTDB Issue Type: Bug Reporter: Jinrui Zhang Assignee: Jinrui Zhang -- This message was sent by Atlassian Jira (v8.20.7#820007)
