Hi, I will fix this bug , i will refer to the *executeQuery()* method of reconnection for repair.
Pr :https://github.com/apache/incubator-iotdb/pull/543 <https://github.com/apache/incubator-iotdb/pull/543> > 在 2019年11月11日，下午5:42，刘大伟 (Jira) <j...@apache.org <mailto:j...@apache.org>> 写道： > > 刘大伟 created IOTDB-300: > ------------------------- > > Summary: When the server restart, the client cannot find the > connection error > Key: IOTDB-300 > URL: https://issues.apache.org/jira/browse/IOTDB-300 > <https://issues.apache.org/jira/browse/IOTDB-300> > Project: Apache IoTDB > Issue Type: Bug > Reporter: 刘大伟 > > > 1. Start the IOTDB-Client and connect to the server successfully > > 2. Restart the server side > > 3. And then if you execute any command on the client, you will receive an > error message: 'MSG: cannot get ID for statement' > > > > > This problem occurs after the [iotdb-291] merge, because a *requeststmtid()* > method is added before executing the SQL statement, but this method is not > the same as the previous *executeQuery()* method: when an error is returned, > re-establish a connection and try again. > > > > I will refer to the *executeQuery()* method of reconnection for repair. Of > course, I think the best way is to have the client constantly check the > connection. What do you think, friends? > > > > -- > This message was sent by Atlassian Jira > (v8.3.4#803005) >
