Jörg,

Thanks for the input. I have read many tutorials, guides (official one 
too). Just I want to re-route in more automagic way. Like routing evenly to 
the shard and duplicating mostly used shard to other shards maybe.

30 Mart 2015 Pazartesi 10:33:19 UTC+3 tarihinde Jörg Prante yazdı:
>
> Elasticsearch is open source, so reading (and using and modifying) the 
> algorithms is possible. There is also a lot of introductory material 
> available online, and I recommend "Elasticsearch - The definitive guide" if 
> you want paperwork.
>
> If you create an index, ES creates shards for this index (by default 5), 
> and different nodes receive one of such shards, so indexing and search is 
> automatically distributed over the participating nodes. ES keeps a map of 
> shards in the cluster state, so every node is able to route a query or an 
> index command. You don't need to manually route queries to shards.
>
> You can force ES to put all data on 3rd node, and in that case, you 
> already know what you want... there is no surprise. ES follows the 
> principle of least surprise.
>
> Jörg
>
> On Mon, Mar 30, 2015 at 5:07 AM, MrBu <metin....@gmail.com <javascript:>> 
> wrote:
>
>> Other than Lucene's own research papers, what are the research papers or 
>> special algorithms that is being used by Elastic? I couldn't find a list it 
>> in the documents.
>>
>> Are the special algorithms used (and which ones are used in where) for 
>> example what is the algorithm used in in load distribution or just round 
>> robin algorithm?
>>
>> I really want to get in deep with Elastic :)
>>
>> This way I could have more knowledge. Example, suppose there are 20 
>> nodes, and surprisingly (and somehow) only the data in 3rd node is being 
>> searched all the time. (say these are popular documents somehow gathered 
>> only in this node) so Elastic weights this load into all cluster by 
>> dividing this data to other nodes ?  Or will it always use only 3rd node? 
>> There are tons of questions in my mind, waiting to be answered. Only 
>> possible way to read the algorithms . It would help me a lot.
>>
>> Thanks
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "elasticsearch" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to elasticsearc...@googlegroups.com <javascript:>.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/elasticsearch/75907f69-38be-49fb-bf69-2f5dbf83cc45%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/elasticsearch/75907f69-38be-49fb-bf69-2f5dbf83cc45%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/elasticsearch/24dc8be9-a80a-4e1c-8c2a-0a8f95301287%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to