zx shen
Reputation: 17
Why Apache IoTDB reported “can't allow more query tasks” when resources are not full?
I am currently using Apache IoTDB Version 1.1.0 and found a problem. When I tried to use "show queries" command, an error message appears: "Msg: 301: The system can't allow more query tasks."
I checked the computing resources and seems like it is not full. Right know I can only restart IoTDB to solve this error. Anyone know how to deal with this problem?
Upvotes: 0
Views: 29
Answers (1)
Sihan Liu
Reputation: 395
This bug is already fixed in the newest version appealed today. You can update to Apache IoTDB Version 1.1.1 in github and see if this problem is solved.
Upvotes: 0
Related Questions
- Why Apache IoTDB reported "if certain time series exists" after upgraded to Version 1.0.1?
- Why did detected pause in JVM or host machine warning reported frequently in Apache IoTDB while the system is still running?
- How to judge the limit number of query tasks mentioned in the system message of Apache IoTDB?
- Why did the placeholder error occurred when executing continuous query in Apache IoTDB?
- Why did the session of Apache IoTDB reported await session pool.Open(false)?
- Why Apache IoTDB encountered OOM problem when doing tsfile flushing?
- How to deal with insertRecord failed error when server can still be executed in Apache IoTDB Version 1.1.0?
- 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?