Hey Mohit, I agree with Hans, and additionally you may have trouble when the cluster needs to rebalance its partitions or when partition leadership changes node.
Also you may loose high-availability and cluster resilience in case of fail-over. Cheers João Reis On 23 Aug 2017, at 08:42, Mohit Chawla <mohit.chawla.bin...@gmail.com<mailto:mohit.chawla.bin...@gmail.com>> wrote: Hey Hans, Thanks for your reply. In a cloud environment this can be useful. Perhaps if partitioning and replicas are selected appropriately, this could be possible ? Thanks, Mohit On Tuesday, August 22, 2017, Hans Jespersen <h...@confluent.io<mailto:h...@confluent.io>> wrote: Doing that doesn't really make sense in a Kafka cluster because the topic partitions and their replicas are spread out across many brokers in the cluster. That's what enables the parallel processing and fault tolerance features of Kafka. -hans On Aug 22, 2017, at 3:14 AM, Mohit Chawla <mohit.chawla.bin...@gmail.com<mailto:mohit.chawla.bin...@gmail.com> <javascript:;>> wrote: Hi folks, Is it possible to pin kafka clients to use only specific brokers throughout their lifetime and not just for the initial bootstrapping ? Thanks, Mohit ______________________________________________________________________ This email has been scanned by the Symantec Email Security.cloud service. For more information please visit http://www.symanteccloud.com<http://www.symanteccloud.com/> ______________________________________________________________________ ______________________________________________________________________ This email has been scanned by the Symantec Email Security.cloud service. For more information please visit http://www.symanteccloud.com ______________________________________________________________________
