Best practice guidelines


  • Based on our validation, NFS is not the right protocol for a Confluent Kafka broker to keep data.

  • We can use SAN (specifically FC) to keep the broker data or local disk, because, in the Confluent tiered storage configuration, the size of the data held in the brokers data directory is based on the segment size and retention time when the data is moved to object storage.

  • Object stores provide better performance when segment.bytes is higher; we tested 512MB.

  • In Kafka, the length of the key or value (in bytes) for each record produced to the topic is controlled by the length.key.value parameter. For StorageGRID, S3 object ingest and retrieve performance increased to higher values. For example, 512 bytes provided a 5.8GBps retrieve, 1024 bytes provided a 7.5GBps s3 retrieve, and 2048 bytes provided close to 10GBps.

The following figure presents the S3 object ingest and retrieve based on length.key.value.

Error: Missing Graphic Image