Re: reg Kafka Node num

Kafka logs traffic to the Controller node separately from the normal traffic to the node. In order to differentiate it subtracts the broker id from 2147483647 (max int) and uses the result as the "node id" for the controller. On a related note, logs and metrics related to the bootstrap process see

Re: kafka broker loosing offsets?

Hey guys, just want to post that upgrade to 0.11.0.1 solved the issue. After excessive disaster testing no re-consumption of old offsets were experienced. On Thu, Oct 12, 2017 at 1:35 AM, Vincent Dautremont < vincent.dautrem...@olamobile.com.invalid> wrote: > Hi, > We have 4 differents Kafka c

Re: Micro-batching in Kafka streams - redux

Hi, as Kafka Streams focuses on stream processing, micro-batching is something we don't consider. Thus, nothing has changed/improved. About the store question: If you buffer up your writes in a store, you need to delete those value from the store later on to avoid that the store grown unbounded.

Micro-batching in Kafka streams - redux

Kafka version: 0.10.2.1 (can upgrade if needed) I wish to revive the discussion around micro batching in Kafka streams. Some past discussions are here & here . I am exploring ways to do at-least-once proces

Re: Kafka Streams 0.11.0.1 Rebalancing Delay

Thanks. I've changed the config settings and gotten a little better results, but the issue still remains, and doesn't seem only related to this. There seems to be an excessive use of bandwidth when initializing state stores in 0.11.0.1 compared to previous version. I realized that at least one of

Kafka inter broker protocol version

Hello, we'd like to ask you for clarification of our question. We have Apache Kafka deployed in the three-nodes Azure cluster. There are three Kafka brokers, three ZooKeeper nodes and three back-end services of our app. The app uses Apache Kafka as an event store. But for some reasons we couldn

Re: reg kafka API versions

See code in NetworkClient : int latestClientVersion = clientRequest .apiKey().latestVersion(); if (header.apiVersion() == latestClientVersion) { ... } else { log.debug("Using older server API v{} to send {} {} with correlation id {} to node {

Re: reg Kafka Node num

Here is related code: log.debug("Using older server API v{} to send {} {} with correlation id {} to node {}", header.apiVersion(), clientRequest.apiKey(), request, clientRequest.correlationId(), nodeId); 2147483647 is the node Id. On Fri, Oct 20, 2017 at 2:

Re: Kafka Streams : Problem with Global State Restoration

Hi Damian, Thanks a lot for the response. Just saw your reply when I visited the mailer-list archive . Unfortunately I haven't received the same on my inbox and I didn't even see the update in the archive when I checked earl

reg Kafka Node num

I have run a Multiple Partition and Multiple Consumer application.Then i have altered the no of Partitions, in log im getting Using older server API v0 to send HEARTBEAT {group_id= altermultipartitionmulticonsumer2,group_generation_id=6, member_id=C2-b7b4f485-d0c3-466b-b0e7-b3de834832e9} to node

reg kafka API versions

I have run a Multiple Partition and Multiple Consumer application.Then i have altered the no of Partitions, in log im getting Using older server API v0 to send HEARTBEAT {group_id= altermultipartitionmulticonsumer2,group_generation_id=6, member_id=C2-b7b4f485-d0c3-466b-b0e7-b3de834832e9} to node