You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -402,23 +402,23 @@ Use NetworkPolicy to control network traffic flow for your applications, it allo
402
402
403
403
## Pod Priorty
404
404
405
-
Pods can be assigned priority that reflects the signifance of a pod compared to other pods. For detailed explanation, please refer [https://kubernetes.io/docs/concepts/scheduling-eviction/pod-priority-preemption/](https://kubernetes.io/docs/concepts/scheduling-eviction/pod-priority-preemption/)
405
+
Pods can be assigned priority that reflects the significance of a pod compared to other pods. If a pod cannot be scheduled, the scheduler will attempt to evict lower-priority pods in order to free up resources and allow high-priority pods to be scheduled. Assigning priority to pods is important to make sure high-priority pods are not preempted and get the required resources. It is highly recommended to set a PriorityClass object with the highest possible value for MarkLogic Pods to ensure the availability of the database.
406
+
For more details on Pod priority and PriorityClass, please refer [https://kubernetes.io/docs/concepts/scheduling-eviction/pod-priority-preemption/](https://kubernetes.io/docs/concepts/scheduling-eviction/pod-priority-preemption/)
406
407
407
-
To add priority for pods, use the following the steps:
408
+
To assign priority for pods, use the following the steps:
408
409
409
-
1. Add a PriorityClass. Following is an example of PriorityClass:
410
+
1. Add a PriorityClass. Following is an example of PriorityClass with a value of 1 million for MarkLogic pods:
410
411
```
411
412
apiVersion: scheduling.k8s.io/v1
412
413
kind: PriorityClass
413
414
metadata:
414
415
name: high-priority
415
416
value: 1000000
416
417
globalDefault: false
417
-
description: "This high priority class should be used for MarkLogic service pods only."
418
+
description: "This high priority class should be used for MarkLogic pods only."
418
419
```
419
-
For more details and examples, refer [https://kubernetes.io/docs/concepts/scheduling-eviction/pod-priority-preemption/#priorityclass](https://kubernetes.io/docs/concepts/scheduling-eviction/pod-priority-preemption/#priorityclass)
420
420
421
-
2. Set priorityClassName in the values.yaml file or using --set flag while installing the chart. Value of priorityClassName should be set to one of the added PriorityClassName.
421
+
2. Set priorityClassName in the values.yaml file or using the --set flag while installing the chart. The value of priorityClassName should be set to one of the added PriorityClassName.
0 commit comments