Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add example on how to trigger manual restart to docs #354

Merged
merged 2 commits into from
Oct 26, 2021
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 17 additions & 0 deletions docs/solr-cloud/managed-updates.md
Original file line number Diff line number Diff line change
Expand Up @@ -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"
```