The Hydrolix Tunables file contains a number of the configurable settings used platform wide, it also includes settings for platform services such as queue time-outs, Kinesis shard counts, SSH Authorized keys and bucket permissions.
These settings can be updated via two methods:
It is suggested where large numbers of items are required to be updated (for example when enabling bucket access or authorized ssh keys), the updates be completed using the Tunables command.
The Tunables file is a TOML file with a list of name value pairs. A partial example is below:
$ hdxctl tunables get hdxcli-ekmeho6e # autoingest_max_receive_count = 10 # autoingest_queue_timeout = 200 # aws_ssh_key_name = "" # batch_bucket_kms_arn =  # batch_peer_threads = 1 # bucket_allowlist =  bucket_allowlist = [ "bucket1", "bucket2", "bucket3",] # ec2_detailed_monitoring = true # enable_query_auth = false # enable_query_peer_hyperthreading = true # enable_turbine_monitor = true # import_max_receive_count = 1 # import_queue_timeout = 43200 # ip_allowlist = [ "111.2222.333.111/32", "222.111.333.222/32",] ip_allowlist = [ "0.0.0.0/0",] # kafka_tls_ca = "" # kafka_tls_cert = "" # listing_max_receive_count = 1 # listing_queue_timeout = 43200
The Tunables options available for setting are as follows:
The number of times a message is delivered to the queue before being moved to the dead-letter queue. Recommended to be kept as default.
specify the maximum message retention period for the Autoingest Queue.
To add a public key that you have stored on AWS, provide a the key’s AWS name as an argument. Note only one can be provided.
Allow Hydrolix servers to decrypt a source bucket where a customer defined KMS key is required. Takes the ARN
Specify the number of vCPU’s a batch-peer should use for import jobs.
Enables the architecture to access other buckets other than the default deployed bucket.
Turns off additional monitoring for Hydrolix EC2 components.
Enable query authorisation for requests to the query end-point. Currently a place-holder and not in use.
Enable hyperthreading on the query peer.
Allow query components to monitor the Hydrolix query engine, restarting it if it hangs.
The number of times a message is delivered to the import queue before being moved to the dead-letter queue.
Specify the time for an individual job to timeout on the SQS queue, in seconds. Recommended to be kept as default.
Sets IP allow lists on the appropriate security groups (BastionSecurityGroup and ELBSecurityGroup for incoming connections. IP’s are provided as CIDR formations. For example: --ip-allowlist 188.8.131.52/32 --ip-allowlist 184.108.40.206/24. Note: If an allow list doesn’t contain “0.0.0.0/0” then the ip /32 of the nat gateway will get added automatically. This is not additive, any update will overwrite previous configurations.
Allows the addition of a TLS Certificate Authority (CA) for mutual identification of Hydrolix Kafka ingest. PEM Format
Allows the addition of a TLS Certificate for mutual identification of Hydrolix Kafka ingest. PEM format
The number of times a message is delivered to the listing queue before being moved to the dead-letter queue.
Specify the time for an import job to timeout of the SQS queue, in seconds. Recommended to be kept as default.
specify the interval for the Merge process to trigger. Recommended to be kept as default.
The number of times a message is delivered to the merge queue before being moved to the dead-letter queue.
specify the maximum message retention period for the Merge Queue, in seconds. Recommended to be kept as default.
specify the maximum message retention period for the Reaper Queue, in seconds. Recommended to be kept as default.
List of Authorized keys that are deployed to components for SSH access
The number of shards AWS Kinesis is configured to use. This Kinesis stream is used between the stream-head and the stream-peers.
Tags to apply to this cluster, in the format TAG-NAME:TAG-VALUE. See also the further notes on tags.
Enable cloudwatch metrics within Grafana.
The number of threads for each Superset web worker.
Superset web workers that are silent for more than this many seconds are killed and restarted.
When you deploy a new version it uses the latest patched version and stores that version, so that there are no unintentional patch updates. You can also specify a different date in which case you would get the latest patch older than that date. Default recommendation is to leave blank.
The number of workers for handling Superset requests.
Updated 30 days ago