Pravega has many configuration options for setting up metrics, tuning, etc. The available options can be found here and are expressed through the pravega/options part of the resource specification.
All values must be expressed as Strings.
...
spec:
pravega:
options:
metrics.statistics.enable: "true"
metrics.statsD.connect.host: "telegraph.default"
metrics.statsD.connect.port: "8125"
...
It is also possible to tune the JVM options for Pravega Controller and Segmentstore. Pravega JVM options are for configuring Controller & Segmenstore JVM process whereas Pravega options are for configuring Pravega software.
Here is an example,
...
spec:
pravega:
controllerjvmOptions: ["-Xms1g", "-Xmx1g", "-XX:+ExitOnOutOfMemoryError", "-XX:+CrashOnOutOfMemoryError", "-XX:+HeapDumpOnOutOfMemoryError"]
segmentStoreJVMOptions: ["-Xms4g", "-Xmx4g", "-XX:MaxDirectMemorySize=11g", "-XX:+ExitOnOutOfMemoryError", "-XX:+CrashOnOutOfMemoryError", "-XX:+HeapDumpOnOutOfMemoryError"]
...
We do not provide any JVM options as defaults within the operator code for the Controller or the Segment Store. These options can be passed into the operator through the deployment manifest. Also we recommend setting both -Xms and -Xmx to the same value (as shown in the example above) so as to ensure that we save up the JVM growing memory.
NOTE: For setting Segment Store options -XX:MaxDirectMemorySize, -Xmx and pravegaservice.cache.size.max, follow the guidelines provided in this document.
It is possible to add additional parameters into the SegmentStore container by allowing users to create a custom ConfigMap or a Secret and specifying their name within the Pravega manifest. However, the user needs to ensure that the following keys which are present in SegmentStore ConfigMap which is created by the Pravega Operator should not be a part of the custom ConfigMap.
- AUTHORIZATION_ENABLED
- CLUSTER_NAME
- ZK_URL
- JAVA_OPTS
- CONTROLLER_URL
- WAIT_FOR
- K8_EXTERNAL_ACCESS
- log.level