zookeeper
This is a ZooKeeper client store for accessors using ZooKeeperConf traits to read/write from ZooKeeper.
This is a simple mixable trait for client applications to fetch ports from ZooKeeper during initialisation or register themselves on a path.
This is a simple mixable trait for client applications to fetch ports from ZooKeeper during initialisation or register themselves on a path. In our eco-system, this is generally mixed in to objects extending TwitterServer or ClientBuilder.
The point is to allow very easy access to the local ZooKeeper node available in a Mesos deployment to fetch "the other" host:port pairs in the eco-system, allowing Thrift clients to auto-generate themselves with a trivial awaiting of a Future. The same mechanism can be used for any type of client.
This also allows applications to register themselves to a ZooKeeper path making them discoverable by other clients.
This is a ZooKeeper client store for accessors using ZooKeeperConf traits to read/write from ZooKeeper. Its sole purpose is to centralise access to ZooKeeper hosts and not necessitate access to multiple clients.
Using a single global client object with a synchronized access pattern and just-in-time init we can solve the problem of localhost Mesos based deployments. In a Mesos environment the ZooKeeper host is always fixed and every client application can easily talk to the same node to obtain data.
Users can easily override all the default implementation details and assumptions this store has and roll out their own communication instance with ZooKeeper. For now, this is mostly tailored to our Mesos deployment mechanism.