problem.
>>>>>
>>>>> The fact that it can persist after a restart is what really sticks out to
>>>>> me. Is there any state stored outside of Kafka that could be getting in
>>>>> the
>>>>> way? Does Zookeeper store anything o
>>
> >>>> On 1 Aug 2019, at 7:10 pm, Rajini Sivaram
> >>> wrote:
> >>>>
> >>>> Hi Michael,
> >>>>
> >>>> Thank you for reporting this. It is possible that we missed out some
> >>>> client-side updat
le for you to provide
>>>> logs from multiple brokers around the time of a broker restart when
>>>> handshake failures started occurring so that we can try to work out which
>>>> client connection is failing? Corresponding to the handshake failure
>>> entry
>
rver in the restarted broker, there should a failed client
>>> connection on another broker. If that has a stack trace, it would be
>> useful.
>>>
>>> Also just to confirm, are these correct:
>>>
>>> 1) All brokers are dynamically updated with ne
broker is restarted, handshakes failures appear in the logs and
> > these are logged from SocketServer in the restarted broker. (this could
> > indicate that some client-side cert was not updated dynamically)
> > 3) Once all brokers are restarted, there are no more handshake failures
having an issue with dynamic configuration of interbroker SSL
> certificates (in Kafka 2.3.0) that I'm hoping someone can give me insight
> on. I've previously posted something similar on the Users email list, but I
> think it will need some help from developers experienced with h
Hi all,
I'm having an issue with dynamic configuration of interbroker SSL certificates
(in Kafka 2.3.0) that I'm hoping someone can give me insight on. I've
previously posted something similar on the Users email list, but I think it
will need some help from developers experienc
