Thanks Ryanne
Sent from Yahoo Mail for iPhone
On Thursday, September 15, 2022, 12:00 AM, Ryanne Dolan
wrote:
The link is correct. Connect and mm2 create those internal topics at
startup, whether or not auto topic creation is enabled.
On Wed, Sep 14, 2022, 11:15 PM Mcs Vemuri
wrote:
>
You're very welcome, and good luck with your installation.
Kind regards,
Richard Bosch
On Fri, 16 Sep 2022, 17:56 James Ziesig,
wrote:
> Hi Richard,
>
> Thank you for the response. That does clear things up for me. I thought
> it would be good to avoid MITM attacks by validating SAN, if CN
Hi Richard,
Thank you for the response. That does clear things up for me. I thought
it would be good to avoid MITM attacks by validating SAN, if CN is a
service identifier, without the need for ACLs. However, I do appreciate
the added flexibility provided by the ACLs, and the lack of client
Hi Jim,
The broker setting for endpoint identification is used when a broker
connects to another broker.
For client connection the handshake is performed by verifying that the
certificate presented by the client is signed by a CA that's in the
truststore, and that it hasn't expired yet.
If you
Thanks Peter,
I’ll check the logs next week and let you know my findings.
Many Thanks
Chris
> On 16 Sep 2022, at 7:45 am, Peter Bukowinski wrote:
>
> The next thing I’d check is the broker logs. The parameters read from the
> config should appear in the logs when kafka starts up. Search
The next thing I’d check is the broker logs. The parameters read from the
config should appear in the logs when kafka starts up. Search the logs for
‘log.dirs’ and ensure the correct configs are loaded.
--
Peter
> On Sep 15, 2022, at 11:10 PM, Chris Peart wrote:
>
> Hi Peter,
>
> Thanks
Hi Peter,
Thanks for your response, we have the following configuration:
Partition count=4
Replication factor=3
All four brokers have topics-partitions in /data/1/kafka/data and are receiving
data.
Each server has 6 x 2TB disks for kaka data.
Many Thanks,
Chris
> On 16 Sep 2022, at 1:56
