Kafka does not check the expiry of SSL certificates if host.cer is included in truststore ?

[Deepak Jain]

Hello fellow Kafka users,

I have came across this behaviour of kafka while using it in SASL_SSL mode. My 
observations are:

When we exclude the host.cer => Expiry date of certificate[1] in certificate 
chain of Keystore is consider.
When we include the host.cer => No expiry is check even for all 3 certificate 
in the chain.

Can anyone help me understands whether it's a known behaviour in kafka or an 
issue?


Any help would be appreciated.



Thanks,
Deepak

N partitions have leader brokers without a matching listener

[lk_hadoop]

hi,all : 
   I using hdp3.1.4 with kafka version is :2.0.0
   when I try to write to or read from a topic I will get : "N partitions have 
leader brokers without a matching listener" error
   And I describe the topic, it shows partion's learder and Replicas's broker 
id: 
but when I go to zookeeper to see /brokers/ids , I find that the broker ids is 
not same with topic partion's leader or replicas's broker id 


I don't know why the brokers id changed in zookeeper, but now how can I fix 
this issue, thanks.

Re:N partitions have leader brokers without a matching listener

[lk_hadoop]

I've resolved by reference this post : 
https://community.cloudera.com/t5/Community-Articles/Troubleshooting-Kafka-Upgrade/ta-p/245991
















At 2021-08-26 10:46:32, "lk_hadoop"  wrote:

hi,all : 
   I using hdp3.1.4 with kafka version is :2.0.0
   when I try to write to or read from a topic I will get : "N partitions have 
leader brokers without a matching listener" error
   And I describe the topic, it shows partion's learder and Replicas's broker 
id: 
but when I go to zookeeper to see /brokers/ids , I find that the broker ids is 
not same with topic partion's leader or replicas's broker id 


I don't know why the brokers id changed in zookeeper, but now how can I fix 
this issue, thanks.