-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: Fix anti-affinity rules not evaluating a new and different node correctly #68
Conversation
Hi, I just tried PR #68 but I have this error : <6> ProxLB: Info: [api-connection]: API connection succeeded to host: 10.99.99.10. |
I tried to relaunch without any modification and it passed : 6> ProxLB: Info: [balanciness-validation]: Rebalancing for memory is not needed. Highest usage: 93% | Lowest usage: 86%. |
Thanks, valuable hint. Found an issue which resulted in the first issue. Will fix it later (not sure if I can do it today). |
45c3bef
to
5ca172b
Compare
Hey @adminsyspro, I just force-pushed the fix. You may give it a try when you have time for it. Happy to hear if this fixes your issue. Have a nice weekend, |
Hey @gyptazy, Thanks for the update, I just tried your fix but there is always an issue. I have thousand of line like that : "Reached limit for random node evaluation. Unable to find a suitable new node." <6> ProxLB: Info: [random-node-getter]: New random node Proxmox-3AZ-1-C evaluated in run 28. |
e98b6fb
to
a8115e1
Compare
Hey @adminsyspro, sorry for that. I pushed a new version but it also shows that new and better unit tests are needed to find such issues faster. However, please give the newly committed version a try. It also prepares a new config options in the However, this option is not yet evaluated with this commit version but this should at least fix your issue (hopefully). Thanks for your time and efforts into testing this! gyptazy |
Hey @gyptazy It works perfectly now :) Regards |
I have another question about master_only, I defined master_only: 1 but I have this error : <6> ProxLB: Info: [only-on-master-executor]: Master only rebalancing is defined. Starting validation. I have a cluster of 3 node. |
I found out why I got this error, I didn't create HA rule yet. It works now ! |
Hey @adminsyspro, happy to hear, thanks for testing and confirming. I'll give it some additional tests this evening when back home and if it succeeds all ones it'll be merged. Cheers, |
a8115e1
to
1420183
Compare
Thanks for the hint. I adjusted the output, hope this makes it more clear: |
Validated in different setups and clusters. LGTM |
fix: Fix anti-affinity rules not evaluating a new and different node correctly.
General
This PR fixes an issue where a new and different node was not correctly evaluated when working with anti-affinity rules. It also applies and adds some more logging and fixes wrong logging options that were previously defined.
Test
Fixes
Fixes: #67