peps
September 30, 2023, 7:31am
1
Greetings to all!
I’ve been watching an annoying bug in a multinode for a long time. When at least one node is unavailable, it is impossible to obtain statistics!
In earlier versions, an inaccessible node was simply skipped and did not participate in the statistics at the moment.
Can this be fixed?
Alexey
September 30, 2023, 10:34am
2
We have a bug for this:
opened 08:53AM - 08 Nov 21 UTC
Enhancement
SNO
### Background
To me a large part of the appeal of the Multinode dashboard is… to easily check the availability of your storage nodes.
### Problem
Currently if any one of the storage nodes are down it doesn't seem to work at all. So it does not help you in finding out which one is down. Worse still, if you've permanently lost a storage node then the dashboard can't be fixed through the GUI (maybe it works after waiting a long time I haven't had the patience).
### Solution
I haven't looked at the code but I suspect it would require some rearchitecting of the Ajax calls to fix this problem.
A quick fix might be to set a more agressive timeout for the DRPC calls to the storage nodes.
If you can fix that, we would appreciate that!
All Community contribution is welcome!
peps
September 30, 2023, 4:53pm
3
I see that there is no movement on the issue for 2 years.
Is it technically difficult?
In general, the multinode is made, very clumsily, very slow…
1 Like
Alexey
October 1, 2023, 12:58am
4
It has a low priority. If you can fix it - please submit a pull request, we are glad to accept a Community contribution.