Hester Tso
Reputation: 350
Why did the cli.bat tool of Apache IoTDB cannot be started after setting `rpc_thrift_compression_enable = true`?
I would like to ask about cli.bat cannot be started after rpc_thrift_compression_enable being set to true in iotdb-engine.properties of Apache IoTDB Version 0.13.4. What may be the reason for this situation? I tried to use a different computer to access IoTDB, and the system prompted can not establish connection with jdbc:iotdb://172.16.3.116:6667/: Socket is closed by peer.
Upvotes: 0
Views: 22
Answers (1)
Yuan Tian
Reputation: 399
If the Apache IoTDB server has already set rpc_thrift_compression_enable=true, then when using command, the Cli tool must add -c. See if adding this will solve your problem.
Upvotes: 0
Related Questions
- In data insertion of Apache IoTDB, what configuration did setting rowSize stores?
- When using `delete from root.table` command, why did the table cannot be deleted in Apache IoTDB?
- For a two-stage cluster deployed in Apache IoTDB, why the confignode of the second server cannot be started and added to the seed confignode?
- Why did the session of Apache IoTDB reported await session pool.Open(false)?
- After upgrading to Version 1.2.2 of Apache IoTDB, why did the system reported connection error when using cli?
- Can not establish connection with jdbc:iotdb://127.0.0.1:6667/
- Why the port of confignode cannot be used after metrics are enabled in Apache IoTDB?
- Why does the log of supervisor keep reporting abnormal startup of Apache IoTDB Version 1.0.1?
- Why Apache IoTDB Version 1.0.1 cannot use ip number to connect server?
- Why the previous data cannot be queried when data directory did not change in Apache IoTDB?