joshsouza commented on issue #471: URL: https://github.com/apache/solr-operator/issues/471#issuecomment-1247042942
Just had a thought on this after perusing the docs further to see if there's anything I could find to support our end goals within current constraints: https://kubernetes.io/docs/tasks/run-application/configure-pdb/#specifying-a-poddisruptionbudget I can specify a disruption `maxUnavailable` of `0`. This will _prevent any voluntary disruptions_ entirely. So if the operator managed the PDB, and set the `maxUnavailable` to, for example `1`, as long as every shard is happy, but when it detects that there are shards in a recovering state where an additional pod going down risks reliability, it can adjust the PDB to set `maxUnavailable` to `0` until that condition passes, then we could prevent additional eviction behavior until it's safe. I think this is a potentially viable solution until the platform supports multiple PDB's on a pod. What do you think? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For additional commands, e-mail: issues-h...@solr.apache.org
