Re: Queue implementation

t; > So while connecting topic T1 with 3 consumer c1,c2,c3 all will have >> >>the >> >> > same group id so only one of the consumer will receive the >>message at >> >> > time. >> >> > >> >> > Same we can do with other t

Re: Queue implementation

consumer will receive the message at > >> > time. > >> > > >> > Same we can do with other topic and rest of the consumer > >> > > >> > Thanks > >> > Gaurav > >> > On Mar 29, 2016 9:20 AM, "Vinod Kakad" wrote:

Re: Queue implementation

while connecting topic T1 with 3 consumer c1,c2,c3 all will have >>the >> > same group id so only one of the consumer will receive the message at >> > time. >> > >> > Same we can do with other topic and rest of the consumer >> > >> > Thanks

Re: Queue implementation

he consumer > > > > Thanks > > Gaurav > > On Mar 29, 2016 9:20 AM, "Vinod Kakad" wrote: > > > > > Can we have multiple topics and multiple consumers but in a queue > > > implementation. > > > > > > for e.g. > > > Th

Re: Queue implementation

one of the consumer will receive the message at > time. > > Same we can do with other topic and rest of the consumer > > Thanks > Gaurav > On Mar 29, 2016 9:20 AM, "Vinod Kakad" wrote: > > > Can we have multiple topics and multiple consumers but in a queue &g

Re: Queue implementation

with other topic and rest of the consumer Thanks Gaurav On Mar 29, 2016 9:20 AM, "Vinod Kakad" wrote: > Can we have multiple topics and multiple consumers but in a queue > implementation. > > for e.g. > There are 2 topics T1 and T2 and four consumers C1,C2,C3 and C4.

Re: Queue implementation

, Vinod Kakad wrote: > Can we have multiple topics and multiple consumers but in a queue > implementation. > > for e.g. > There are 2 topics T1 and T2 and four consumers C1,C2,C3 and C4. > > can we have C1,C2,C3 subscribe to T1 and (C3,C4) subscribe to T2. and this > shoul

Re: Queue implementation

Can we have multiple topics and multiple consumers but in a queue implementation. for e.g. There are 2 topics T1 and T2 and four consumers C1,C2,C3 and C4. can we have C1,C2,C3 subscribe to T1 and (C3,C4) subscribe to T2. and this should work like a queue. i.e. T2 should send message to only C3

Re: Queue implementation

5:19 PM, Vinod Kakad wrote: > > > Can anybody share any good example(code) for kafka as a queue > > implementation? > > > > Thanks & Regards, > > Vinod Kakad. > > > > > > -- > -- > Sharninder >

Re: Queue implementation

at 5:19 PM, Vinod Kakad wrote: > > > Can anybody share any good example(code) for kafka as a queue > > implementation? > > > > Thanks & Regards, > > Vinod Kakad. > > > > > > -- > -- > Sharninder > -- Regards Vamsi Subhash

Re: Queue implementation

What kind of queue are you looking for? Kafka works as a nice FIFO queue by default anyway. On Mon, Mar 28, 2016 at 5:19 PM, Vinod Kakad wrote: > Can anybody share any good example(code) for kafka as a queue > implementation? > > Thanks & Regards, > Vinod Kakad. > -- -- Sharninder

Queue implementation

Can anybody share any good example(code) for kafka as a queue implementation? Thanks & Regards, Vinod Kakad.

Re: [New Feature Request] Ability to Inject Queue Implementation Async Mode

Thank you all for the comments. Yes, I understand concern from community members with extra burden of having the complexity to drop message, but if ability to inject implementation of the Queue which will make this completely transparent to Kafka. I just need fine-grained control of the applicati

Re: [New Feature Request] Ability to Inject Queue Implementation Async Mode

Policies for which messages to drop, retain, etc seem like something you should code in your application. I personally would not like to see this extra complexity added to Kafka. Philip -- http://www.philipotoole.com > On Aug 7, 2014, at 2:44 PM, Bhavesh Mistry

Re: [New Feature Request] Ability to Inject Queue Implementation Async Mode

Basically, requirement is to support message dropping policy in event when queue is full. When you get storm of data (in our case logging due to buggy application code), we would like to retain current message instead of first one in queue. We will mitigate this by rate limiting on producer side

Re: [New Feature Request] Ability to Inject Queue Implementation Async Mode

Is it possible there is another solution to the problem? I think if you could better describe the problem(s) you are facing and how you are architected some then you may get responses from others that perhaps have faced the same problem with similar architectures ... or maybe folks can chime in wit

[New Feature Request] Ability to Inject Queue Implementation Async Mode

Kafka Version: 0.8.x 1) Ability to define which messages get drooped (least recently instead of most recent in queue) 2) Try Unbounded Queue to find out the Upper Limit without drooping any messages for application (use case Stress test) 3) Priority Blocking Queue ( meaning a single Producer can