You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@iotdb.apache.org by "FengQingxin (Jira)" <ji...@apache.org> on 2022/05/22 13:21:00 UTC
[jira] [Created] (IOTDB-3252) [cluster]Can not be connect after stop 2 config nodes(3C3D)
FengQingxin created IOTDB-3252:
----------------------------------
Summary: [cluster]Can not be connect after stop 2 config nodes(3C3D)
Key: IOTDB-3252
URL: https://issues.apache.org/jira/browse/IOTDB-3252
Project: Apache IoTDB
Issue Type: Bug
Components: Core/Cluster
Affects Versions: 0.14.0-SNAPSHOT
Reporter: FengQingxin
Reproduce steps:
# start a cluster with 3C3d(default config).
# excute below sql to test cluster:
{color:#57d9a3}set storage group to root.sg;{color}
{color:#57d9a3}create timeseries root.sg.d.s1 with datatype=INT32,encoding=RLE,compression=snappy;{color}
{color:#57d9a3}create timeseries root.sg.d.s2 with datatype=INT32,encoding=RLE,compression=snappy;{color}
{color:#57d9a3}create timeseries root.sg.d.s3 with datatype=INT32,encoding=RLE,compression=snappy;{color}
{color:#57d9a3}insert into root.sg.d(time,s1,s2,s3) values(1,1,2,3);{color}
{color:#57d9a3}insert into root.sg.d(time,s1,s2,s3) values(2,1,2,3);{color}
{color:#57d9a3}select * from root.**{color}
# stop a config node(not the target node).
# try to connect datanode with iotdb-cli. It is ok.
# stop a config node(not the target node).
# try to connect datanode with iotdb-cli. {color:#de350b}Failed{color}
{color:#de350b}Can not establish connection with jdbc:iotdb://Chaos-5:6667/ : Internal error processing openSession. Host is Chaos-5, port is 6667.{color}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)