Thanks for the feedback On May 26, 2016 10:26 AM, "Camille Fournier" <[email protected]> wrote:
> AFAIK you'll have to implement this yourself in a client somewhere. A > script that watched for changes in the main DC and wrote them to the other > zk instances. Alternately you could put observer nodes for this in the > other dcs and have the client configured specifically to connect and read > from this set of nodes for this data. But nothing out of the box will get > this for you. > On May 26, 2016 1:16 PM, "David Capwell" <[email protected]> wrote: > > > We have multiple data centers and a ZK cluster deployed in each. One > > of the needs of our application is to have a specific feature see the > > same state in each DC (though if propagation takes a long time, thats > > fine, we just eventually consistency cross DCs), but only one DC will > > ever do the writing. > > > > What I have been trying to look for is a ability to replicate a > > specific path (the path this feature uses) to the other ZK clusters, > > but have not been in luck of finding such a thing. > > > > Thought about using a observer as well, but for each ZK cluster we > > need it to behave like a normal cluster isolated to the DC for every > > other use-case we have for ZK (membership/configs/etc.). > > > > Does anyone know of something out there that I could leverage? > > > > Thanks for your time reading this email. > > >
