lywsvip/oneclickvirt.github.io
1
0
Fork 0
mirror of https://github.com/oneclickvirt/oneclickvirt.github.io.git synced 2026-07-01 01:36:12 +08:00
Code Issues Packages Projects Releases Wiki Activity

feat: 添加开设实例过多导致节点异常时的处理方式

Browse Source
This commit is contained in:
spiritlhl
2025-10-24 12:27:59 +00:00
parent e72981b4ef
commit fcaa2b5795
5 changed files with 51 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

BIN
docs/en/guide/oneclickvirt/images/iofailed.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 152 KiB

25
docs/en/guide/oneclickvirt/oneclickvirt_qa.md
View File

@@ -68,4 +68,27 @@ Execute
docker volume rm oneclickvirt-data oneclickvirt-storage oneclickvirt-config
```
to delete
to delete
## Excessive Instance Creation Causes Node Abnormalities
A prominent symptom is extremely slow operation execution, with commands taking several minutes to complete.
This commonly occurs when a node has poor I/O performance and is over-allocated with SWAP memory.
For example, in an LXD environment, executing ```lxc list``` may result in an error:
```shell
internal error, please report: running “lxd.lxc” failed: cannot create transient scope: DBus error “org.freedesktop.DBus.Error.TimedOut”: [Failed to activate service ‘org.freedesktop.systemd1’: timed out (service_start_timeout=25000ms)]
```
The root cause is setting too many instances while the provider imposes strict I/O restrictions.
![](./images/iofailed.png)
At this point, only one solution remains: force-reboot the node server.
Immediately after reboot, log into SSH and use the corresponding script to clear swap usage, then delete some instances to free resources.
Since containers take time to restart individually after reboot, this window may not delete many instances, but each reboot clears some.
Ultimately, when limiting instance counts, carefully assess node performance. Avoid overloading weaker nodes or those with strict constraints.