Nope, cores are just a self-contained index, really. What is the point of breaking them up? If you have some kind of rolling currency (i.e. you only want to keep the last N days/weeks/months) then you can always delete-by-query to age-out the relevant docs.
You'll be able to fit more on one server if it's in a single core, but what the ratio is I'm not sure. My take would be go for the simplest, which would be a single core (index) for administrative purposes if for no other reason, but that may well just be personal preference... Best Erick On Fri, Jun 3, 2011 at 10:10 AM, JohnRodey <timothydd...@yahoo.com> wrote: > Thanks Erick for the response. > > So my data structure is the same, i.e. they all use the same schema. Though > I think it makes sense for us to somehow break apart the data, for example > by the date it was indexed. I'm just trying to get a feel for how large we > should aim to keep those (by day, by week, by month, etc...). > > So it sounds like we should aim to keep them at a size that one solr server > can host to avoid serving multiple cores. > > One question, there is no real difference (other than configuration) from a > server hosting its own index vs. it hosting one core, is there? > > Thanks! > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Better-to-have-lots-of-smaller-cores-or-one-really-big-core-tp3017973p3019686.html > Sent from the Solr - User mailing list archive at Nabble.com. >
