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
about the old users, their data will be still added to the
server1. How to address this issue. Is rebuilding the index the only way.
Could any one share their experience, How they solved scale out problems?
Regards
Ganesh
- Original Message -
From: "Anshum"
To:
Se
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 s
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
On Mon, Feb 8, 2010 at 9:33 AM, Chris Lu wrote:
> Since you already have RMI interface, maybe you can parallel search on
> several nodes, collect the data, pick top ones, and send back results via
> RMI.
>
One thing to be careful about this, which you might already be aware of:
Query (and subcla
is taking huge amount of RAM. We want to add multiple nodes, and scale out the search.
Currently my applaication supports RMI interface and it return appliaction specific result set objects as hits. I could host multiple search instance in different nodes, then i may need to sort / combine the
> Any thoughts on scaling / clustering? Whether i need to use Hadoop / Carrot
> etc...
>
Carrot2 does search results clustering (by content), while what you probably
need is server/index clustering. See the other responses in this thread for
suggestions.
S.
Solr has more powerful scalability than lucene, maybe you can try that
On Mon, Feb 8, 2010 at 6:14 PM, Ganesh wrote:
> Our indexes is growing and the sorted cache is taking huge amount of RAM.
> We want to add multiple nodes, and scale out the search.
>
> Currently my applaication
http://katta.sourceforge.net/ sounds well worth a look.
--
Ian.
On Mon, Feb 8, 2010 at 10:14 AM, Ganesh wrote:
> Our indexes is growing and the sorted cache is taking huge amount of RAM. We
> want to add multiple nodes, and scale out the search.
>
> Currently my applaication
Our indexes is growing and the sorted cache is taking huge amount of RAM. We
want to add multiple nodes, and scale out the search.
Currently my applaication supports RMI interface and it return appliaction
specific result set objects as hits. I could host multiple search instance in
different
10 matches
Mail list logo
