Hi,
you really understand the subject and I'm going to ask for patience as I'm getting started on the product. I will take to get your knowledge ..rs
Come on...
I put one of the nodes into maintenance and chose the default option that appears. I did not choose the middle option. It has already been selected and seemed the safest. However, vSAN stayed at 19% for about 20 minutes and we understood that it was stuck and we were worried if we had chosen the right option. Then we canceled. Soon after this message appears. I mean, days after.
So I researched and found out that I could do the rebalancing manually. I did and the status of disk balanced turned green, that is, problem solved.
What I mean is that this was not done again, but the same message returned. That is, if I have not done anything NOW, why does the same message that has occurred previously appear and was resolved?
Do you understand now what I mean?
Looking at your answer to the first question, I understand that really 20 minutes is little, I could have waited longer. Operational failure, okay!
Now that you know I did not set the host on maintenance, I wondered, why did it happen again? Where can I look to see where my problem may be?
I looked at the events for some hardware failure, shutdown servers, but in vCenter I did not find LOGs for this. So I found out that there is vRealize that has LOGs, but I also have not encountered any flaws in vRealize on this day that appears in vxRail Manager when it started cluster failures.
Well, I did the rebalancing again and made an ack on the alarm in the cluster and now no errors appear.
My concern is that this error appears again, so I wanted to monitor the disk balanced to see if at some point it will get back on edge. So I can see what the end user is doing that is causing this failure again.
You told me that when it's 80% rebalanced will happen automatically. I figured it would not happen automatically if proative was not enabled. Got it!
Now I come back to the question ... why did this happen again?
Where should I look to evaluate whether it is close to generating this new warning of need for balanced warning?
At that point, as I said, I've already rebalanced.
Thank you.