This guide lists some of the supported advanced parameters that allow you to configure your Cloud Analytics with Kafka® Connect according to your use cases.
Requirements
- A Public Cloud project in your OVHcloud account
- A Kafka® Connect service running on your OVHcloud Cloud Analytics (this guide can help you to meet this requirement)
- Access to your OVHcloud Control Panel or the OVHcloud API
Instructions
NOTE: The management of advanced parameters is not supported via Terraform.
Using the OVHcloud Control Panel
Please refer to this guide to find out how to change your advanced parameters from the OVHcloud Control Panel.
Using API
Please refer to this guide to find out how to change your advanced parameters from the OVHcloud API.
Advanced parameters for Kafka® Connect
You can find a complete list of configuration options via OVHcloud API. Below is a summary of some configuration options available for Kafka® Connect service:
| Parameters |
|---|
kafka_connect.connector_client_config_override_policy stringvalues: All, NoneDefines what client configurations can be overridden by the connector. Default is None |
kafka_connect.consumer_auto_offset_reset stringvalues: earliest, latestWhat to do when there is no initial offset in Kafka or if the current offset does not exist any more on the server. Default is earliest |
kafka_connect.consumer_fetch_max_bytes longmin: 1048576 max: 104857600Records are fetched in batches by the consumer, and if the first record batch in the first non-empty partition of the fetch is larger than this value, the record batch will still be returned to ensure that the consumer can make progress. As such, this is not a absolute maximum. |
kafka_connect.consumer_isolation_level stringvalues: read_committed, read_uncommittedTransaction read isolation level. read_uncommitted is the default, but read_committed can be used if consume-exactly-once behavior is desired. |
kafka_connect.consumer_max_partition_fetch_bytes longmin: 1048576 max: 104857600Records are fetched in batches by the consumer.If the first record batch in the first non-empty partition of the fetch is larger than this limit, the batch will still be returned to ensure that the consumer can make progress. |
kafka_connect.consumer_max_poll_interval_ms longmin: 1 max: 2147483647The maximum delay in milliseconds between invocations of poll() when using consumer group management (defaults to 300000). |
kafka_connect.consumer_max_poll_records longmin: 1 max: 10000The maximum number of records returned in a single call to poll() (defaults to 500). |
kafka_connect.offset_flush_interval_ms longmin: 1 max: 100000000The interval at which to try committing offsets for tasks (defaults to 60000). |
kafka_connect.offset_flush_timeout_ms longmin: 1 max: 2147483647Maximum number of milliseconds to wait for records to flush and partition offset data to be committed to offset storage before cancelling the process and restoring the offset data to be committed in a future attempt (defaults to 5000). |
kafka_connect.producer_batch_size longmin: 0 max: 5242880This setting gives the upper bound of the batch size to be sent. If there are fewer than this many bytes accumulated for this partition, the producer will 'linger' for the linger.ms time waiting for more records to show up. A batch size of zero will disable batching entirely (defaults to 16384). |
kafka_connect.producer_buffer_memory longmin: 5242880 max: 134217728The total bytes of memory the producer can use to buffer records waiting to be sent to the broker (defaults to 33554432). |
kafka_connect.producer_compression_type stringvalues: gzip, lz4, none, snappy, zstdSpecify the default compression type for producers. This configuration accepts the standard compression codecs ('gzip', 'snappy', 'lz4', 'zstd'). It additionally accepts 'none' which is the default and equivalent to no compression. |
kafka_connect.producer_linger_ms longmin: 0 max: 5000This setting gives the upper bound on the delay for batching: once there is batch.size worth of records for a partition it will be sent immediately regardless of this setting, however if there are fewer than this many bytes accumulated for this partition the producer will 'linger' for the specified time waiting for more records to show up. Defaults to 0. |
kafka_connect.producer_max_request_size longmin: 131072 max: 67108864This setting will limit the number of record batches the producer will send in a single request to avoid sending huge requests. |
kafka_connect.scheduled_rebalance_max_delay_ms longmin: 0 max: 600000The maximum delay that is scheduled in order to wait for the return of one or more departed workers before rebalancing and reassigning their connectors and tasks to the group. During this period the connectors and tasks of the departed workers remain unassigned. Defaults to 5 minutes. |
kafka_connect.session_timeout_ms longmin: 1 max: 2147483647The timeout in milliseconds used to detect failures when using Kafka’s group management facilities (defaults to 10000). |
Go further
For more information and tutorials, please see our other Managed Databases & Analytics or Platform as a Service guides. You can also explore the guides for other OVHcloud products and services.
OVHcloud Managed Databases and Analytics:
- Grafana® is a registered trademark of Grafana Labs and is used with the permission of Grafana Labs. OVH SAS and its subsidiaries are not affiliated with or endorsed by Grafana Labs.
- Kafka® is a registered trademark of The Apache Software Foundation and has been licensed for use by OVHcloud, who has no affiliation with and is not endorsed by The Apache Software Foundation.
- MongoDB® is a registered trademark of MongoDB, Inc.
- MySQL® is a registered trademark of Oracle and/or its affiliates.
- PostgreSQL® is a registered trademark of the PostgreSQL Community Association of Canada.