New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IndexMissingException when calling _mlt on client node #2197
Labels
Comments
I was able to reproduce this issue as well. The issue is that the mlt request should be executed on the client node, but it should be redirected to data node that actually has the index available locally. |
Fixed by @martijnvg. |
Thanks for the quick turnaround! |
martijnvg
added a commit
to martijnvg/elasticsearch
that referenced
this issue
Aug 26, 2012
…This issue occurred if the mlt request was executed on a node that didn't have the metadata of index available locally.
martijnvg
added a commit
to martijnvg/elasticsearch
that referenced
this issue
Aug 27, 2012
mute
pushed a commit
to mute/elasticsearch
that referenced
this issue
Jul 29, 2015
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I think I've found a bug with ElasticSearch with _mlt and node clients.
We're running 0.19.8.
We have two data nodes and each app server has its own ES instance running in node client mode. Searches and normal document GETs work fine, however when running _mlt on a client node, I get an IndexMissingException. The exact same query works fine on the data node. I suspect _mlt is only checking the local _mlt
To sum it up:
On data node:
$ curl http://localhost:9200/foo/bar/1 # Works
$ curl http://localhost:9200/foo/bar/1/_mlt # Works
On client node:
$ curl http://localhost:9200/foo/bar/1 # Works
$ curl http://localhost:9200/foo/bar/1/_mlt # Fails with IndexMissingException
Full gist showing curl verbose output at https://gist.github.com/3431254
Originally raised on group at https://groups.google.com/forum/#!starred/elasticsearch/iFGSXu1e77Q
The text was updated successfully, but these errors were encountered: