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
fix!: Remove unused PVCs which caused problems (#769)
* fix!: Remove unused PVCs which caused problems
* changelog
* docs: Document why we need to provide an empty struct
* remove missleading leftover comment
* Update tests and docs
Copy file name to clipboardExpand all lines: CHANGELOG.md
+11Lines changed: 11 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -39,6 +39,16 @@ All notable changes to this project will be documented in this file.
39
39
40
40
- Use `json` file extension for log files ([#733]).
41
41
- Fix a bug where changes to ConfigMaps that are referenced in the TrinoCluster spec didn't trigger a reconciliation ([#734]).
42
+
- BREAKING: The PersistentVolumeClaims for coordinator and workers have been removed ([#769])
43
+
- They caused problems, as Trino kept it's process ID in `/stackable/data/var/run/launcher.pid`.
44
+
A forceful stop (e.g. OOMKilled) could result in a leftover PID in this file.
45
+
In this case Trino would refuse startup with `trino ERROR: already running as 21`.
46
+
As the PersistentVolumeClaims didn't store any actual data, they have been removed.
47
+
- Upgrading will result in the error message `Failed to reconcile object [...]: Forbidden: updates to statefulset spec for fields other than [...] are forbidden`
48
+
as Kubernetes currently does not allow changing the `volumeClaimTemplates` field. Simply delete the mentioned StatefulSet, the operator will re-create it.
49
+
- You might want to clean up now useless PVCs.
50
+
Tip: You can list all Trino-related PVCs using `kubectl get pvc -l app.kubernetes.io/name=trino`.
51
+
- The `.spec.(coordinators|workers).config.resources.storage.data` field has been removed, as it's not needed anymore.
42
52
43
53
### Removed
44
54
@@ -58,6 +68,7 @@ All notable changes to this project will be documented in this file.
Copy file name to clipboardExpand all lines: docs/modules/trino/pages/usage-guide/configuration.adoc
+1-36Lines changed: 1 addition & 36 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -108,36 +108,7 @@ workers:
108
108
109
109
Here too, overriding properties such as `http-server.https.port` will lead to broken installations.
110
110
111
-
== Resources
112
-
113
-
=== Storage for data volumes
114
-
115
-
You can mount a volume where data (config and logs of Trino) is stored by specifying https://kubernetes.io/docs/concepts/storage/persistent-volumes[PersistentVolumeClaims] for each individual role or role group:
116
-
117
-
[source,yaml]
118
-
----
119
-
workers:
120
-
config:
121
-
resources:
122
-
storage:
123
-
data:
124
-
capacity: 2Gi
125
-
roleGroups:
126
-
default:
127
-
config:
128
-
resources:
129
-
storage:
130
-
data:
131
-
capacity: 3Gi
132
-
----
133
-
134
-
In the above example, all Trino workers in the default group store data (the location of the property `--data-dir`) on a `3Gi` volume.
135
-
Additional role groups not specifying any resources inherit the config provided on the role level (`2Gi` volume).
136
-
This works the same for memory or CPU requests.
137
-
138
-
By default, in case nothing is configured in the custom resource for a certain role group, each Pod has a `2Gi` large local volume mount for the data location containing mainly logs.
0 commit comments