Thanks for the reply.
My goal is to have a redundant copy of all 8 currently running, but
non-redundant shards. This setup (8 nodes with no replicas) was a test
and it has proven quite functional from a performance perspective.
Loading, though, takes almost 3 weeks so I'm really not in a position to
redesign the distribution, though I can add nodes.
I have acquired another resource, a very large machine that I'd like to
use to hold the replicas of the currently deployed 8-nodes.
I realize I can run 8 jetty/tomcats and accomplish my goal but that is a
maintenance headache and is really a last resort. I really would just
like to be able to deploy this big machine with 'numShards=8'.
Is that possible or do I really need to have 8 other nodes running?
David
On 12/22/2013 03:58 PM, Furkan KAMACI wrote:
Hi David;
When you start up 8 nodes within that machine they will be replicas of each
shards and you will accomplish what you want. However if you can give more
detail about your hardware infrastructure and needs I can offer you a
design.
Thanks;
Furkan KAMACI
22 Aralık 2013 Pazar tarihinde David Santamauro <david.santama...@gmail.com>
adlı kullanıcı şöyle yazdı:
any hint?
On 12/22/2013 06:48 AM, David Santamauro wrote:
Hi,
I have an 8-node setup currently with 1 shard per node (no redundancy).
These 8 nodes are smaller machines not capable of supporting the entire
collection..
I have another machine resource that can act as other node and this last
node is capable of holding the entire collection. I'd like to make this
large node hold a replica of all the other 8 nodes' shards for
redundancy as well as performance.
Is this possible? ... and what would be the configuration magic needed
to accomplish this? This collection is very large (1.4TB) and as you can
imagine, I don't want to fiddle around trying configuration alternatives
assuming each try would lead to a replication of 1.4TB of data.
Any help would be greatly appreciated.
David
