Hi Martin, FYI, there is ZOOKEEPER-1147 which was supposed to target a relatively close objective: "We are planning on having about a 1 million clients connect to a ZooKeeper ensemble through a set of 50-100 observers. Majority of these clients are read only - ie they do not do any updates or create ephemeral nodes."
It's not exactly the same as yours, as some of the clients are pure listeners: they never write. The JIRA was not discussed that much, but someone assigned to himself 2 months ago, so may be something new will happen soon? Cheers, Nicolas On Tue, Sep 18, 2012 at 6:11 AM, Ted Dunning <[email protected]> wrote: > sorry. > > Hit send a bit early. > > I meant a special purpose proxy that limits the amount of notification that > goes out by changing the semantics a bit. You really don't want millions > of change notices to go out all at once. > > On Mon, Sep 17, 2012 at 8:46 PM, Morris Bernstein < > [email protected]> wrote: > > > Uhm, yeah, that's what I meant... > > On Sep 17, 2012 7:59 PM, "Ted Dunning" <[email protected]> wrote: > > > > > Another option is to use a proxy. > > > > > > On Mon, Sep 17, 2012 at 6:44 PM, Morris Bernstein < > > > [email protected]> wrote: > > > > > > > The obvious solution would be running multiple Zookeepers > > hierarchically. > > > > Each server would take, say, 1000 clients. Each server would be a > > client > > > > of an uber Zookeeper. It'll increase latency some, but it scales. > > > > On Sep 17, 2012 3:57 PM, "Martin Kou" <[email protected]> wrote: > > > > > > > > > Hi all, > > > > > > > > > > I'm having a use case where there're potentially millions of client > > > > > processes connected to a Zookeeper cluster, but only a very small > > > > > proportion of them would be actively sending requests or receiving > > any > > > > data > > > > > (say, about 1000 of them every second) at any time. Has anyone > tried > > > this > > > > > before? > > > > > > > > > > Best Regards, > > > > > Martin Kou > > > > > > > > > > > > > > >
