When running a rolling update on a cluster it happens that the new solr config gets published and is missing on the old nodes ( like new Beanresolvers introduced) so that the old nodes get an error still being up.
Is there any way to prevent this behavior integrated in SAP Commerce that i am missing ? Or is the only way to not do rolling updates at this point ?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.