On Fri, 2011-02-04 at 05:54 +0100, Ganesh wrote:
> 2. Consider a scenario I am sharding based on the User, I am having single
> search server and It is handling 1000 members. Now as the memory consumption
> is high, I have added one more search server. New users could access the
> second server
nt: Friday, January 21, 2011 12:04 PM
Subject: Re: Scale out design patterns
> Hi Ganesh,
> I'd suggest, if you have a particular dimension/field on which you could
> shard your data such that the query/data breakup gets predictable, that
> would be a good way to scale out e.g. if you h
Hi Ganesh,
I'd suggest, if you have a particular dimension/field on which you could
shard your data such that the query/data breakup gets predictable, that
would be a good way to scale out e.g. if you have users which are equally
active/searched then you may want to split their data on a simple mod
Hello all,
Could you any one guide me what all the various ways we could scale out?
1. Index: Add data to the nodes in round-robin.
Search: Query all the nodes and cluster the results using carrot2.
2.Horizontal partitioning and No shared architecture,
Index: Split the data based on
