Granting permission for jira

Please grant permission for jira to luoen

Re: kafka command is not working

In bootstrap server put at least two brokers nodes of the cluster to get the metadata of the initial connection בתאריך יום ב׳, 17 במאי 2021, 18:07, מאת Aniket Pant ‏: > Hi team, > my question is , i have 3 nodes of kafka cluster and when i stop one broker > i cannot lag messages it show me error

Upgrading Apache Kafka 2.7 to Java 11 Changes authenticationID sent to ZooKeeper Enabling Only 1 Kafka Broker to r/w znodes

I am having some trouble upgrading a kerberized Kafka 2.7 cluster to Java 11. Once upgraded, Kafka no longer sends the expected authenticationID to ZooKeeper and the ACLs on the znodes now only allow access to the Kafka host that first created them. Complete details of this problem can be found

Re: Application state persistence in Kafka

Urko, You can enable changelog topics for your state store. This will enable the application to persist the data to a Kafka topic. Next time when application start, it will first build it's state by using this topic. Are you using Kstreams or the low-level processor API? Regards, Mangat On Mon,

Application state persistence in Kafka

Hello, I have a question regarding the use of Kafka/Kafka Streams to store the state of a stateful application. My application is filtering on a stream based on a value from the previous event of the stream. For example, if the previous car with the same model was red, this car cannot be red.

kafka command is not working

Hi team, my question is , i have 3 nodes of kafka cluster and when i stop one broker i cannot lag messages it show me error like ``` [2021-05-17 19:20:22,583] WARN [AdminClient clientId=adminclient-1] Connection to node -1 (localhost/xx.xx.xx.xx:9092) could not be established. Broker may not be

Re: Is bootstrap.servers resolved only once?

Yes. On initial bootstrapping dns resolves all ip as of 2.10, if you specified client.dns.lookup to use all addresses. But the dns is evaluated only once in the producer initialisation (constructor) so it will fail if all broker ip changed at once. On Mon, 17 May 2021 at 9:42 PM, Michał

Re: Is bootstrap.servers resolved only once?

On Mon, May 17, 2021 at 2:25 PM Shilin Wu wrote: > Bootstrap servers are just used for initial connection, clients will get > all server metadata from one of the bootstrap servers to discover the full > cluster membership (which may change dynamically), this list does not have > to contain the

Re: Is bootstrap.servers resolved only once?

Bootstrap servers are just used for initial connection, clients will get all server metadata from one of the bootstrap servers to discover the full cluster membership (which may change dynamically), this list does not have to contain the full set of servers (you may want more than one, though, in

Is bootstrap.servers resolved only once?

Hey, Trying to understand how *bootstrap.servers* is handled for KafkaProducer. I see that it's processed during creating of producer (here ) and later if client DNS lookup

a zk-session-expiry issue

Hi， When we use Kafka, we find a strange issue: Once Kafka has a zk-session-expiry exception , a large number of isr shrink, and zk request’s latency is high. Metrics from jmx: [cid:D3CD0A0D-58EA-4328-ADB3-F68F7ECEE962] [cid:E68F4EA5-44F9-46EA-9F67-378FEDB7AAD1] When we get broker’s jstack,we