Hello, However, after a short amount of time, the linstor controller just stops > responding again, with basic commands like "linstor node list" timing > out after 5 minutes. >
We were fixing a few deadlock-related issues in the recent LINSTOR release, but also have found another one (will be included in the next release). However, if you (or any other reader here) face a hanging controller, you would help us to capture us a thread-dump of the java process and send it to me (directly is fine, no need to spam the ML with thread-dumps, since they scale with CPU count and can easily get >100kb). To get such a thread dump there are 3 options, whereas the first two might require a JDK installed instead of just a JRE. The third option works also with a JRE: 1) jstack <pid> 2) jcmd <pid> Thread.print 3) kill -3 <pid> The third option will NOT kill the process, but it will only print the thread dump on stdout, so likely into your journalctl. -- Best regards, Gabor Hernadi
