Connection string on Kubernetes

[Tim Ward <ti...@featurespace.co.uk>]

What should the Curator connection string be when Zookeeper is running on Kubernetes?

Must it be a list of all the individual ZK nodes, or will just giving the service address work? By "work", I might mean something like "if a ZK node goes down, Curator will re-query DNS as necessary to pick up a different node, rather than keep retrying the failed one". (Or that might not be what I mean - I don't know, that's the issue.)


Tim Ward


Principal engineer


—


t: +44 (0) 1223 345 940




Broers Building, Hauser Forum
21 JJ Thomson Avenue, Cambridge
CB3 0FA United Kingdom


featurespace.com<https://www.featurespace.com/> | Twitter<https://twitter.com/FeaturespaceLtd> | LinkedIn<https://www.linkedin.com/company/featurespace>

[cid:image001.png@01D5FD43.4F719E60]


[A screenshot of a cell phone  Description automatically generated]


This message, and any files/attachments transmitted together with it, is intended for the use only of the person (or persons) to whom it is addressed. It may contain information which is confidential and/or protected by legal privilege. Accordingly, any dissemination, distribution, copying or use of this message, or any part of it or anything sent together with it, other than by intended recipients, may constitute a breach of civil or criminal law and is hereby prohibited. Unless otherwise stated, any views expressed in this message are those of the person sending it and not the sender's employer. No responsibility, legal or otherwise, of whatever nature, is accepted as to the accuracy of the contents of this message or for the completeness of the message as received. Anyone who is not the intended recipient of this message is advised to make no use of it and is requested to contact Featurespace Limited as soon as possible. Any recipient of this message who has knowledge or suspects that it may have been the subject of unauthorised interception or alteration is also requested to contact Featurespace Limited.

Re: Connection string on Kubernetes

[Jordan Zimmerman <jo...@jordanzimmerman.com>]

> What should the Curator connection string be when Zookeeper is running on Kubernetes?

The connection string is passed through to the managed ZooKeeper class. So, I'd refer you to the ZooKeeper docs: http://zookeeper.apache.org/doc/r3.5.7/zookeeperProgrammers.html 

> Must it be a list of all the individual ZK nodes, or will just giving the service address work? By "work", I might mean something like "if a ZK node goes down, Curator will re-query DNS as necessary to pick up a different node, rather than keep retrying the failed one". (Or that might not be what I mean - I don't know, that's the issue.)

Just as with the ZooKeeper class itself, you can put whatever server instances in the connection string that you want. Ideally, you'd put all server instances in the string. To be clear - Curator wraps the existing ZooKeeper library - it doesn't implement its own version of the protocol.

-Jordan

> On Mar 18, 2020, at 11:36 AM, Tim Ward <ti...@featurespace.co.uk> wrote:
> 
> What should the Curator connection string be when Zookeeper is running on Kubernetes?
>  
> Must it be a list of all the individual ZK nodes, or will just giving the service address work? By "work", I might mean something like "if a ZK node goes down, Curator will re-query DNS as necessary to pick up a different node, rather than keep retrying the failed one". (Or that might not be what I mean - I don't know, that's the issue.)
>  
>  
> Tim Ward 
>  
>  
> Principal engineer 
>  
>  
> — 
>  
>  
> t: +44 (0) 1223 345 940 
>  
>  
>  
>  
> Broers Building, Hauser Forum 
> 21 JJ Thomson Avenue, Cambridge 
> CB3 0FA United Kingdom 
>  
>  
> featurespace.com <https://www.featurespace.com/> | Twitter <https://twitter.com/FeaturespaceLtd> | LinkedIn <https://www.linkedin.com/company/featurespace> 
>  
> <image001.png>
>  
>  
> <image002.png>
>  
>  
> This message, and any files/attachments transmitted together with it, is intended for the use only of the person (or persons) to whom it is addressed. It may contain information which is confidential and/or protected by legal privilege. Accordingly, any dissemination, distribution, copying or use of this message, or any part of it or anything sent together with it, other than by intended recipients, may constitute a breach of civil or criminal law and is hereby prohibited. Unless otherwise stated, any views expressed in this message are those of the person sending it and not the sender's employer. No responsibility, legal or otherwise, of whatever nature, is accepted as to the accuracy of the contents of this message or for the completeness of the message as received. Anyone who is not the intended recipient of this message is advised to make no use of it and is requested to contact Featurespace Limited as soon as possible. Any recipient of this message who has knowledge or suspects that it may have been the subject of unauthorised interception or alteration is also requested to contact Featurespace Limited.