Skip to Content
Jan 20, 2021 at 11:16 AM

Rolling Updates and Solr on a cluster


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 ?