Reg: Impact in topic-partition proportion

are all the factors considered? Any small advice can lead us to make a big decision. Thanks in advance, With regards, Gowtham S

Re: Regarding Fairness in choosing topic and partition for an event

Team, we too have these challenges at our end, anyone please guide us. With regards, Gowtham S. On Tue, 1 Dec 2020 at 16:23, girija arumugam wrote: > Team, > We are having a use-case, where a User in an Organisation can send data at > different rates for the event - sending m

Reg: Max number of partitions in a topic

Hi, Can we have 1000 partitions in a Single topic? If not how many partitions will a single topic have at the max? Anyone, please tell. Thanks and regards, Gowtham S

Re: Need Java Reference

Hi All, Please clarify this. Thanks and regards, Gowtham S. On Fri, 2 Oct 2020 at 13:30, Gowtham S wrote: > Hi All, > We require Java references of the codes available in scala (Kafka Repo). > Are there any references available on GitHub or any? > Ex: SocketServer.scala > <

Need Java Reference

ersion of Kafka server-side implementations which are done in scala) Thanks and regards, Gowtham S.

Re: Poll Records Return Zero Records

we can able to increase consumer throughput. With regards, Gowtham S, MCA On Fri, 18 Sep 2020 at 14:07, 子明小友 wrote: > Interesting! > > Liam Clarke-Hutchinson 于 2020年9月18日周五 15:23写道： > > > Hi Gowtham, that output indicates that there is no lag for the consumer > > group

Re: Poll Records Return Zero Records

favor. There are no quota throttles. We are using the default quota configuration. Please let us know if we miss any configuration/metrics to change/listen? With regards, Gowtham S, MCA On Fri, 18 Sep 2020 at 09:51, Shaohan Yin wrote: > Hi Gowtham, > > You could check if there are

Poll Records Return Zero Records

Consumer configuration - fetch.max.bytes=102428800 - fetch.min.bytes=1 - receive.buffer.bytes=-1 - max.partition.fetch.bytes=102428800 - max.poll.records=1000 Can anyone help us to resolve this? Thanks and regards, Gowtham S, MCA

Re: Reg: Dual Kafka Clients - Issues with jar version conflicts

ethodError: org.apache.kafka.common.record.Record.recordSize([B[B)I Thanks and regards, Gowtham S, MCA On Wed, 15 Apr 2020 at 19:32, Nicolas Carlot wrote: > What do you mean by communication between Kafka Clients ? > A Client is either a producer or a consumer, they don't "commu

Re: Reg: Dual Kafka Clients - Issues with jar version conflicts

Hello, It will be helpful if anyone suggests solutions. Thanks and regards, Gowtham S, MCA On Tue, 7 Apr 2020 at 12:31, Gowtham S wrote: > > Hello, > > As per our team requirements, we are supposed to use and communicate > between two different Kafka Clients, provided and

Reg: Dual Kafka Clients - Issues with jar version conflicts

possible to use them without compatibility issues. Is it necessary to move the topics to a single Kafka? If necessary to upgrade the clients, suggest the best practices for the same. With regards, Gowtham S, MCA

Re: Reg: Guidance for Machine Capacity Plan

Hi George, The 90Mb/s, how did you calculate that? We are expecting 360 messages (events) per second across all topics we have. One event size = 256Kb With regards, Gowtham S, MCA On Wed, 19 Feb 2020 at 11:01, George wrote: > Hi there > > with regard to "> Can you please

Re: Reg: Guidance for Machine Capacity Plan

Thanks, George and Alexandre for the reply. George, to answer your question > How did you get to 90MB/s - this is our expected throughput. For the RAM size and CPU count? > Can you please suggest me how to calculate this! With regards, Gowtham S, MCA PH: 9597000673 On Wed, 19 Fe

Re: Reg: Guidance for Machine Capacity Plan

Hi, Please help/guide me to identify the size of the cluster. Thanks and Regards, Gowtham S. On Fri, 24 Jan 2020 at 14:31, Gowtham S wrote: > Hi, > > We are in the process of deploying Kafka in our service. We need to decide > the machine capacity plan, we arrived at the below

Reg: Guidance for Machine Capacity Plan

Hi, We are in the process of deploying Kafka in our service. We need to decide the machine capacity plan, we arrived at the below formulae for deriving total machine capacity. Total Broker machine size = Message size per second * Retention period * Replication Factor Am I need to consider the