NPE in ContextIndexSearcher

dpilato · May 17, 2011, 7:19am

Hi,

I'm using the ElasticSearch FrontEnd client ( https://github.com/mobz/elasticsearch-head ). The last version in master...

I use it with ES 0.16.1.

When I try to search (simple match_all query), I get a NPE.

Here is what ESFrontEnd is sending to ES :
{
query: {
bool: {
must: [
{
match_all: { }
}
]
must_not: [ ]
should: [ ]
}
}
from: 0
size: 50
sort: [ ]
facets: { }
}

In ES logs, I get :
[2011-05-17 09:08:40,592][DEBUG][action.search.type ] [The Entity] [dau][4], node[6bzzlBiuTVu52IhXYwE4Qw], [P], s[STARTED]: Failed to execute [org.elasticsearch.action.search.SearchRequest@1b6ba28]
java.lang.NullPointerException
at org.elasticsearch.search.internal.ContextIndexSearcher.removeCollectors(ContextIndexSearcher.java:81)
at org.elasticsearch.search.facet.FacetPhase.execute(FacetPhase.java:72)
at org.elasticsearch.search.query.QueryPhase.execute(QueryPhase.java:220)
at org.elasticsearch.search.SearchService.executeQueryPhase(SearchService.java:222)
at org.elasticsearch.search.action.SearchServiceTransportAction.sendExecuteQuery(SearchServiceTransportAction.java:134)
at org.elasticsearch.action.search.type.TransportSearchQueryThenFetchAction$AsyncAction.sendExecuteFirstPhase(TransportSearchQueryThenFetchAction.java:76)
at org.elasticsearch.action.search.type.TransportSearchTypeAction$BaseAsyncAction.performFirstPhase(TransportSearchTypeAction.java:192)
at org.elasticsearch.action.search.type.TransportSearchTypeAction$BaseAsyncAction.access$000(TransportSearchTypeAction.java:75)
at org.elasticsearch.action.search.type.TransportSearchTypeAction$BaseAsyncAction$1.run(TransportSearchTypeAction.java:151)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)

It seems that there is a NPE in ContextIndexSearcher.removeCollectors().
Something strange is that I'm not in DEBUG mode. I use the standard logging setup file but the trace seems to be a DEBUG trace...

Thanks for any help.
Should I open a bug for that ?

Cheers

kimchy · May 17, 2011, 1:02pm

Heya,

Yea, this looks like a possible bug when providing empty facets element. Opened an issue for it: Search: Empty facets element causes search failures · Issue #938 · elastic/elasticsearch · GitHub.

-shay.banon
On Tuesday, May 17, 2011 at 10:19 AM, dpilato wrote:

Hi,

I'm using the Elasticsearch FrontEnd client (
GitHub - mobz/elasticsearch-head: A web front end for an elastic search cluster ). The last version in master...

I use it with ES 0.16.1.

When I try to search (simple match_all query), I get a NPE.

Here is what ESFrontEnd is sending to ES :
{
query: {
bool: {
must: [
{
match_all: { }
}
]
must_not:
should:
}
}
from: 0
size: 50
sort:
facets: { }
}

In ES logs, I get :
[2011-05-17 09:08:40,592][DEBUG][action.search.type ] [The Entity]
[dau][4], node[6bzzlBiuTVu52IhXYwE4Qw], [P], s[STARTED]: Failed to execute
[org.elasticsearch.action.search.SearchRequest@1b6ba28]
java.lang.NullPointerException
at
org.elasticsearch.search.internal.ContextIndexSearcher.removeCollectors(ContextIndexSearcher.java:81)
at org.elasticsearch.search.facet.FacetPhase.execute(FacetPhase.java:72)
at org.elasticsearch.search.query.QueryPhase.execute(QueryPhase.java:220)
at
org.elasticsearch.search.SearchService.executeQueryPhase(SearchService.java:222)
at
org.elasticsearch.search.action.SearchServiceTransportAction.sendExecuteQuery(SearchServiceTransportAction.java:134)
at
org.elasticsearch.action.search.type.TransportSearchQueryThenFetchAction$AsyncAction.sendExecuteFirstPhase(TransportSearchQueryThenFetchAction.java:76)
at
org.elasticsearch.action.search.type.TransportSearchTypeAction$BaseAsyncAction.performFirstPhase(TransportSearchTypeAction.java:192)
at
org.elasticsearch.action.search.type.TransportSearchTypeAction$BaseAsyncAction.access$000(TransportSearchTypeAction.java:75)
at
org.elasticsearch.action.search.type.TransportSearchTypeAction$BaseAsyncAction$1.run(TransportSearchTypeAction.java:151)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)

