Advanced topic parameters for Aiven for Apache Kafka® Inkless

View the topic-level configuration options for Inkless in Aiven for Apache Kafka®. These configurations apply to Inkless Kafka on Aiven Cloud.

cleanup_policy string enum: compact,delete The retention policy to use on old segments. Possible values include 'delete', 'compact', or a comma-separated list of them. The default policy ('delete') will discard old segments when their retention time or size limit has been reached. The 'compact' setting will enable log compaction on the topic.

delete_retention_ms integer min: 60000 max: 604800000 The amount of time to retain delete tombstone markers for log compacted topics. This setting also gives a bound on the time in which a consumer must complete a read if they begin from offset 0 to ensure that they get a valid snapshot of the final stage (otherwise delete tombstones may be collected before they complete their scan).

max_message_bytes integer min: 0 max: 20971520 The largest record batch size allowed by Kafka (after compression if compression is enabled). If this is increased and there are consumers older than 0.10.2, the consumers' fetch size must also be increased so that the they can fetch record batches this large. In the latest message format version, records are always grouped into batches for efficiency. In previous message format versions, uncompressed records are not grouped into batches and this limit only applies to a single record in that case.

message_timestamp_after_max_ms integer min: 0 max: 9223372036854775807 The maximum difference allowed between the timestamp when a broker receives a message and the timestamp specified in the message. If message.timestamp.type=CreateTime, a message will be rejected if the difference in timestamp exceeds this threshold. Applies only for messages with timestamps later than the broker's timestamp.

message_timestamp_before_max_ms integer min: 0 max: 9223372036854775807 The maximum difference allowed between the timestamp when a broker receives a message and the timestamp specified in the message. If message.timestamp.type=CreateTime, a message will be rejected if the difference in timestamp exceeds this threshold. Applies only for messages with timestamps earlier than the broker's timestamp.

message_timestamp_type string enum: CreateTime,LogAppendTime Define whether the timestamp in the message is message create time or log append time.

min_insync_replicas integer min: 0 max: 2 When a producer sets acks to 'all' (or '-1'), this configuration specifies the minimum number of replicas that must acknowledge a write for the write to be considered successful. If this minimum cannot be met, then the producer will raise an exception (either NotEnoughReplicas or NotEnoughReplicasAfterAppend). When used together, min.insync.replicas and acks allow you to enforce greater durability guarantees. A typical scenario would be to create a topic with a replication factor of 3, set min.insync.replicas to 2, and produce with acks of 'all'. This will ensure that the producer raises an exception if a majority of replicas do not receive a write.

retention_bytes integer min: -1 max: 9223372036854775807 This configuration controls the maximum size a partition (which consists of log segments) can grow to before we will discard old log segments to free up space if we are using the 'delete' retention policy. By default there is no size limit only a time limit. Since this limit is enforced at the partition level, multiply it by the number of partitions to compute the topic retention in bytes.

unclean_leader_election_enable boolean Indicates whether to enable replicas not in the ISR set to be elected as leader as a last resort, even though doing so may result in data loss.

retention_ms integer range: -1 or between 60000 and 9223372036854775807 min: -1 This configuration controls the maximum time we will retain a log before we will discard old log segments to free up space if we are using the 'delete' retention policy. This represents an SLA on how soon consumers must read their data. If set to -1, no time limit is applied.

diskless_enable boolean Indicates whether diskless should be enabled. This is only available for BYOC services with Diskless feature enabled.

remote_storage_enable boolean Indicates whether tiered storage should be enabled. This is only available for services with Tiered Storage feature enabled.