Visual tool for kafka?

Hi I need a Visual tool for kafka. For example, A Web UI can display the detail of each topics、the offset of each consumer. Has any recommended visual tools? 1095193...@qq.com

offsets.topic.replication.factor vs default.replication.factor

Hi We have a 3 node Kafka Brokers setup. Our current value of default.replication.factor is 2. What should be the recommended value of offsets.topic.replication.factor ? Please advise as we are not completely sure about offsets.topic.replication.factor ? Thanks for your help. R

Re: SIGSEGV fault in Kafka broker

It's probably because you're using Alpine Linux. That's not a supported operating system as we don't test with it. Ismael On Tue, 16 Oct 2018, 11:50 Vishnu Viswanath, wrote: > Hi, > > I am using openjdk-jre 8. > https://pkgs.alpinelinux.org/package/v3.6/community/x86/openjdk8-jre > > I also not

RE: New increased partitions could not be rebalance, until stop all consumers and start them

Hi, I don't think it's a bug. 1. The increasement of the partitions will marked the metadata.updateNeeded=true, however this won't really trigger a update till the next metadata.expire time (the default METADATA_MAX_AGE_CONFIG is 5*60*1000 ms). 2. Before the leader of the group update its metadat

Kafka Streams, when is considered processed?

Hi, I can't find the following in the documentation. In a Kafka Streams application, I wonder for when a message is considered processed. For example for exactly-once configured, we are promised exactly-once processing. But when is it considered processed, directly after consumption? Rega

Re: Strange log delete behavior after segment rollover

Sorry, Please ignore the question of deleting older segments again. Those were for other partitions. The only question is about the delay. Thanks, Vishnu On Thu, Oct 18, 2018 at 1:26 PM Vishnu Viswanath < vishnu.viswanat...@gmail.com> wrote: > Hi All, > > I am seeing some strange behavior on how

Strange log delete behavior after segment rollover

Hi All, I am seeing some strange behavior on how the rolled over segments are deleted. Here is the log for one of the partition. [2018-10-18 07:49:31,557] Rolled new log segment at offset 3600 in 24 ms. (kafka.log.Log) [2018-10-18 07:51:32,443] Deleting segment 0 (kafka.log.Log) ^ Log was rolled

Re: New increased partitions could not be rebalance, until stop all consumers and start them

You can add the config *props.put("metadata.max.age.ms ", 5000);* to your cases, and re-test it. 飞翔的加菲猫 <526564...@qq.com> 于2018年10月18日周四 上午10:47写道： > Sorry for bothering. I don't know whether it is a bug. Maybe something > wrong in my test or there is explanation for