Expose Kafka Config Parameters in SIP Container Environment

We request IBM to expose and allow configuration of the following parameters in the SIP container environment. While we understand IBM’s concern regarding potential application performance impact, these parameters do not always behave uniformly across all environments. Allowing flexibility will help us optimize performance and cost.

Business Justification

• Compression: Many clients in Adidas successfully use compression on the client side without any negative impact. Not enabling compression is costing extra money to adidas due to increased traffic and disk usage.
• Batching & Traffic Optimization: Adjusting batching parameters will reduce network overhead and disk consumption.
• Timeout Issues in Production Environment: Current disconnection issues suggest the need for tuning idle and metadata-related timeouts.

Requested Configurations:

1. Optimizing Batching / Traffic / Disk Usage

compression.type = lz4
linger.ms = 20   (for one producer; another producer uses 100)
batch.size = 262144

2. Addressing Timeout Issues

connections.max.idle.ms = 180000
metadata.max.age.ms = 15000
metadata.max.idle.ms = 15000
metadata.recovery.rebootstrap.trigger.ms = 15000

Expected Outcome:

• Reduced traffic and disk usage through compression and batching.
• Improved stability in Production environments by mitigating disconnection issues.