Hi Emmanuel, thanks for reply. So, I will try to implement my own load balancer which will be responsible for Shard selection. After that it will forward the request to RAIDb-1 load balancer which will choose a backend.
I will write here about my progress. Regards Jacek On Wed, Mar 5, 2008 at 11:34 AM, Emmanuel Cecchet <[EMAIL PROTECTED]> wrote: > Hi Jacek, > > From what I understood, Shard is supposed to do the request > dispatching. Now if you want the availability part to be handled by > Sequoia, you can use a RAIDb-1 Sequoia cluster (full replication) for > each Shard partition (and Sequoia will just do the load balancing among > replicas of the same partition). > If you really want to do the row-based partitioning in Sequoia then you > will have to implement your own load balancer or integrate parts of the > Shard logic into a Sequoia load balancer. > > Hope this helps, > Emmanuel > > > > I want to create some basic application which will use shards. I mean > > the application which will use many real databases partitioned in some > > way (by range, hash etc.). So I have one table which reside in > > multiple databases, but in one database I have only a part of rows. I > > want to use Sequoia as a request dispatcher. It will be responsible > > for select what database will be used to a given query. I read the > > documentation and didnt find similar solution. There is only RAIDb-0 > > which split database by tables. But I want to split rows in tables > > instead. How can I implement this using Sequoia? Should I implement my > > own load balancer? > > > > > -- > Emmanuel Cecchet - Research scientist > EPFL - LABOS/DSLAB - IN.N 317 > Phone: +41-21-693-7558 > > _______________________________________________ > Sequoia mailing list > [email protected] > https://forge.continuent.org/mailman/listinfo/sequoia > _______________________________________________ Sequoia mailing list [email protected] https://forge.continuent.org/mailman/listinfo/sequoia
