Thanks Eric,

The situation is like this - we have only a single broker and it has to
make a clean break from PLAINTEXT, but our clients are all either old or
new (upgraded to SSL). The old ones will obviously not be able to work
against the upgraded broker. The problem is I have 18 (only a slight
exaggeration) different clients in C/C++, Python and Java. I wanted to
upgrade the client code one git commit at a time, without breaking the
system before we switch the broker over to SSL. So I was hoping I'd find a
way to determine if the broker was talking SSL yet, and start up the
clients in either PLAINTEXT or SSL based on my query.

Sorry for not being this clear up front.

John

On Wed, Aug 15, 2018 at 12:33 PM Eric Azama <[email protected]> wrote:

> Zookeeper definitely has the information about endpoints and protocol.
> The /brokers/ids/<broker_id> paths in zookeeper contains the endpoints that
> are open on the broker.
>
> I have doubts that you'll be able to make this change without any downtime
> though. To my knowledge, clients are only capable of using one security
> protocol at a time. If half your brokers are only using plaintext and the
> other half are only using ssl, the clients will be unable to talk to half
> of your brokers. Any partitions whose leader is on one of the brokers with
> the wrong protocol will be offline as far as the client is concerned.
>
> The same would apply to the replication protocol. Any followers that aren't
> using the same protocol as the leader will be unable to retrieve data from
> the leader and will eventually drop from the ISR.
>
> On Wed, Aug 15, 2018 at 10:18 AM John Calcote <[email protected]>
> wrote:
>
> > I have a situation where I have to upgrade a distributed system in a
> > piecemeal from plaintext to ssl between kafka clients and broker.
> >
> > Is there a simple way to detect from the client if it should be trying to
> > use plaintext or ssl - from a kafka API perspective? I can do a low-level
> > trick like open a socket and send an ssl client-hello message, but I was
> > hoping I could read some zookeeper data to determine if the broker is
> using
> > ssl or plaintext. Also, (for internal political reasons) I can't open
> both
> > ssl and plaintext channels - once the broker changes over, it has to be
> all
> > or nothing.
> >
> > Thanks in advance,
> > John
> >
>

Reply via email to