It seems that there is a NPE in ContextIndexSearcher.removeCollectors().
Something strange is that I'm not in DEBUG mode. I use the standard logging
setup file but the trace seems to be a DEBUG trace...

Thanks for any help.
Should I open a bug for that ?

Cheers

--
View this message in context: http://elasticsearch-users.115913.n3.nabble.com/NPE-in-ContextIndexSearcher-tp2951467p2951467.html
Sent from the Elasticsearch Users mailing list archive at Nabble.com.

Alois_Cochard · May 24, 2011, 6:10am

I have same exception on my cluster when trying to open elasticsearch-
head browser

On May 17, 3:02 pm, Shay Banon shay.ba...@elasticsearch.com wrote:

Heya,

Yea, this looks like a possible bug when providing empty facets element. Opened an issue for it:Search: Empty facets element causes search failures · Issue #938 · elastic/elasticsearch · GitHub.

-shay.banon

On Tuesday, May 17, 2011 at 10:19 AM, dpilato wrote:

Hi,

I'm using the Elasticsearch FrontEnd client (
GitHub - mobz/elasticsearch-head: A web front end for an elastic search cluster). The last version in master...

I use it with ES 0.16.1.

When I try to search (simple match_all query), I get a NPE.

Here is what ESFrontEnd is sending to ES :
{
query: {
bool: {
must: [
{
match_all: { }
}
]
must_not:
should:
}
}
from: 0
size: 50
sort:
facets: { }
}

In ES logs, I get :
[2011-05-17 09:08:40,592][DEBUG][action.search.type ] [The Entity]
[dau][4], node[6bzzlBiuTVu52IhXYwE4Qw], [P], s[STARTED]: Failed to execute
[org.elasticsearch.action.search.SearchRequest@1b6ba28]
java.lang.NullPointerException
at
org.elasticsearch.search.internal.ContextIndexSearcher.removeCollectors(Con textIndexSearcher.java:81)
at org.elasticsearch.search.facet.FacetPhase.execute(FacetPhase.java:72)
at org.elasticsearch.search.query.QueryPhase.execute(QueryPhase.java:220)
at
org.elasticsearch.search.SearchService.executeQueryPhase(SearchService.java :222)
at
org.elasticsearch.search.action.SearchServiceTransportAction.sendExecuteQue ry(SearchServiceTransportAction.java:134)
at
org.elasticsearch.action.search.type.TransportSearchQueryThenFetchAction$As yncAction.sendExecuteFirstPhase(TransportSearchQueryThenFetchAction.java:76 )
at
org.elasticsearch.action.search.type.TransportSearchTypeAction$BaseAsyncAct ion.performFirstPhase(TransportSearchTypeAction.java:192)
at
org.elasticsearch.action.search.type.TransportSearchTypeAction$BaseAsyncAct ion.access$000(TransportSearchTypeAction.java:75)
at
org.elasticsearch.action.search.type.TransportSearchTypeAction$BaseAsyncAct ion$1.run(TransportSearchTypeAction.java:151)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.j ava:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java: 908)
at java.lang.Thread.run(Thread.java:619)

It seems that there is a NPE in ContextIndexSearcher.removeCollectors().
Something strange is that I'm not in DEBUG mode. I use the standard logging
setup file but the trace seems to be a DEBUG trace...

Thanks for any help.
Should I open a bug for that ?

Cheers

--
View this message in context:http://elasticsearch-users.115913.n3.nabble.com/NPE-in-ContextIndexSe...
Sent from the Elasticsearch Users mailing list archive at Nabble.com.