Thanks Mark, in regards to failover I completely agree, I am wondering more
about performance and memory usage if the indexes are large and wondering
if the separate Java instances under heavy load would more or less
performant. Currently we deploy a single core per instance but deploy
multiple instances per machine
On Wednesday, February 8, 2012, Mark Miller <markrmil...@gmail.com> wrote:
>
> On Feb 8, 2012, at 9:52 PM, Jamie Johnson wrote:
>
>> In solr cloud what is a better approach / use of resources having
multiple
>> cores on a single instance or multiple instances with a single core? What
>> are the benefits and drawbacks of each?
>
>
> It depends I suppose. If you are talking about on a single machine, I'd
prefer using multiple cores over multiple Solr instances. I think it's just
easier to manage. You have to be sensible about that though - if all the
replicas for a shard are on the same machine, in the same instance, as
different cores, you don't have a lot of room for error - if that box goes
down, goodbye. But you can certainly mix and match instances and cores.
>
> One interesting thing you can do is a poor mans micro sharding - put a
few shards per machine - then later when you add more nodes to your
cluster, you can bring up a core on one of the new machines, it will catch
up, then you could unload that core on the original machine and replicas.
Then start up any other new nodes to add replicas for the moved shard.
Roughly and/or something like that anyway - I haven't thought it through
thoroughly, but Yonik has brought it up before, and it seems pretty easily
doable.
>
> - Mark Miller
> lucidimagination.com
>
>
>
>
>
>
>
>
>
>
>
>
