Dataserver#
The following table contains the list of custom properties that can be configured for Dataserver. To use a custom property from the table, just add it to the following YML file in the custom-vars folder configured as per your environment:
- vars.dataserver.aws.yml
- vars.dataserver.azure.yml
- vars.dataserver.gcp.yml
| Property | Description | Values | Default Value |
|---|---|---|---|
| DATASERVER_HTTP_PORT | Property to change the default port number for a non-secured Dataserver. | 8181 | |
| DATASERVER_PROXY_SSL | Set the property to enable/disable DataServer Proxy SSL | true, false | true |
| DATASERVER_HTTPS_PORT | Property to change the default port number for a secured Dataserver. | 8282 | |
| DATASERVER_SSL_SELF_SIGNED | Set the value of the property to false to use signed certificate for DataServer. |
true | |
| DATASERVER_HOST_NAME | Signed DNS name for DataServer. | ||
| DATASERVER_SSL_SIGNED_PEM_FULL_CHAIN | The SSL certificates chain that consists of root certificates and intermediate certificate. | ||
| DATASERVER_SSL_SIGNED_PEM_PRIVATE_KEY | Signed certificate authority private key. | ||
| DATASERVER_SSL_SIGNED_CERT_FORMAT | Signed certificate key format. The format is .pem. |
||
| DATASERVER_DATABRICKS_ALLOWED_URLS |
Property accepts a comma-separated list of allowable Databricks URLs. For example:
|
||
| DATASERVER_V2_WORKDER_THREADS | Number of worker threads to process inbound connection. | 20 | |
| DATASERVER_V2_CHANNEL_CONNECTION_BACKLOG | Maximum queue size for inbound connection. | 128 | |
| DATASERVER_V2_CHANNEL_CONNECTION_POOL | Enable connection pool for outbound request. | true, false | false |
| DATASERVER_V2_FRONT_CHANNEL_IDLE_TIMEOUT | Idle timeout for inbound connection. | 60 | |
| DATASERVER_V2_BACK_CHANNEL_IDLE_TIMEOUT | Idle timeout for outbound connection and will take effect only if the connection pool enabled. | 60 | |
| Memory Variables | |||
| DATASERVER_HEAP_MIN_MEMORY_MB | Minimum Java Heap memory in MB used by Dataserver. For example, DATASERVER_HEAP_MIN_MEMORY_MB: "1024" | ||
| DATASERVER_HEAP_MIN_MEMORY | Minimum Java Heap memory used by Dataserver. Setting this value will override DATASERVER_HEAP_MIN_MEMORY_MB. For example, DATASERVER_HEAP_MIN_MEMORY: "1g" | ||
| DATASERVER_HEAP_MAX_MEMORY_MB | Maximum Java Heap memory in MB used by Dataserver. For example, DATASERVER_HEAP_MAX_MEMORY_MB: "1024" | ||
| DATASERVER_HEAP_MAX_MEMORY | Maximum Java Heap memory used by Dataserver. Setting this value will override DATASERVER_HEAP_MAX_MEMORY_MB. For example, DATASERVER_HEAP_MAX_MEMORY: "1g" | ||
| DATASERVER_K8S_MEM_REQUESTS_MB | Minimum amount of Kubernetes memory in MB to be requested by Dataserver. For example, DATASERVER_K8S_MEM_REQUESTS_MB: "1024" | ||
| DATASERVER_K8S_MEM_REQUESTS | Minimum amount of Kubernetes memory to be used by Dataserver. Setting this value will override DATASERVER_K8S_MEM_REQUESTS_MB. For example, DATASERVER_K8S_MEM_REQUESTS: "1G" | ||
| DATASERVER_K8S_MEM_LIMITS_MB | Maximum amount of Kubernetes memory in MB to be requested by Dataserver. For example, DATASERVER_K8S_MEM_LIMITS_MB: "1024" | ||
| DATASERVER_K8S_MEM_LIMITS | Maximum amount of Kubernetes memory to be used by Dataserver. Setting this value will override DATASERVER_K8S_MEM_LIMITS_MB. For example, DATASERVER_K8S_MEM_LIMITS: "1G" | ||
| DATASERVER_CPU_MIN | Minimum amount of Kubernetes CPU to be requested by Dataserver. For example, DATASERVER_CPU_MIN: "0.5" | ||
| DATASERVER_CPU_MAX | Maximum amount of Kubernetes CPU to be used by Dataserver. For example, DATASERVER_CPU_MAX: "0.5" | ||
Last update: September 24, 2021