Hi,

There is no specific doc. "--command-config" option takes admin client
configs (.
AdminClient configs are listed here:
http://kafka.apache.org/documentation/#adminclientconfigs


On Tue, Aug 14, 2018 at 10:35 PM John Calcote <john.calc...@gmail.com>
wrote:

> Manikumar,
>
> Thank you. You are right - the security.protocol is NOT being passed to
> adminclient.properties file. Where exactly is the doc for that file? I
> searched for hours and finally had to guess at which options should be in
> there.
>
> J
>
> On Tue, Aug 14, 2018, 8:54 AM Manikumar <manikumar.re...@gmail.com> wrote:
>
> > looks like port is wrong or security.protocol config is not passed to
> > adminclient.properties file
> >
> > On Tue, Aug 14, 2018 at 7:23 PM John Calcote <john.calc...@gmail.com>
> > wrote:
> >
> > > Hi,
> > >
> > > I'm using the latest kafka broker - 2.0.0 with scala 2.12. I have a
> > > complete SSL configuration working, but I add clients occasionally and
> > want
> > > to be able to tell the broker to reload it's ssl truststore (as new
> certs
> > > have been added to it).
> > >
> > > I've followed the doc here:
> > >
> > >
> >
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-226+-+Dynamic+Broker+Configuration
> > >
> > > and this is what I get:
> > >
> > > $ kafka_2.12-2.0.0/bin/kafka-configs.sh --bootstrap-server
> > > data-cluster:9092 --command-config
> > > ./kafka_2.12-2.0.0/adminclient.properties --alter --add-config
> > > ssl.truststore.password=password --entity-name 0 --entity-type brokers
> > > [2018-08-14 07:48:57,223] ERROR Uncaught exception in thread
> > > 'kafka-admin-client-thread | adminclient-1':
> > > (org.apache.kafka.common.utils.KafkaThread)
> > > java.lang.OutOfMemoryError: Java heap space
> > >         at java.nio.HeapByteBuffer.<init>(HeapByteBuffer.java:57)
> > >         at java.nio.ByteBuffer.allocate(ByteBuffer.java:335)
> > >         at
> > >
> >
> org.apache.kafka.common.memory.MemoryPool$1.tryAllocate(MemoryPool.java:30)
> > >         at
> > >
> > >
> >
> org.apache.kafka.common.network.NetworkReceive.readFrom(NetworkReceive.java:112)
> > >         at
> > >
> >
> org.apache.kafka.common.network.KafkaChannel.receive(KafkaChannel.java:335)
> > >         at
> > >
> org.apache.kafka.common.network.KafkaChannel.read(KafkaChannel.java:296)
> > >         at
> > > org.apache.kafka.common.network.Selector.attemptRead(Selector.java:560)
> > >         at
> > >
> > >
> >
> org.apache.kafka.common.network.Selector.pollSelectionKeys(Selector.java:496)
> > >         at
> > org.apache.kafka.common.network.Selector.poll(Selector.java:425)
> > >         at
> > > org.apache.kafka.clients.NetworkClient.poll(NetworkClient.java:510)
> > >         at
> > >
> > >
> >
> org.apache.kafka.clients.admin.KafkaAdminClient$AdminClientRunnable.run(KafkaAdminClient.java:1116)
> > >         at java.lang.Thread.run(Thread.java:748)
> > > Error while executing config command with args '--bootstrap-server
> > > data-cluster:9092 --command-config
> > > ./kafka_2.12-2.0.0/adminclient.properties --alter --add-config
> > > ssl.truststore.password=password --entity-name 0 --entity-type brokers'
> > > java.util.concurrent.TimeoutException
> > >         at
> > >
> > >
> >
> org.apache.kafka.common.internals.KafkaFutureImpl$SingleWaiter.await(KafkaFutureImpl.java:108)
> > >         at
> > >
> > >
> >
> org.apache.kafka.common.internals.KafkaFutureImpl.get(KafkaFutureImpl.java:274)
> > >         at
> > kafka.admin.ConfigCommand$.brokerConfig(ConfigCommand.scala:346)
> > >         at
> > > kafka.admin.ConfigCommand$.alterBrokerConfig(ConfigCommand.scala:304)
> > >         at
> > > kafka.admin.ConfigCommand$.processBrokerConfig(ConfigCommand.scala:290)
> > >         at kafka.admin.ConfigCommand$.main(ConfigCommand.scala:83)
> > >         at kafka.admin.ConfigCommand.main(ConfigCommand.scala)
> > > $
> > >
> > > There's nothing on the net about this, so I can only assume the issue
> is
> > > either too new, or I'm just doing something obvious (to someone else)
> the
> > > wrong way. :)
> > >
> > > Thanks in advance,
> > > John
> > >
> >
>

Reply via email to