Open rahullepakshi opened 8 months ago
@baum can you refer to this issue? cc - @leonidc
@rahullepakshi please provide more details:
Most probably this is once again the same rm issue.
@caroav replies inline
@rahullepakshi please provide more details:
- Did you remove daemons or uninstalled gws on this cluster?
Yes, I removed daemons and uninstalled gws too and for this fresh installation it has GW load balacning set to 7. But my question during this new installation, though it sets to 7, why should ana_state of ana_group 2 and 4 be optimized. On a fresh installation, it should make them inaccessible as they are not this GWs preffered ana_group
- How many nvmeof gws are running there?
2 nvmeof GWs
Most probably this is once again the same rm issue.
This may be related but not same
This issue is open for discussion if needed.
I assume that ana_group and --load-balancing-group are same. I am observing a strange ana_state of "optmized" for multiple "ana_groups" on a Gateway node as below. In this case ana_group 2 and 4 also has ana_state optimized and of ana_group: 7 is expected as this Gateway's load balancing group is 7
IMO, this should not the be the case, all ana_states other than that of ana_group: 7 should always be inaccessible. Because a GW should only have one optimized path at any point in time. Say if we add a new gateway and it takes "Gateway's load balancing group as 2 or 4" this will cause issue as there will be 2 optimized paths to same namespace always and during failover - I am not sure how this handled.
Please let me know you thoughts