Open kvanhijf opened 7 years ago
This is (to me at least) expected. If we don't want this behaviour we should either
Probably the most workable/desirable solution is the first one (no more asd discovery).
Regarding my preference for no more asd discovery: that would also prevent issues such as #269 (maintenance from env1 trying to connect to asds from env2 - which it possibly can't even reach due to how the network is configured)
@domsj I believe there is a command to purge OSDs from monitoring, I assume the same can be used to remove it from list-all-osds?
yes, it can be used. the question is: when should it be used? (and the answer determines wether you fall into option 2 or 3 that I mentioned)
@kvanhijf why would you need a 'purified' list-all-osds? What is the context of this ticket. Can the extra command to purge from the monitoring be of any help?
@wimpers : Reason i reported this was just because it seemed not logic to me, to see these differences between ALBA backends. They're not causing any issues for us, but it might be good for OPS to know in which cases they can end up in such behavior
BAM needs to lay its egg. Will we still do auto discovery now that project Golden Gate is coming our way.
This issue occurs when having multiple ALBA Backends
Above output shows the ASDs listed by backend
bend1
andbend2
All ASDs of both nodes are identical and 2 ASD has been claimed bybend1
and 1 ASD has been claimed bybend2
Now when removing an ASD from
bend1
(GZPEeAG8pf8PaFNCiXFetYJGBCEDcboq), we see its being reported asdecommissioned
bybend1
, but obvisouly this is not the case forbend2
, as seen belowAfter maintenance has completely purged the ASD i get this output now
ASD with ID
GZPEeAG8pf8PaFNCiXFetYJGBCEDcboq
is still being reported bybend2
, but no longer bybend1
The more ASDs get claimed and removed between different Backends, the more thelist-all-osds
output starts differing