IndexMissingException when using MoreLike


(Ivan Brusic) #1

I have been getting occasional IndexMissingExceptions, but only when using
MoreLike. The request uses an alias and the exception points to the correct
index.

Not only do searches work fine, but the MoreLike request that failed
actually returns a proper response. Perhaps one node is incorrect? Hard to
debug due to multiple threads. Here is the exception:

org.elasticsearch.indices.IndexMissingException: [products-20120919-114007]
missing
at
org.elasticsearch.indices.InternalIndicesService.indexServiceSafe(InternalIndicesService.java:243)
at
org.elasticsearch.action.mlt.TransportMoreLikeThisAction$1.onResponse(TransportMoreLikeThisAction.java:114)
at
org.elasticsearch.action.mlt.TransportMoreLikeThisAction$1.onResponse(TransportMoreLikeThisAction.java:105)
at
org.elasticsearch.action.support.TransportAction$ThreadedActionListener$1.run(TransportAction.java:86)
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:662)

Running ES 0.19.8 via the TransportClient. The index does not have shards
on every node of the cluster due to the distribution of shards across the
nodes. Shouldn't be an issue, just an FYI.

Cheers,

Ivan

--


(Ivan Brusic) #2

Quick correction: the failed MoreLike request does not return a valid
response. My error handling code (inherited!) for exceptions was faulty.

On Wed, Sep 26, 2012 at 1:21 PM, Ivan Brusic ivan@brusic.com wrote:

I have been getting occasional IndexMissingExceptions, but only when using
MoreLike. The request uses an alias and the exception points to the correct
index.

Not only do searches work fine, but the MoreLike request that failed
actually returns a proper response. Perhaps one node is incorrect? Hard to
debug due to multiple threads. Here is the exception:

org.elasticsearch.indices.IndexMissingException:
[products-20120919-114007] missing
at
org.elasticsearch.indices.InternalIndicesService.indexServiceSafe(InternalIndicesService.java:243)
at
org.elasticsearch.action.mlt.TransportMoreLikeThisAction$1.onResponse(TransportMoreLikeThisAction.java:114)
at
org.elasticsearch.action.mlt.TransportMoreLikeThisAction$1.onResponse(TransportMoreLikeThisAction.java:105)
at
org.elasticsearch.action.support.TransportAction$ThreadedActionListener$1.run(TransportAction.java:86)
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:662)

Running ES 0.19.8 via the TransportClient. The index does not have shards
on every node of the cluster due to the distribution of shards across the
nodes. Shouldn't be an issue, just an FYI.

Cheers,

Ivan

--


(Igor Motov) #3

It looks like https://github.com/elasticsearch/elasticsearch/issues/2197
only instead of executing request on the node client, it fails when request
is getting executed on the node where your index doesn't have any shards.

On Wednesday, September 26, 2012 4:48:45 PM UTC-4, Ivan Brusic wrote:

Quick correction: the failed MoreLike request does not return a valid
response. My error handling code (inherited!) for exceptions was faulty.

On Wed, Sep 26, 2012 at 1:21 PM, Ivan Brusic <iv...@brusic.com<javascript:>

wrote:

I have been getting occasional IndexMissingExceptions, but only when
using MoreLike. The request uses an alias and the exception points to the
correct index.

Not only do searches work fine, but the MoreLike request that failed
actually returns a proper response. Perhaps one node is incorrect? Hard to
debug due to multiple threads. Here is the exception:

org.elasticsearch.indices.IndexMissingException:
[products-20120919-114007] missing
at
org.elasticsearch.indices.InternalIndicesService.indexServiceSafe(InternalIndicesService.java:243)
at
org.elasticsearch.action.mlt.TransportMoreLikeThisAction$1.onResponse(TransportMoreLikeThisAction.java:114)
at
org.elasticsearch.action.mlt.TransportMoreLikeThisAction$1.onResponse(TransportMoreLikeThisAction.java:105)
at
org.elasticsearch.action.support.TransportAction$ThreadedActionListener$1.run(TransportAction.java:86)
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:662)

Running ES 0.19.8 via the TransportClient. The index does not have shards
on every node of the cluster due to the distribution of shards across the
nodes. Shouldn't be an issue, just an FYI.

Cheers,

Ivan

--


(Ivan Brusic) #4

Thanks. I searched the mailing list (and found another with the same
issue), but not the actual issues.

I suspected that not having the index have shards on every node might
be a problem, which is why I mentioned it. I found other
inconsistencies and created a full replication, but luckily you
responded first.

Cheers,

Ivan

On Wed, Sep 26, 2012 at 5:54 PM, Igor Motov imotov@gmail.com wrote:

It looks like https://github.com/elasticsearch/elasticsearch/issues/2197
only instead of executing request on the node client, it fails when request
is getting executed on the node where your index doesn't have any shards.

On Wednesday, September 26, 2012 4:48:45 PM UTC-4, Ivan Brusic wrote:

Quick correction: the failed MoreLike request does not return a valid
response. My error handling code (inherited!) for exceptions was faulty.

On Wed, Sep 26, 2012 at 1:21 PM, Ivan Brusic iv...@brusic.com wrote:

I have been getting occasional IndexMissingExceptions, but only when
using MoreLike. The request uses an alias and the exception points to the
correct index.

Not only do searches work fine, but the MoreLike request that failed
actually returns a proper response. Perhaps one node is incorrect? Hard to
debug due to multiple threads. Here is the exception:

org.elasticsearch.indices.IndexMissingException:
[products-20120919-114007] missing
at
org.elasticsearch.indices.InternalIndicesService.indexServiceSafe(InternalIndicesService.java:243)
at
org.elasticsearch.action.mlt.TransportMoreLikeThisAction$1.onResponse(TransportMoreLikeThisAction.java:114)
at
org.elasticsearch.action.mlt.TransportMoreLikeThisAction$1.onResponse(TransportMoreLikeThisAction.java:105)
at
org.elasticsearch.action.support.TransportAction$ThreadedActionListener$1.run(TransportAction.java:86)
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:662)

Running ES 0.19.8 via the TransportClient. The index does not have shards
on every node of the cluster due to the distribution of shards across the
nodes. Shouldn't be an issue, just an FYI.

Cheers,

Ivan

--

--


(system) #5