Hi,
You can, but behaviour depends on the authorizer plugin, I think the one
that comes with Kafka, treats non-authorized users as an ANONYMOUS user, so
if you have no ACL defined for it, they get denied.
Good luck,
OSB
On Mon, Nov 4, 2024, 14:00 Sameer Modak wrote:
> Hello Team,
>
> I tried a
Hi,
The log shown on the blog post was for the console consumer tool. These
log messages emitted for the consumer process so you need to configure
log4j configuration for the kafka tools if you want to achieve the same
thing.
The functionality provided by the KIP-392 is only realized only if cli
Hi,
Could not able to find correlationID response for the Apiversions API, did
you mean Produce API?
Maybe it is throttleTimeSize ?
https://github.com/a0x8o/kafka/blob/54eff6af115ee647f60129f2ce6a044cb17215d0/core/src/main/scala/kafka/api/ProducerResponse.scala#L68
On Sun, Oct 27, 2024, 17:42 C
Hi Erik,
What do you mean by "this must be done external to " ?
If the cluster still uses ZK for metadata, you can construct a read-only
Zookeeper client to get zNode creation timestamp for the topic from ZK
node, which reflects the creation time.
Also determining unused topics can be tricky if
Hi,
Why do you even bother catching the exception if you could change the
connection details for the clients?
You would need to create a new listener, each client then required to be
reconfigured to connect that, introducing a code/configuration change
anyways.
Good luck,
Ömer Şiar Baysal
On
Hi Austin,
I think it is worth to mention also the network bandwidth without even
Kafka involved. You can create a test bench with basic Linux toolkit like
ncat. Tuning socket buffers hardly make sense if the bandwidth is already
low between the producer and remote site.
When OS is configured t
Hi,
I have never seen PolicyViolationException before with vanilla Kafka. What
is the flavor?
This may caused by the controller mutation rate checks introduced by
KIP-599, it may be triggered for non-existing topics but not for the
existing resources.
Hope this help you track it down.
OSB
On
Hi David,
Thank you for your response and your interest in this one. I also
agree with the main counter-argument, having a single control-plane
for all tenants would have a greater blast radius, I still think it
would also be more cost effective. The idea is having a multi-region
(3 AZ) controller
Hi,
ZK chroot allows the Zookeeper ensemble to be shared with other
applications, including other Kafka clusters, without a conflict.
Kafka brokers from different clusters can connect to a single ZK
ensemble consists from 5 nodes (metadata), I will explain below why I
have chosen 5 nodes.
One can