You need to pass "security.protocol" config using producer.config or
--consumer.config command-line options.
Only java clients supports security. You need use "--new-consumer" option
for kafka-console-consumer.sh
also need to setup producer/consumer scripts to use jaas conf using
Bump, still haven't seen anything here. Betting this problem isn't unique
to us. Would love to hear how other folks are managing controlled restarts
of their clusters. =)
On Tue, Nov 28, 2017 at 4:40 PM Matt Farmer wrote:
> Hey all,
>
> So, I'm curious to hear how others have
@Girish, wow, that could be a nice issue to debug. I was thinking about
exactly these kind of issues with virtualized environments.
@Wim, how did you overcome the problem?
Thinking about such issues my first thoughts are increasing the VM's memory
that can be utilized to read/write caching by the
Thanks for reporting back, Sameer!
On Fri, Dec 1, 2017 at 2:46 AM, Guozhang Wang wrote:
> Thanks for confirming Sameer.
>
>
> Guozhang
>
> On Thu, Nov 30, 2017 at 3:52 AM, Sameer Kumar
> wrote:
>
> > Just wanted to let everyone know that this issue
If you set these configs at broker start they will automatically replicate
newly created topics:
default.replication.factor
num.partitions=3
Ben
On Fri, Dec 1, 2017 at 1:41 PM Skip Montanaro
wrote:
> Are dynamically created topics thus never replicated?
>
> On Nov
Are dynamically created topics thus never replicated?
On Nov 30, 2017 6:52 PM, "Tauzell, Dave"
wrote:
> You then also need to set this up for each topic you create:
>
> > bin/kafka-topics.sh --create --zookeeper localhost:2181
> --replication-factor 3 --partitions
1.Version
Kafka version: 0.10.0.0
2.Config
#config/server.properties
advertised.listeners=SASL_PLAINTEXT://hzadg-mammut-platform2.server.163.org:6667
listeners=SASL_PLAINTEXT://hzadg-mammut-platform2.server.163.org:6667
authorizer.class.name=kafka.security.auth.SimpleAclAuthorizer
Hello,
We have the following code to send avro message to a topic (Please find the
code snippet below). Although the ProducerResord received a complete
acknowledgement withiot exception, the message is never stored in this
topic.
In the log we can see the following message is logged:
Hi XinYi,
All consumer instances using the same group.id will share the data
(partitions) of a certain topic. The consumer group.id is not bound to a
topic.
If you want to share data on 1 topic, and parallel process data on another,
you have to change the group.id.
best regards,
Joris
On