ES version 16.0 queries

Hi Shay,

Please help me out by answering the following queries. The Es version
I am using is 16.0.

1.What is the maximum child type associated with parent type? Is there
any limitation on this?
2.What is the best configuration for the production server that we can
equip?
3.What is the maximum hash child we can send in a single query? For
the same scenario, if multiple users uses.
4.When I try to hit my application, it gradually increases the memory
of ES is going up to the maximum level which I setup in server. When
this will come to normal position? Do I need to give any query for
normalizing the memory level?
5.I use to get the following error “Remote Transport Exception” and
when I check for memory, it shows normal usage only. Why is it
happening like this?

Thanks
Katrinaa

On Friday, July 15, 2011 at 12:19 AM, Katrina K wrote:

Hi Shay,

Please help me out by answering the following queries. The Es version
I am using is 16.0.

1.What is the maximum child type associated with parent type? Is there
any limitation on this?
There isn't a limit for it.
2.What is the best configuration for the production server that we can
equip?
Its a too open ended question to answer...
3.What is the maximum hash child we can send in a single query? For
the same scenario, if multiple users uses.
There is no limit, the more you have, the slower the query will be.
4.When I try to hit my application, it gradually increases the memory
of ES is going up to the maximum level which I setup in server. When
this will come to normal position? Do I need to give any query for
normalizing the memory level?
Parent child requires loading all the id values to memory, you might hit that. You need to increase the memory allocated to elasticsearch or start more nodes if it does not have enough mem.
5.I use to get the following error “Remote Transport Exception” and
when I check for memory, it shows normal usage only. Why is it
happening like this?
Can you gist the exception failure?

Thanks
Katrinaa

Hi Shay,

While querying Elastic search with has-child query concurrently we are
getting the following error.

We are searching with following characteristics.

  1. Search type as "dfs_query_then_fetch".

  2. Query is based on more than 4 child tables

  3. More than 7 users concurrently hitting Elastic search.

  4. Occasionaly we are getting following errors...

{"took":407125,"timed_out":false,"_shards":{"total":6,"successful":
2,"failed":4,"failures":[{"reason":"RemoteTransportException[[Omega
the Unknown][inet[/10.41.23.16:9300]][search/phase/fetch/id]]; nested:
SearchContextMissingException[No search context found for id [9998]];
"},{"reason":"RemoteTransportException[[Ebon Seeker][inet[/
10.41.23.19:9300]][search/phase/fetch/id]]; nested:
SearchContextMissingException[No search context found for id [7908]];
"},{"reason":"RemoteTransportException[[Ebon Seeker][inet[/
10.41.23.19:9300]][search/phase/fetch/id]]; nested:
SearchContextMissingException[No search context found for id [7909]];
"},{"reason":"RemoteTransportException[[Sweetface][inet[/
10.41.23.21:9300]][search/phase/fetch/id]]; nested:
SearchContextMissingException[No search context found for id [5086]];
"}]}

Thanks,
Katrina

On Jul 15, 10:21 am, Shay Banon shay.ba...@elasticsearch.com wrote:

On Friday, July 15, 2011 at 12:19 AM, Katrina K wrote:

Hi Shay,

Please help me out by answering the following queries. The Es version
I am using is 16.0.

1.What is the maximum child type associated with parent type? Is there
any limitation on this?

There isn't a limit for it.> 2.What is the best configuration for the production server that we can

equip?

Its a too open ended question to answer...> 3.What is the maximum hash child we can send in a single query? For

the same scenario, if multiple users uses.

There is no limit, the more you have, the slower the query will be.> 4.When I try to hit my application, it gradually increases the memory

of ES is going up to the maximum level which I setup in server. When
this will come to normal position? Do I need to give any query for
normalizing the memory level?

Parent child requires loading all the id values to memory, you might hit that. You need to increase the memory allocated to elasticsearch or start more nodes if it does not have enough mem.> 5.I use to get the following error “Remote Transport Exception” and

when I check for memory, it shows normal usage only. Why is it
happening like this?

Can you gist the exception failure?

Thanks
Katrinaa- Hide quoted text -

  • Show quoted text -