Re: Kafka Monitoring

Ok thank you Michal On Tue, Dec 12, 2017 at 9:30 PM, Michal Michalski < michal.michal...@zalando.ie> wrote: > Hi Irtiza, > > Unfortunately I don't know what could be the issue in your case - in my > case all these metrics simply appear under appropriate keys > (e.g. "kafka.controller") in the

Re: Strange rebalancing exception in Kafka 1.0.0

Hi All, Any pointers to the above issue that I can explore further. -Sameer. On Tue, Dec 12, 2017 at 5:40 PM, Sameer Kumar wrote: > HI Ismael, > > This is what I see in the logs, I tried this twice and got the same > exception. > > This is only reproducible when I have

Using Bootstrap Server List for data center failover

Hi, If we have two data centers, one with a passive Kafka cluster and one with an active Kafka cluster, would listing the Kafka servers for both clusters as the bootstrap servers for our consumer apps cause any trouble? We were thinking about doing this to avoid the need to reconfigure out

Connectors Information from Microsoft SQL Server to Kafka

Hi Team, We have a requirement of replicating the data from MSSQL Source database to MSSQL target database. We are using SQL Server 2014 Web edition as the source database and target database as well. We want to replicate the data from Source database to target database realtime. Enabled the

Re: ConcurrentModificationException

Since you're running Storm to read data from Kafka, I'd expect it is not due to 6349. Could you provide a more detailed stack trace? The current provided one is really small and not informative at all. Guozhang On Tue, Dec 12, 2017 at 6:42 PM, Ted Yu wrote: > From the

Re: ConcurrentModificationException

>From the stack trace, it seems you hit KAFKA-6349 (where Damian provided a PR). FYI On Mon, Dec 11, 2017 at 11:29 PM, Mr.Wang <1282183...@qq.com> wrote: > Hi~ > We found this error when we read kafka data using storm: > java.util.ConcurrentModificationException at >

ConcurrentModificationException

Hi~ We found this error when we read kafka data using storm: java.util.ConcurrentModificationException at java.util.LinkedHashMap$LinkedHashIterator.nextNode(LinkedHashMap.java:719) at java.util.LinkedHashMap$LinkedKeyIterator.next(LinkedHashMap.java:742) at

Re: Why is compression disabled by default?

Thank you Ismael On Tue, Dec 12, 2017 at 11:49 AM, Ismael Juma wrote: > Yes, the broker will store the batches it receives from the producer. By > default, it won't recompress, but it can be configured to recompress. > Either way, it won't merge multiple batches into a single

Re: Why is compression disabled by default?

Yes, the broker will store the batches it receives from the producer. By default, it won't recompress, but it can be configured to recompress. Either way, it won't merge multiple batches into a single one. Ismael On Tue, Dec 12, 2017 at 6:45 PM, Dmitry Minkovsky wrote: >

Re: Why is compression disabled by default?

I would like to follow up with this more concrete question: For the purpose of achieving decent compression ratios, I am having difficulty finding information on whether the broker can perform additional record batching beyond the batching received from a producer. It seems like in a low-latency

Re: Kafka Monitoring

Hi Irtiza, Unfortunately I don't know what could be the issue in your case - in my case all these metrics simply appear under appropriate keys (e.g. "kafka.controller") in the JSON response of the /list request - the same as the one you're making (I checked it right now to be sure). I also

Re: Strange rebalancing exception in Kafka 1.0.0

HI Ismael, This is what I see in the logs, I tried this twice and got the same exception. This is only reproducible when I have 3 nodes in my cluster even in the start of the app, everything works fine on 2 nodes. [2017-12-12 17:28:36,822] INFO [GroupCoordinator 90]: Preparing to rebalance

Re: Strange rebalancing exception in Kafka 1.0.0

Can you please check the broker logs for errors? Ismael On Tue, Dec 12, 2017 at 12:10 PM, Sameer Kumar wrote: > Hi All, > > Facing an strange exception while running Kafka Streams. I am reading from > a topic of 60 partitions. I am using exactly once in Kafka 1.0.0. > >

Strange rebalancing exception in Kafka 1.0.0

Hi All, Facing an strange exception while running Kafka Streams. I am reading from a topic of 60 partitions. I am using exactly once in Kafka 1.0.0. Now, this error has started appearing recently. The application runs fine on 2 nodes, but as soon as a 3rd node is added, it starts throwing