Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (athena.apache.org: local policy)
Date: Thu, 11 Oct 2012 11:40:19 +0300
From: svilen <az@svilendobrev.com>
To: user@couchdb.apache.org
Subject: Re: can i listen to changes of whole server, not per-db?
Message-ID: <20121011114019.5dd33b7f@eee-az>
In-Reply-To: 
 <CAJNb-9pONOt6CsisnH9YQ_vypQv+fQfB=zxHRuPARXBPkfP=ww@mail.gmail.com>
References: <20121007085933.472ff68a@svilendobrev.com>
	<CAL+Y1nvzj8qsqMhyb0mLMFLTcgzFosz3GOovQiTWk2n0uroKnw@mail.gmail.com>
	<CAJNb-9pONOt6CsisnH9YQ_vypQv+fQfB=zxHRuPARXBPkfP=ww@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

how about hierarchical replication then ?

kind-a
 - have a list of observed dbs
 - listen to some special db/feed that gets updated when some
   of above dbs changes
 - replication over above scheme (i.e. replicate continiously the
   speical db and replicate others once-off at each update)

i may do the above, as otherwise there will be 10000s of connections
doing nothing (but still kept alive).=20

svil


On Sun, 7 Oct 2012 09:43:15 +0200
Benoit Chesneau <bchesneau@gmail.com> wrote:

> On Sun, Oct 7, 2012 at 9:27 AM, Dave Cottlehuber <dch@jsonified.com>
> wrote:
> > On 7 October 2012 07:59, svilen <az@svilendobrev.com> wrote:
> >> g'day
> >>
> >> i'm going to have thousands of databases. They are all of similar
> >> kind, but belong to different (groups of) users, so can't be
> >> bundled into one. And setupping 10000 connections to
> >> couchdb/dbXXXXX/_changes doesn't seem very neat, even if on same
> >> machine.
> >
> > Not possible today unfortunately.
> >
> > Has anybody got any numbers or experience on practical limits of
> > _changes feeds connections to a single server?
> >
> > A+
> > Dave
>=20
>=20
> For rcouch I have written a plugin that listen on all dbs changes:
>=20
> https://github.com/refuge/couch_dbupdates
>=20
> It only notify you when a db is updated for any reason. Then you can
> use _changes to get latest changes for this db.
>=20
>=20
> I'm actually actively working on porting patches to couch and prepare
> some branches. If some think it would be interesting to have it in
> couch I can port it as well.
>=20
> - beno=C3=AEt