be stuck in an uneven state, then that can
either be because (a) there's a bug in the assignor, or more likely (b) the
group itself is unstable and the assignment can't converge.
Given this issue is accompanied by the "hostname unavailable", it sounds
like the group is stuck re
ws and session windows. To
> retrieve
> > windows efficiently, I've established a remote query mechanism between
> > Kafka Streams instances. By leveraging the queryMetadataForKey method on
> > streams, I can retrieve the hostname where a specific key
veraging the queryMetadataForKey method on
> streams, I can retrieve the hostname where a specific key was processed and
> where the corresponding window data resides in the state store.
> *streams.queryMetadataForKey(storeName, recordKey, new
> DataKeySerilizer()).activeHost(
o retrieve
windows efficiently, I've established a remote query mechanism between
Kafka Streams instances. By leveraging the queryMetadataForKey method on
streams, I can retrieve the hostname where a specific key was processed and
where the corresponding window data resides in
dating 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 hostname
> validation on handshake simplifies the client cert deployment.
>
> Thanks again, and have a nice weekend.
&
hostname
validation on handshake simplifies the client cert deployment.
Thanks again, and have a nice weekend.
Jim Ziesig
On Fri, Sep 16, 2022 at 4:31 AM Richard Bosch
wrote:
> Hi Jim,
>
> The broker setting for endpoint identification is used when a broker
> connects to another b
t.
If you want to limit access to resources on the location, you can set up
ACLs to match on the reported hostname of the client as well.
This allows you to define an ACL with a meaning like this: Principal
CN=MyClientCert has Consume access for Topic Y if it connects from Host
10.1.2.100
I hope
Hi,
I have configured mTLS on a three server Kafka cluster. The servers and
clients are all communicating properly, except I am having trouble with
client hostname validation when the client is using a cert from a different
host. I would expect this to fail on handshake like it does when the
Hi,
I have enabled SSL certificate betwen my Kafka server and client
communicaiton with correct host name in CSR of certificates.
I've multiple hosts (100-200) that can produce the messages on the broker
and would liek to share the same certificates for each of the hosts.
For this, I want to kn
d I be able to use the same
certificates for my brokers in test environment where they have FQDN as:
host1.testsystem.net
host2.testsystem.net
In other words, if the clients do full hostname verification will this be
accepted? I haven't managed to check the source file yet.
I hope I have set it up
Hello,
Previously, we were using Kafka version 0.10.0.0 and Kafka Connect
0.10.0.0. Everything was working fine, but we would like to upgrade Connect
to the latest version 0.10.1.1 to make use of some new features. We do not
want to upgrade Kafka if we don't have to. However, it seems that the new
Hello,
Previously, we were using Kafka version 0.10.0.0 and Kafka Connect
0.10.0.0. Everything was working fine, but we would like to upgrade Connect
to the latest version 0.10.1.1 to make use of some new features. We do not
want to upgrade Kafka if we don't have to. However, it seems that the new
You'll need to do a rolling restart of your kafka nodes after changing the
zookeeper ensemble. There's no real way around that right now.
On Sun, Sep 25, 2016 at 6:41 PM, Ali Akhtar wrote:
> Perhaps if you add 1 node, take down existing node, etc?
>
> On Sun, Sep 25, 2016 at 10:37 PM, brenfield1
Perhaps if you add 1 node, take down existing node, etc?
On Sun, Sep 25, 2016 at 10:37 PM, brenfield111
wrote:
> I need to change the hostnames and ips for the Zookeeper ensemble
> serving my Kafka cluster.
>
> Will Kafka carry on as usual, along with it's existing ZK nodes, after
> making the c
I need to change the hostnames and ips for the Zookeeper ensemble
serving my Kafka cluster.
Will Kafka carry on as usual, along with it's existing ZK nodes, after
making the config changes?
Thanks
host
and port of a ZooKeeper server rather than the host and port info of the
broker that gets published to ZK.
# Hostname the broker will advertise to producers and consumers. If not
set, it uses the
# value for "host.name" if configured. Otherwise, it will use the valu
ts
> > > > > used for two purposes: 1) to bind the socket 2) to publish the
> broker
> > > > > details to ZK for clients to use.
> > > > >
> > > > > There are times when these two settings need to be different.
> Here'
s to ZK for clients to use.
> > > >
> > > > There are times when these two settings need to be different. Here's
> an
> > > > example. I want to setup Kafka brokers on OpenStack virtual machines
> > in a
> > > > private cloud but I need producers to c
enStack virtual machines
> in a
> > > private cloud but I need producers to connect from elsewhere on the
> > > internal corporate network. With OpenStack, the virtual machines are
> only
> > > exposed to DHCP addresses (typically RFC 1918 private addresses). Yo
ducers to connect from elsewhere on the
> > internal corporate network. With OpenStack, the virtual machines are only
> > exposed to DHCP addresses (typically RFC 1918 private addresses). You can
> > assign "floating ips" to a virtual machine but it's
Translation and not exposed directly to the VM. Also, there's
> typically no DNS to provide hostname lookup. Hosts have names like
> "fubar.novalocal" that are not externally routable.
>
> Here's what I want. I want the broker to bind to the VM's private networ
ically RFC 1918 private addresses). You can
assign "floating ips" to a virtual machine but it's forwarded using Network
Address Translation and not exposed directly to the VM. Also, there's
typically no DNS to provide hostname lookup. Hosts have names like
"fubar.novaloca
; You can mitigate this issue by using controlled shutdown to stop a
> broker.
> >
> > Thanks,
> > Neha
> > On Oct 4, 2013 2:45 AM, "Aniket Bhatnagar"
> > wrote:
> >
> > > Because Kafka was detecting localhost.domain as hostname, I comme
ssue by using controlled shutdown to stop a broker.
>
> Thanks,
> Neha
> On Oct 4, 2013 2:45 AM, "Aniket Bhatnagar"
> wrote:
>
> > Because Kafka was detecting localhost.domain as hostname, I commented out
> > the line "127.0.0.1 localhost.l
restart the broker very quickly?
You can mitigate this issue by using controlled shutdown to stop a broker.
Thanks,
Neha
On Oct 4, 2013 2:45 AM, "Aniket Bhatnagar"
wrote:
> Because Kafka was detecting localhost.domain as hostname, I commented out
> the
Because Kafka was detecting localhost.domain as hostname, I commented out
the line "127.0.0.1 localhost.localdomain localhost" and added
"127.0.0.1 ip-10-0-1-20.localdomain" in etc/hosts. When I restart Kafka
(issues kill -15 pid), writes to existing topics a
I think, if kafka can not identify hostname by its own, try to set the hostname
in the server.properties.
Would this work for you?
--
Markus Roder
Am 20.06.2013 um 17:56 schrieb "Yu, Libo " :
> Hi,
>
> I set up kafka on a linux vm player. There is no hostname with it.
&g
Hi,
I set up kafka on a linux vm player. There is no hostname with it.
So I used IP in all configuration files. I assume that should work.
But I got an exception and kafka asked for hostname. That seems
to be a bug.
Regards,
Libo
28 matches
Mail list logo
