What happen if you change size to 10?

David

> Le 10 déc. 2014 à 03:53, Xiaolin Xie <[email protected]> a écrit :
> 
> Hi Elastic Search developers
> 
> I am new to ES. We had some performance issues with our Elastic Search 
> system, and we would like to get some ideas/thoughts about this issue from 
> your guys.
> 
> Here is our use case: we have three types of documents in one index: 
> “campaign_group”, “campaign”, and “ad”. “campaign_group” is the parent of 
> “campaign”, and “campaign” is the parent of “ad”.  Each document type has 
> about 10 simple properties, such as string, long, short. The three kinds of 
> documents all have a property “user”(long) and a property 
> “run_status”(short). Documents are hashed by “user”, documents with the same 
> “user” are mapped into the same shard.
> 
> We have about 1.4 billion documents in total. We have 200 shards, 3 master 
> node, and 21 data nodes, and each shard has too replica.  The total data size 
> is 1.5TB. We are running elasticsearch 1.21.
> 
> 
> Queries are made against specific shard by routing. The flowing query(1) 
> checks the run_status of “ads”(run_status is a short type), and it takes 
> about 100 milliseconds. The query(2) checks both the run_status of “ad”, and 
> the run_status of its parent, and it takes about 2000 milliseconds.  It looks 
> like there are some performance issues with the has_parent filter.
> 
> Do your guys have any thoughts about this problem? Is it expected(because ES 
> cannot support has_parent well)? Or something else cloud result this problem? 
> Or we should upgrade our Elastic Search version?
> 
> 
> Please let me know if you need any other information about our uses cases. 
> 
> Any thoughts/ideas will be highly appreciated.
> 
> ========================Query(1) ========================
> 
> {
> 
>   "filter":{
> 
>     "and":[
> 
>       {
> 
>         "term":{
> 
>           "user":1436594776581528
> 
>         }
> 
>       },
> 
>       {
> 
>         "terms":{
> 
>           "run_status":[
> 
>             1
> 
>           ]
> 
>         }
> 
>       }
> 
>     ]
> 
>   },
> 
>   "sort":{
> 
>     "_uid":"desc"
> 
>   },
> 
>   "size":1000000,
> 
>   "from":0
> 
> }
> 
>  
> 
> ===========================Query(2)====================
> 
> {
> 
>   "filter":{
> 
>     "and":[
> 
>       {
> 
>         "term":{
> 
>           "user":1436594776581528
> 
>         }
> 
>       },
> 
>       {
> 
>         "terms":{
> 
>           "run_status":[
> 
>             1
> 
>           ]
> 
>         }
> 
>       },
> 
>       {
> 
>           "has_parent" : {
> 
>               "parent_type": "campaign",
> 
>               "filter" : {
> 
>                   "terms" : {
> 
>                       "run_status" : [1]
> 
>                   }
> 
>               }
> 
>           }
> 
>       }
> 
>     ]
> 
>   },
> 
>   "sort":{
> 
>     "_uid":"desc"
> 
>   },
> 
>   "size":1000000,
> 
>   "from":0
> 
> }
> 
>  
> 
> -- 
> 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 [email protected].
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/elasticsearch/220b1d9a-da80-416c-8b8d-d7cc3efc8b5a%40googlegroups.com.
> 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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/elasticsearch/B9C2DFF9-2368-4D0E-B09A-96D6A7EFBB78%40pilato.fr.
For more options, visit https://groups.google.com/d/optout.

Reply via email to