All i want to do is avoid static IP as we have zk cluster in autoscalling
environment and IP is ephemeral there.
On Fri, Jun 7, 2019, 2:38 PM Enrico Olivelli wrote:
> A round robin DNS name should work
>
>
> Enrico
>
> Il ven 7 giu 2019, 22:39 rammohan ganapavarapu
> ha
> scritto:
>
> > Hi,
> >
A round robin DNS name should work
Enrico
Il ven 7 giu 2019, 22:39 rammohan ganapavarapu ha
scritto:
> Hi,
>
> Since with 3.5.5 version clients can watch on zoookeeper/confg znode for
> the active zk servers, do we still need to give all the IPs of zk servers
> to client? or can i give one IP
Hi Ram,
Just one question:
What happens if you only give one server's IP to your client and that one
stops working? The quorum might be still active, only that one server is
inactive.
You try to connect to that server to get the server list, but cannot
connect.
If you have more than one IP given
Hi,
Since with 3.5.5 version clients can watch on zoookeeper/confg znode for
the active zk servers, do we still need to give all the IPs of zk servers
to client? or can i give one IP or rr dns name to a client and client can
get server's list from the config znode to balance the connections?
Tha
Enrico,
Thank you.
Ram
On Fri, Jun 7, 2019 at 5:30 AM Enrico Olivelli wrote:
> Ram
> Can you describe better your problem ?
> Usually you are activating auth on clients and then you apply the ACLs this
> way all clients will be able to access data.
>
> Try our procedure in a staging environmen
Ram
Can you describe better your problem ?
Usually you are activating auth on clients and then you apply the ACLs this
way all clients will be able to access data.
Try our procedure in a staging environment before doing in in production
Enrico
Il gio 6 giu 2019, 23:56 rammohan ganapavarapu ha
s