May be running hot_threads API would tell you more?
BTW which version is it ?
--
David ;-)
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
> Le 6 mai 2015 à 10:33, Chetan Dev <cheten....@carwale.com> a écrit :
>
> Hi,
>
> Servers were at 20% cpu but after sudden restart java started taking more cpu
> currently cpu utilization is 90%
>
> I digged into the logs and found this
>
> at
> org.elasticsearch.search.SearchService.parseSource(SearchService.java:687)
> at
> org.elasticsearch.search.SearchService.createContext(SearchService.java:543)
> at
> org.elasticsearch.search.SearchService.createAndPutContext(SearchService.java:515)
> at
> org.elasticsearch.search.SearchService.executeQueryPhase(SearchService.java:277)
> at
> org.elasticsearch.search.action.SearchServiceTransportAction$5.call(SearchServiceTransportAction.java:231)
> at
> org.elasticsearch.search.action.SearchServiceTransportAction$5.call(SearchServiceTransportAction.java:228)
> at
> org.elasticsearch.search.action.SearchServiceTransportAction$23.run(SearchServiceTransportAction.java:559)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.NumberFormatException: For input string:
> "${map_makes:${lowercase:}}"
> at
> java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
> at java.lang.Long.parseLong(Long.java:578)
> at java.lang.Long.parseLong(Long.java:631)
> at
> org.elasticsearch.index.mapper.core.NumberFieldMapper.parseLongValue(NumberFieldMapper.java:354)
> at
> org.elasticsearch.index.mapper.core.LongFieldMapper.indexedValueForSearch(LongFieldMapper.java:169)
> at
> org.elasticsearch.index.mapper.core.AbstractFieldMapper.termsFilter(AbstractFieldMapper.java:483)
> at
> org.elasticsearch.index.query.TermsFilterParser.parse(TermsFilterParser.java:201)
> at
> org.elasticsearch.index.query.QueryParseContext.executeFilterParser(QueryParseContext.java:347)
> at
> org.elasticsearch.index.query.QueryParseContext.parseInnerFilter(QueryParseContext.java:328)
> at
> org.elasticsearch.index.query.BoolFilterParser.parse(BoolFilterParser.java:92)
> at
> org.elasticsearch.index.query.QueryParseContext.executeFilterParser(QueryParseContext.java:347)
> at
> org.elasticsearch.index.query.QueryParseContext.parseInnerFilter(QueryParseContext.java:328)
> at
> org.elasticsearch.index.query.BoolFilterParser.parse(BoolFilterParser.java:92)
> at
> org.elasticsearch.index.query.QueryParseContext.executeFilterParser(QueryParseContext.java:347)
> at
> org.elasticsearch.index.query.QueryParseContext.parseInnerFilter(QueryParseContext.java:328)
> at
> org.elasticsearch.index.query.IndexQueryParserService.parseInnerFilter(IndexQueryParserService.java:295)
> at
> org.elasticsearch.search.aggregations.bucket.filter.FilterParser.parse(FilterParser.java:42)
> at
> org.elasticsearch.search.aggregations.AggregatorParsers.parseAggregators(AggregatorParsers.java:130)
> at
> org.elasticsearch.search.aggregations.AggregatorParsers.parseAggregators(AggregatorParsers.java:77)
> at
> org.elasticsearch.search.aggregations.AggregationParseElement.parse(AggregationParseElement.java:60)
> at
> org.elasticsearch.search.SearchService.parseSource(SearchService.java:671)
> ... 9 more
>
>
>
>
> [2015-05-06 12:27:16,506][DEBUG][action.search.type ] [AEPLES1] All
> shards failed for phase: [query]
>
>> On Wednesday, May 6, 2015 at 1:15:27 PM UTC+5:30, David Pilato wrote:
>> What is wrong ?
>>
>> I mean that if you are doing indexing for example, that's fine if your CPU
>> is used.
>> But may be you are running out of memory and GC is running all the time ?
>>
>> Hard to say without any details / logs...
>>
>> BTW me moved to https://discuss.elastic.co/
>>
>> --
>> David ;-)
>> Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
>>
>>> Le 6 mai 2015 à 09:28, Chetan Dev <chete...@carwale.com> a écrit :
>>>
>>> Hi,
>>>
>>> I am running elasticsearch 1.4.4 with java 1.8.0.25 on windows machine . i
>>> have assigned 2 Gb heap memory
>>> java.exe taking almost 70 per cpu ?
>>> everything else is working fine
>>> Can somebody please give right direction to diagnose what is causing this
>>> fluctuation
>>>
>>>
>>> Thanks
>>>
>>>
>>> --
>>> Please update your bookmarks! We moved to https://discuss.elastic.co/
>>> ---
>>> 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.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/elasticsearch/c2860555-c430-4301-b7ec-e25d4187bac6%40googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>
> --
> Please update your bookmarks! We moved to https://discuss.elastic.co/
> ---
> 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/186606d3-bd65-4325-bd15-090291ab8694%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
--
Please update your bookmarks! We moved to https://discuss.elastic.co/
---
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/FF215DAA-EC7E-49A4-BC8C-04BA144B1AA3%40pilato.fr.
For more options, visit https://groups.google.com/d/optout.
