KIP-226 - Dynamic Broker Configuration

2018-04-18 Thread Darshan
Hi KIP-226 is released in 1.1. I had a questions about it. If we add a new certificate (programmatically) in the truststore that Kafka Broker is using it, do we need to issue any CLI or other command for Kafka broker to read the new certificate or with KIP-226 everything happens automatically ?

Kafka stream error about message format

2018-04-18 Thread sy.pan
Hi, All: I have upgraded my Kafka cluster from 0.10.2 to 1.1 recently. After rolling upgrade, the broker version related configuration is : inter.broker.protocol.version = 1.1 log.message.format.version = 0.10.2 I keep the log message format as low version because not all clients could

Apache Kafka topic security for PLAINTEXT port reg.

2018-04-18 Thread Vinay Danda
Hi, I have listeners configured with 2 ports as below: (9092 -> Plaintext, 9092 -> SASL_PLAIN) listeners=PLAINTEXT://:9092, SASL_PLAIN://:9093 For a topic, I want restrict Consumers to consume data from 9093 port only, and consuming data from 9092 port should be denied. I've gone through ACL

org.apache.kafka.common.errors.UnsupportedVersionException in Java

2018-04-18 Thread James Yu
Hi, I can use "kafka-console-consumer.sh" to subscribe a topic on my kafka broker, the consumer receives messages from kafka broker just fine. However, when I try to subscribe the same topic in Java code with spring-kafka, I get the UnsupportedVersionException error: 2018-04-19 06:42:30.124

Re: Default kafka log.dir /tmp | tmp-file-cleaner process

2018-04-18 Thread Marc
Hey guys, thanks for the answers so far. I got your points. I would recommend to add a hint like „Don’t use /tmp as default in production. Please change this parameter in a production environment“. They are doing this with other parameters like the replication factor in the documenation, too.

Re: Default kafka log.dir /tmp | tmp-file-cleaner process

2018-04-18 Thread Peter Bukowinski
I believe that default parameters should help people new to a product get a test instance running relatively easily. Setting the log.dir to temp aligns with this philosophy. Once you’re out of a testing phase, you’ll hopefully be familiar enough with the product to set appropriate values for

RE: Default kafka log.dir /tmp | tmp-file-cleaner process

2018-04-18 Thread adrien ruffie
Hi Marc, I think it's depends rather on "log.dirs" parameter. Because this parameter would prefer to use in more convenient case, "log.dir" parameter is secondary. logs.dirs: The directories in which the log data is kept. If not set, the value in log.dir is used log.dir: The directory in

Re: Commit in Kafka streams reduces throughput

2018-04-18 Thread Guozhang Wang
Hello Shivam, I think your two questions can be answer as one :) Have just created this FAQ entry for you: https://cwiki.apache.org/confluence/display/KAFKA/FAQ#FAQ-WhenIcommitmyprocessstate,whatdoestheStreamslibrarydoandhowitaffectsmyapplication'sperformance ? Guozhang On Tue, Apr 17, 2018

Re: Bug report: Topologies affecting each other through store: Partition XXX is not assigned to any tasks: {}

2018-04-18 Thread Guozhang Wang
Hello Erwin, Thanks for reporting this issue. I'd agree with you that root cause is not very clearly explained in the WARN log entries, which makes users very confused when debugging such scenarios. More specifically: When you are letting two sub-topologies to access the same store, Streams will

Default kafka log.dir /tmp | tmp-file-cleaner process

2018-04-18 Thread Marc van den Bogaard
Hey guys, when I look in the kafka documentation (https://kafka.apache.org/documentation/ ) the default log.dir for the kafka logs is /tmp. Could someone please tell me why? Because if you don’t change this you probably get some issues regarding the

Restrict kafka consumers from PLAINTEXT port.

2018-04-18 Thread Vinay Kumar
Hi, I have listeners configured with 2 ports as below: (9092 -> Plaintext, 9092 -> SASL_PLAIN) listeners=PLAINTEXT://:9092, SASL_PLAIN://:9093 For a topic, I want restrict Consumers to consume data from 9093 port only, and consuming data from 9092 port should be denied. I've gone through ACL

Re: Possible to Disable Offset Checkpointing for an In-Memory Global Store?

2018-04-18 Thread Matthias J. Sax
Make totally sense and is a known issue: https://issues.apache.org/jira/browse/KAFKA-6711 Please follow up the ticket and/or PR -- not sure what the current status is. -Matthias On 4/17/18 11:16 PM, David Chu wrote: > I have a custom in-memory state store which I’d like to configure as a