Shay, you are going to kill me but I have one more question. It has to
do with uniqueness. Our documents kind of look like this:
"tags": "Princess Cruises ships to resume calls in Egypt .
http://usat.ly/if6AaO hottraveldeals2 Hot Travel Deals",
And what if I wanted to make sure the record_id is unique to prevent
dupes in there? Is there a way to do that?
On Apr 21, 3:52 pm, Shay Banon shay.ba...@elasticsearch.com wrote:
This is the auto generate id elasticsearch generates. Its a UUID that has been base64. A long value is much more problematic to do in distributed systems, but, you can provide one (the id) if you want.
On Friday, April 22, 2011 at 12:41 AM, electic wrote:
Sounds great. One last question. I noticed the IDs are alphanumeric:
is there a way to make them long integers?
On Apr 21, 8:37 am, Clinton Gormley clin...@iannounce.co.uk wrote:
On Thu, 2011-04-21 at 08:22 -0700, electic wrote:
Thanks guys! I think I am just going to go ahead and use the POST part
of the API instead of trying to pass the whole thing via the URL. Made
life easier. On an un-related note. We are seriously looking at adding
10 more servers to the cluster to see how easy that is. Currently,
each server is a quad core xeon with 16GB of RAM and a 600GB SAS disk.
At this time, we have 5 shards. My understanding is that 5 shards = 5
servers. Now let's say I had 10 nodes and we have 15 servers. How do
we best migrate the index or modify the index to take advantage of
those 10 nodes?
You have primary shards and replicas. By default, you'd have 5 primary
shards and 1 replica (ie 1 replica for each primary shard)
So if you start 10 nodes, then you would have one shard on each (either
a primary or a replica).
You can dynamically increase your number of replicas, so if you set
replicas to 2, then you'd have enough shards to fill 15 nodes with one
If you want to (and need to) increase the number of primary shards, then
you will need to reindex to a new index that has been created with a
higher number of primary shards.