You mention here the "recommended (and most tested) order" which
order is that?
Using cephadm with containers wouldn't the orchestrator command
below take care of everything without having me to worry about any
upgraded order/path?
Yes, the orchestrator does that for you, but it can't hur
Thanks to both of you for your answers. So I understand that the best practice
would be to keep all nodes on the same Ceph version number.
You mention here the "recommended (and most tested) order" which order is that?
Using cephadm with containers wouldn't the orchestrator command below take ca
Den fre 23 apr. 2021 kl 08:45 skrev Eugen Block :
> you can't really avoid having different versions in a cluster, think
> about an update/upgrade. Usually it's not an issue, but I would
> recommend to have that state for as short as possible. Just a recently
> a customer complained about inconsist
Hi,
you can't really avoid having different versions in a cluster, think
about an update/upgrade. Usually it's not an issue, but I would
recommend to have that state for as short as possible. Just a recently
a customer complained about inconsistent objects on a regular basis
although all
