What's a Kafka partition made of?
Kafka partitions are made of segments (usually each segment is 1GB), and each segment has two corresponding indexes (offset index and time index)
You are using JDBC source connector to copy data from 3 tables to three Kafka topics. There is one connector created with max.tasks equal to 2 deployed on a cluster of 3 workers. How many tasks are launched?
here, we have three tables, but the max.tasks is 2, so that's the maximum number of tasks that will be created
You are sending messages with keys to a topic. To increase throughput, you decide to increase the number of partitions of the topic. Select all that apply.
Increasing the number of partition causes new messages keys to get hashed differently, and breaks the guarantee 'same keys goes to the same partition'. Kafka logs are immutable and the previous messages are not re-shuffled
To allow consumers in a group to resume at the previously committed offset, I need to set the proper value for...
Setting a group.id that's consistent across restarts will allow your consumers part of the same group to resume reading from where offsets were last committed for that group
A producer is sending messages with null key to a topic with 6 partitions using the DefaultPartitioner. Where will the messages be stored?
Message with no keys will be stored with round-robin strategy among partitions.