You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@iotdb.apache.org by "刘珍 (Jira)" <ji...@apache.org> on 2023/03/20 01:42:00 UTC
[jira] [Commented] (IOTDB-5204) start-cli.sh -timeout does not work
[ https://issues.apache.org/jira/browse/IOTDB-5204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17702397#comment-17702397 ]
刘珍 commented on IOTDB-5204:
---------------------------
rc/1.1.0 0316_aaa86ca
-timeout参数不起作用
cli -timeout 36000 -e "select min_time(s_9),max_time(s_9),count(s_9) from root.** align by device;" > 0320_all_nodes_online_q1.out &
未到超时时间，返回：Msg: 301: null
2023-03-20 09:30:46,220 [pool-23-IoTDB-ClientRPC-Processor-64] WARN o.a.i.d.u.ErrorHandlingUtils:89 - Status code: 301, Query Statement: "select min_time(s_9),max_time(s_9),count(s_9) from root.** align by device". executeStatement failed
org.apache.iotdb.commons.exception.IoTDBException: org.apache.iotdb.db.mpp.execution.fragment.FragmentInstanceFailureInfo$FailureException
at org.apache.iotdb.db.mpp.plan.execution.QueryExecution.dealWithException(QueryExecution.java:476)
at org.apache.iotdb.db.mpp.plan.execution.QueryExecution.getResult(QueryExecution.java:459)
at org.apache.iotdb.db.mpp.plan.execution.QueryExecution.getByteBufferBatchResult(QueryExecution.java:494)
at org.apache.iotdb.db.utils.QueryDataSetUtils.convertQueryResultByFetchSize(QueryDataSetUtils.java:254)
at org.apache.iotdb.db.service.thrift.impl.ClientRPCServiceImpl.lambda$static$0(ClientRPCServiceImpl.java:166)
at org.apache.iotdb.db.service.thrift.impl.ClientRPCServiceImpl.executeStatementInternal(ClientRPCServiceImpl.java:239)
at org.apache.iotdb.db.service.thrift.impl.ClientRPCServiceImpl.executeStatementV2(ClientRPCServiceImpl.java:480)
at org.apache.iotdb.service.rpc.thrift.IClientRPCService$Processor$executeStatementV2.getResult(IClientRPCService.java:3629)
at org.apache.iotdb.service.rpc.thrift.IClientRPCService$Processor$executeStatementV2.getResult(IClientRPCService.java:3609)
at org.apache.thrift.ProcessFunction.process(ProcessFunction.java:38)
at org.apache.iotdb.db.service.thrift.ProcessorWithMetrics.process(ProcessorWithMetrics.java:64)
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)
Caused by: org.apache.iotdb.db.mpp.execution.fragment.FragmentInstanceFailureInfo$FailureException: null
at org.apache.iotdb.db.mpp.execution.fragment.FragmentInstanceManager.lambda$cancelTimeoutFlushingInstances$9(FragmentInstanceManager.java:304)
at java.util.concurrent.ConcurrentHashMap.forEach(ConcurrentHashMap.java:1597)
at org.apache.iotdb.db.mpp.execution.fragment.FragmentInstanceManager.cancelTimeoutFlushingInstances(FragmentInstanceManager.java:300)
at org.apache.iotdb.commons.concurrent.threadpool.ScheduledExecutorUtil.lambda$scheduleWithFixedDelay$1(ScheduledExecutorUtil.java:177)
at org.apache.iotdb.commons.concurrent.WrappedRunnable$1.runMayThrow(WrappedRunnable.java:44)
at org.apache.iotdb.commons.concurrent.WrappedRunnable.run(WrappedRunnable.java:29)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
... 3 common frames omitted
2023-03-20 09:30:46,220 [pool-23-IoTDB-ClientRPC-Processor-64$20230320_011706_00001_3] INFO o.a.i.d.m.p.Coordinator:221 - {color:red}*Cost: 820022 ms, *{color}sql is select min_time(s_9),max_time(s_9),count(s_9) from root.** align by device
> start-cli.sh -timeout does not work
> ------------------------------------
>
> Key: IOTDB-5204
> URL: https://issues.apache.org/jira/browse/IOTDB-5204
> Project: Apache IoTDB
> Issue Type: Bug
> Components: mpp-cluster
> Affects Versions: master branch, 1.0.1-SNAPSHOT
> Reporter: 刘珍
> Assignee: Yuan Tian
> Priority: Minor
> Attachments: image-2022-12-14-11-55-26-408.png
>
>
> rel/1.0 1214 b7516d4 1rep 1C1D
> 1. start 1rep 1C1D cluster
> config_node_consensus_protocol_class=org.apache.iotdb.consensus.ratis.RatisConsensus
> schema_region_consensus_protocol_class=org.apache.iotdb.consensus.ratis.RatisConsensus
> data_region_consensus_protocol_class=org.apache.iotdb.consensus.iot.IoTConsensus
> 2. cli query specified -timeout 36000 second ，
> In fact, the timeout is still 60 seconds
> 在配置文件中指定超时时间，没这个问题。
> !image-2022-12-14-11-55-26-408.png!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)