刘珍 created IOTDB-3773:
-------------------------

             Summary: [ query ] The first batch of results is not output
                 Key: IOTDB-3773
                 URL: https://issues.apache.org/jira/browse/IOTDB-3773
             Project: Apache IoTDB
          Issue Type: Bug
          Components: mpp-cluster
    Affects Versions: 0.14.0-SNAPSHOT
            Reporter: 刘珍
            Assignee: Yuan Tian


master_0704_9f79ce6 , 执行查询
grep "align by device" logs/log_all.log
2022-07-07 16:17:04,778 [20220707_081704_00000_3-166] INFO  
o.a.i.d.m.p.Coordinator:115 - start executing sql: select count(s_4) from 
root.** align by device
2022-07-07 16:50:14,359 [pool-61-IoTDB-RPC-Client-1] INFO  
o.a.i.d.s.t.i.ClientRPCServiceImpl:593 - {color:red}*Cost: 1989760 ms*{color}, 
sql is select count(s_4) from root.** align by device
日志中出现查询耗时,但是后续日志还在打印此queryID的查询信息,请教田原:查询返回第一个fetch 
result会打印这个日志,{color:red}*但是并没有输出查询结果,需解决。*{color}

复现流程
1. 192.168.10.62/66/68
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
query_timeout_threshold=3600000

数据:/data/liuzhen_test/master_0704_9f79ce6/datanode/data   3.8TB
1000个设备
共3,000,000序列 

ip62 cli执行查询:
nohup ./sbin/start-cli.sh  -h 192.168.10.62 -e "select count(s_4) from root.** 
align by device;" > s4.out &

查询结果:|root.test.g_0.d_ip62_991|    676560|
|root.test.g_0.d_ip62_992|    676560|
|root.test.g_0.d_ip62_993|    676560|
|root.test.g_0.d_ip62_994|    676560|
|root.test.g_0.d_ip62_995|    676560|
|root.test.g_0.d_ip62_996|    676560|
|root.test.g_0.d_ip62_997|    676560|
|root.test.g_0.d_ip62_998|    676560|
|root.test.g_0.d_ip62_999|    676560|
+------------------------+----------+
It costs 3477.116s
Msg: 500: [INTERNAL_SERVER_ERROR(500)] Exception occurred: fetchResults failed. 
Task was cancelled. (最后这个异常还是因为超时被kill)






--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to