Thanks for the lecture! In your explanation, either for the range or round robin assignor, the order of consumers plays an important role here. Can I assume that consumers are always ordered by the time it is created? For example, consumer 1 is always created earlier than consumer 2 and consumer 2 is always created earlier than consumer 3.
Actually order is not imp Chen Guo, like in case of range assignor, for order change max to max , consumer 1 may get 3,4,5 & consumer 2 get 0,1,2 in that case instead of consumer 1 getting 0,1,2 & consumer 2 getting 3,4,5 , but ultimately both are range assignor .. similarly , in case of round robin assignor , consumer 1 getting 0,2,4 & consumer 2 getting 1,3,5 or consumer 1 getting 1,3,5 and consumer 2 getting 0,2,4 does not matter , but point to be noted in both case , the partitions are distributed in round robin fashion what will ultimately result into efficient faster execution in consumer side ... Hope you got it ....
Hi , @Knowledge Amplifier, Thanks for all the amazing content!!! My request for the content is to on-premises data migration from oracle to snowflake using AWS. Can you please create any such content , or if you already created plz share the link for the same.
Hi KnowlegeAmplifier1 , I have issue with consumer group member where it has only 2 members out of 3 brokers I have , sometimes only one member , so when the cordinator broker goes down that consumer group is useless, how do I fix this?
Thanks for your great efforts and nice explanation, Please make a video on Kafka monitoring tools Prometheus & Grafana
Thanks for the lecture! In your explanation, either for the range or round robin assignor, the order of consumers plays an important role here. Can I assume that consumers are always ordered by the time it is created? For example, consumer 1 is always created earlier than consumer 2 and consumer 2 is always created earlier than consumer 3.
Actually order is not imp Chen Guo, like in case of range assignor, for order change max to max , consumer 1 may get 3,4,5 & consumer 2 get 0,1,2 in that case instead of consumer 1 getting 0,1,2 & consumer 2 getting 3,4,5 , but ultimately both are range assignor .. similarly , in case of round robin assignor , consumer 1 getting 0,2,4 & consumer 2 getting 1,3,5 or consumer 1 getting 1,3,5 and consumer 2 getting 0,2,4 does not matter , but point to be noted in both case , the partitions are distributed in round robin fashion what will ultimately result into efficient faster execution in consumer side ... Hope you got it ....
Hi , @Knowledge Amplifier, Thanks for all the amazing content!!! My request for the content is to on-premises data migration from oracle to snowflake using AWS. Can you please create any such content , or if you already created plz share the link for the same.
Hi KnowlegeAmplifier1 , I have issue with consumer group member where it has only 2 members out of 3 brokers I have , sometimes only one member , so when the cordinator broker goes down that consumer group is useless, how do I fix this?
can you explain this question in detail?