lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From 韦震宇 <weizhe...@win-trust.com>
Subject Re: How can I create about 100000 independent indexes in Solr?
Date Thu, 27 Sep 2012 11:00:00 GMT
Hi, Tanguy
   Oh, I understand now. I don't have the issue as you. Though there
are so many customers in our site, but the fields they owned are same.
so few field fields are ok in my scene.
Best Regards!
Monton

----- Original Message ----- 
From: "Tanguy Moal" <tanguy.moal@gmail.com>
To: <solr-user@lucene.apache.org>
Sent: Thursday, September 27, 2012 4:34 PM
Subject: Re: How can I create about 100000 independent indexes in Solr?


Hello Monton,

I wanted to make sure that you understood me well : I really don't how well
does solr scale if the number of fields increases...

What I mean here is that the more distinct fields you index, the more
memory you will need.

So if in your schema, you have something like 15 fields declared, then
storing data for 100 distinct customers would generate 1500 fields in the
index.

I really don't know how well would that scale.

The simplest solution is one core per customer but the same issue (memory
consumption) will rise at some point, I guess.

There must be a clever way to do that...

--
Tanguy

2012/9/26 韦震宇 <weizhenyu@win-trust.com>

> Hi, Tanguy
>      I would do as your suggestion.
> Best Regards!
> Monton
> ----- Original Message -----
> From: "Tanguy Moal" <tanguy.moal@gmail.com>
> To: <solr-user@lucene.apache.org>; <te@statsbiblioteket.dk>
> Sent: Tuesday, September 25, 2012 11:05 PM
> Subject: Re: How can I create about 100000 independent indexes in Solr?
>
>
> That is an interesting issue...
> I was wondering if relying on dynamic fields could be an option...
>
> Something like :
>
> * <field_name>: <field_type>
> * customer : string
> * *_field_a1 : type_a
> * *_field_a2 : type_a
> * *_field_b1 : type_b
> * ...
>
> And the prefix each field by the customer name, so for customer1, indexed
> documents are as follow :
> * customer : customer1
> * customer1_field_a1 : value for field_a1
> * customer1_field_a2 : value for field_a2
> * customer1_field_b1 : value for field_b1
> * ...
> And for customer2 :
> * customer : customer2
> * customer2_field_a1 : value for field_a1
> * customer2_field_a2 : value for field_a2
> * customer2_field_b1 : value for field_b1
> * ...
>
> This solution is simple, and helps isolating each customers fields so
> features like suggester, spellcheck, ..., things relying on frequencies
> would work (as if in a single core)
>
> I just don't how well does solr scale if the number of fields increases...
>
> Then scaling could be achieved depending on number of doc / customer and
> number of customer / core (if amount of fields consumes resources)
>
> Could that help ?
>
> --
> Tanguy
>
> 2012/9/25 Toke Eskildsen <te@statsbiblioteket.dk>
>
> > On Tue, 2012-09-25 at 04:21 +0200, 韦震宇 wrote:
> > > The company I'm working in have a website to server more than 100000
> > > customers, and every customer should have it's own search cataegory.
> > > So I should create independent index for every customer.
> >
> > How many of the customers are active at any given time and how large are
> > the indexes? Depending on usage you might be able to have a limited
> > number of indexes open at any given time and opening new indexes on
> > demand.
> >
> >
>
Mime
View raw message