Monster Zhang
Reputation: 152
Why Apache IoTDB reported `FragmentInstance is aborted by timeout` query error?
I wonder why this error happened in Apache IoTDB? The information is Caused by: org.apache.iotdb.db.mpp.execution.schedule.FragmentInstanceAbortedException: FragmentInstance 20231114_020733_73751_1.1.0 is aborted by timeout. There is a multi-threaded query in my code. Does this timeout mean that the data for this multi-threaded query are not queried?
Upvotes: 0
Views: 14
Answers (1)
Summer
Reputation: 504
You can increase the query timeout settings of Apache IoTDB and try again. I guess that you have queried all the data in the device dimension, and that's why this query got timeout and no result came back.
Upvotes: 0
Related Questions
- When reported current confignode is not ready and all query progress got timeout, what configuration should be checked in Apache IoTDB?
- When upgrading Version 1.2.1 to 1.2.2, why did the `quantity` parameter of the monitoring panel adapted to Apache IoTDB have no data?
- After upgrading to Version 1.2.2 of Apache IoTDB, why did the system reported connection error when using cli?
- Why Apache IoTDB reported `too many requests` error and need to restart to be normal?
- How to query interpolation in Apache IoTDB?
- After restarting Apache IoTDB, why the system still prompted 6667 configuration port is occupied?
- Why Apache IoTDB Version 1.0.1 reported 305 code error on Ratis consensus?
- Why did Apache IoTDB filled data in aligned time series but reported "timeseries not aligned" error?
- Why original query reported 301 error after data migration to Apache IoTDB Version 1.0.0?
- Why Apache IoTDB reported "Invalid method name" error after startup?