ainode 查询报错 Timeout waiting for idle object, borrowMaxWaitMillis=10000

使用ainode的 Stray 模型查询时报错超时了，该超时参数在哪个地方能配置吗？
版本：
```
> show cluster
+------+----------+-------+------------------+------------+-------+---------+
|NodeID| NodeType| Status| InternalAddress|InternalPort|Version|BuildInfo|
+------+----------+-------+------------------+------------+-------+---------+
| 0|ConfigNode|Running| iotdb-service-dev| 10710| 1.3.3| ad95a7e|
| 1| DataNode|Running| iotdb-service-dev| 10730| 1.3.3| ad95a7e|
| 6| AINode|Running|ainode-service-dev| 10810| 1.3.3| 385781d|
+------+----------+-------+------------------+------------+-------+---------+
Total line number = 3
```

使用 Stray：
```
> call inference(_Stray, "SELECT DIFFERENCE(`Full Scans/sec`)/(TIME_DIFFERENCE(`Full Scans/sec`)/1000) FROM root.test.`521208820433152` WHERE Time >= 2025-07-16 09:50:14 and Time <= 2025-07-16 10:20:14", k=2)
Msg: org.apache.iotdb.jdbc.IoTDBSQLException: 301: org.apache.iotdb.db.exception.runtime.ModelInferenceProcessException: java.util.NoSuchElementException: Timeout waiting for idle object, borrowMaxWaitMillis=10000
```

正常查询数据：
```
> SELECT DIFFERENCE(`Full Scans/sec`)/(TIME_DIFFERENCE(`Full Scans/sec`)/1000) FROM root.test.`521208820433152` WHERE Time >= 2025-
07-16 09:50:14 and Time <= 2025-07-16 10:20:14
+-----------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Time|DIFFERENCE(root.test.`521208820433152`.`Full Scans/sec`) / TIME_DIFFERENCE(root.olm.`521208820433152`.`Full Scans/sec`) / 1000|
+-----------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
|2025-07-16T10:08:02.835+08:00| 80.48639258830342|
|2025-07-16T10:08:03.696+08:00| 121.95121951219512|
|2025-07-16T10:08:04.714+08:00| 1956.7779960707269|
|2025-07-16T10:08:05.571+08:00| 130.68844807467912|
|2025-07-16T10:08:06.671+08:00| 97.27272727272727|
|2025-07-16T10:08:07.879+08:00| 115.89403973509934|
|2025-07-16T10:08:08.587+08:00| 138.4180790960452|
|2025-07-16T10:08:09.649+08:00| 1881.3559322033898|
|2025-07-16T10:08:10.555+08:00| 114.79028697571744|
|2025-07-16T10:08:11.598+08:00| 106.42377756471717|
|2025-07-16T10:08:12.729+08:00| 123.7842617152962|
|2025-07-16T10:08:13.728+08:00| 247.24724724724726|
|2025-07-16T10:08:14.858+08:00| 1624.778761061947|
|2025-07-16T10:08:16.061+08:00| 102.24438902743141|
|2025-07-16T10:08:17.159+08:00| 122.95081967213113|
|2025-07-16T10:08:18.198+08:00| 109.720885466795|
|2025-07-16T10:10:06.879+08:00| 18.108040963921937|
|2025-07-16T10:12:07.936+08:00| 1.1564800052867656|
|2025-07-16T10:14:08.986+08:00| 0.9087154068566708|
|2025-07-16T10:16:09.978+08:00| 1.0661861941285373|
|2025-07-16T10:18:10.868+08:00| 0.9512780213417156|
|2025-07-16T10:20:11.923+08:00| 16.190987567634544|
+-----------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
Total line number = 22
It costs 0.023s
```

Beginne beim Inferenzpfad des AINode Stray-Modells und verfolge die Quelle des Timeouts `borrowMaxWaitMillis=10000`. Prüfe, wie die Inferenzverbindung oder der Objektpool konfiguriert ist, und verifiziere anschließend, ob sich das Timeout ändern lässt und ob die gemeldete Abfrage ohne den Fehler abgeschlossen wird.

Vom Indexierungsmodell aus dem Issue-Text verfasst.