suchenglong created IOTDB-4316:
----------------------------------

             Summary: Query error after a replica node is shut down (successful 
second execution)
                 Key: IOTDB-4316
                 URL: https://issues.apache.org/jira/browse/IOTDB-4316
             Project: Apache IoTDB
          Issue Type: Bug
    Affects Versions: 0.14.0-SNAPSHOT
            Reporter: suchenglong
         Attachments: image-2022-09-02-17-45-43-302.png

环境:集群(3c3d,2副本)

步骤:
 # 插入一条数据(insert into root.clsu2.test1.test(time,s1) values 
(100,200)),此时会自动创建存储组,用show 
regions查看,此时192.168.1.218是leader,此时能够查询出数据。这时192.168.1.218是leader,192.168.1.222是follower
 # 此时停掉192.168.1.218,此时192.168.1.222变为了leader
 # 插入一条新数据(insert into root.clsu2.test1.test(time,s1) values 
(200,200)),此时查询可以查询到两条数据。
 # 启动192.168.1.218,等待一会,停掉192.168.1.222,此时218变为了leader
 # 执行查询(select s1 from root.clsu2.test1.test),此时报错                              
        IoTDB> select s1 from root.clsu2.test1.test
Msg: 500: [INTERNAL_SERVER_ERROR(500)] Exception occurred: "select s1 from 
root.clsu2.test1.test". executeStatement failed. all replicas for 
region[TConsensusGroupId(type:DataRegion, id:0)] are not available in these 
DataNodes[[TDataNodeLocation(dataNodeId:4, 
clientRpcEndPoint:TEndPoint(ip:192.168.1.218, port:6667), 
internalEndPoint:TEndPoint(ip:192.168.1.218, port:9003), 
mPPDataExchangeEndPoint:TEndPoint(ip:192.168.1.218, port:8777), 
dataRegionConsensusEndPoint:TEndPoint(ip:192.168.1.218, port:40010), 
schemaRegionConsensusEndPoint:TEndPoint(ip:192.168.1.218, port:50010)), 
TDataNodeLocation(dataNodeId:5, clientRpcEndPoint:TEndPoint(ip:192.168.1.222, 
port:6667), internalEndPoint:TEndPoint(ip:192.168.1.222, port:9003), 
mPPDataExchangeEndPoint:TEndPoint(ip:192.168.1.222, port:8777), 
dataRegionConsensusEndPoint:TEndPoint(ip:192.168.1.222, port:40010), 
schemaRegionConsensusEndPoint:TEndPoint(ip:192.168.1.222, port:50010))]]
 # 再次执行此sql,此时查询结果正常 !image-2022-09-02-17-45-43-302.png!

 



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

Reply via email to