SessionPool 连接3个节点集群超时

日志信息如下:

SessionPool

022-08-06 00:00:16.002 WARN [SimpleAsyncTaskExecutor-7289746] org.apache.iotdb.session.pool.SessionPool.getSession.225 the SessionPool has wait for 60 seconds to get a new connection: 192.200.3.7:6667 with root, root
2022-08-06 00:00:16.002 WARN [SimpleAsyncTaskExecutor-7289746] org.apache.iotdb.session.pool.SessionPool.getSession.232 current occupied size 0, queue size 0, considered size 1000
2022-08-06 00:00:16.002 ERROR [SimpleAsyncTaskExecutor-7289746] com.yhd.admin.scada.iotdb.TimeSeriesDao.insert.41 >>>>>>>>>>>>>>>>>:insert into root.DLGL.2202( Time,ZS2202_Ua_PV)values(1659715216286,693.373474),timeout to get a conn
ection from 192.200.3.7:6667
SessionPool 配置如下：

` public SessionPool SessionPool() {
return new SessionPool(iotDBCfg.getIp(), iotDBCfg.getPort(), iotDBCfg.getUsername(), iotDBCfg.getPassword(), 1000);
}`

- Version apache-iotdb-0.13.0-all-bin 3个节点集群

**Additional context**
Add any other context about the problem here.

Start with SessionPool.getSession and the supplied timeout logs, then review how connections are configured for the three-node cluster in apache-iotdb-0.13.0. Reproduce the timeout with the shown pool size and cluster setup, and confirm that connection acquisition succeeds without the reported 60-second wait.

Written by the indexing model from the issue text.