This is an automated email from the ASF dual-hosted git repository.
houston pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/solr-operator.git
The following commit(s) were added to refs/heads/main by this push:
new d527675 Add example on how to trigger manual restart to docs (#354)
d527675 is described below
commit d527675a8de7532c8108dc71bce04dfe69a0e7c7
Author: Nik Osvalds <[email protected]>
AuthorDate: Tue Oct 26 16:09:13 2021 +0100
Add example on how to trigger manual restart to docs (#354)
---
docs/solr-cloud/managed-updates.md | 17 +++++++++++++++++
1 file changed, 17 insertions(+)
diff --git a/docs/solr-cloud/managed-updates.md
b/docs/solr-cloud/managed-updates.md
index 3677665..86ec236 100644
--- a/docs/solr-cloud/managed-updates.md
+++ b/docs/solr-cloud/managed-updates.md
@@ -72,3 +72,20 @@ This maximum is calculated by taking the given, or default,
[`maxPodsUnavailable
- Some replicas in the shard may already be in a non-active state, or
may reside on Solr Nodes that are not "live".
The `maxShardReplicasUnavailable` calculation will take these replicas
into account, as a starting point.
- If a pod contains non-active replicas, and the pod is chosen to be
updated, then the pods that are already non-active will not be double counted
for the `maxShardReplicasUnavailable` calculation.
+
+## Triggering a Manual Rolling Restart
+
+Given these complex requirements, `kubectl rollout restart statefulset` will
generally not work on a SolrCloud.
+
+One option to trigger a manual restart is to change one of the podOptions
annotations. For example you could set this to the date and time of the manual
restart.
+
+
+```yaml
+apiVersion: solr.apache.org/v1beta1
+kind: SolrCloud
+spec:
+ customSolrKubeOptions:
+ podOptions:
+ annotations:
+ manualrestart: "2021-10-20T08:37:00Z"
+```
