Re: What is the benefit of using acks=all and minover e.g. acks=3

2015-12-01 Thread Andreas Flinck
ll the parameters, num.replica.fetchers should be kept higher to 4 can be of help. Please try it out and let us know if it worked Thanks, Prabhjot On Nov 28, 2015 4:59 PM, "Andreas Flinck" mailto:andreas.fli...@digitalroute.com>> wrote: Hi! Here are our settings for th

SV: What is the benefit of using acks=all and minover e.g. acks=3

2015-11-28 Thread Andreas Flinck
r.bytes": 10485760, Similarly, please share your producer config as well. I'm thinking may be it is related to tuning your cluster. Thanks, Prabhjot On Sat, Nov 28, 2015 at 3:54 PM, Andreas Flinck < andreas.fli...@digitalroute.com> wrote: > Great, thanks for the informatio

Re: What is the benefit of using acks=all and minover e.g. acks=3

2015-11-28 Thread Andreas Flinck
gt; messages. >>>> >>>> acks = all requires all ISR to ack as long as they are in the ISR, >>>> protecting you from this scenario (but leading to high latency if a >>> replica >>>> is hanging and is just about to drop out of the ISR). >>>>

What is the benefit of using acks=all and minover e.g. acks=3

2015-11-27 Thread Andreas Flinck
Hi all The reason why I need to know is that we have seen an issue when using acks=all, forcing us to quickly find an alternative. I leave the issue out of this post, but will probably come back to that! My question is about acks=all and min.insync.replicas property. Since we have found a wor