How to query elasticsearch: I keep getting index_not_found_exception
1
Elasticsearch 6.4.3
Issue: a /_search command returns:
index_not_found_exception
Specifically:
$ curl -X GET "192.168.2.2:9200/MyNew_Index/_search" -H 'Content-Type: application/json'
{
"from": 0,
"size": 40,
"sort":
...
Returns:
{
"error": {
"root_cause": [{
"type": "index_not_found_exception",
"reason": "no such index",
"resource.type": "index_or_alias",
"resource.id": "MyNew_Index",
"index_uuid": "_na_",
"index": "MyNew_Index"
}],
...
But when I look to see what indexes are present, I see it:
$ curl -X GET "192.168.2.2:9200/_cat/indices?v" -H 'Content-Type: application/json'
health status index uuid pri rep docs.count docs.deleted store.size pri.store.size
green open MyNew_Index 71X8IOLzQaKqj7aaK5CRbA 50 1 900288822
3322978 1tb 533.4gb
What am I missing?
elasticsearch
asked Nov 14 '18 at 2:54
JonesomeJonesome
2,96763575
add a comment |
1
Elasticsearch 6.4.3
Issue: a /_search command returns:
index_not_found_exception
Specifically:
$ curl -X GET "192.168.2.2:9200/MyNew_Index/_search" -H 'Content-Type: application/json'
{
"from": 0,
"size": 40,
"sort":
...
Returns:
{
"error": {
"root_cause": [{
"type": "index_not_found_exception",
"reason": "no such index",
"resource.type": "index_or_alias",
"resource.id": "MyNew_Index",
"index_uuid": "_na_",
"index": "MyNew_Index"
}],
...
But when I look to see what indexes are present, I see it:
$ curl -X GET "192.168.2.2:9200/_cat/indices?v" -H 'Content-Type: application/json'
health status index uuid pri rep docs.count docs.deleted store.size pri.store.size
green open MyNew_Index 71X8IOLzQaKqj7aaK5CRbA 50 1 900288822
3322978 1tb 533.4gb
What am I missing?
elasticsearch
asked Nov 14 '18 at 2:54
JonesomeJonesome
2,96763575
Weird. Try deleting the index and recreating. Maybe also try something lowercase? Can’t see anything different than what I’ve done 1000x
– John H
Nov 14 '18 at 2:57
@JohnH Drop the index... not possible, it is a 500GB index that takes days to build (and it works, just not via curl)
– Jonesome
Nov 14 '18 at 16:05
Did you encounter any memory issues recently with the cluster or any crashes? I faced the same issue once because of storage getting filled up. I have to restart the cluster to query the index. Don't know how, process dumps filled up my complete storage and faced this issue.
– BarathVutukuri
Nov 14 '18 at 17:36
@BarathVutukuri No issues of any kind. The cluster is running cleanly.
– Jonesome
Nov 14 '18 at 22:16
add a comment |
1
1
1
Elasticsearch 6.4.3
Issue: a /_search command returns:
index_not_found_exception
Specifically:
$ curl -X GET "192.168.2.2:9200/MyNew_Index/_search" -H 'Content-Type: application/json'
{
"from": 0,
"size": 40,
"sort":
...
Returns:
{
"error": {
"root_cause": [{
"type": "index_not_found_exception",
"reason": "no such index",
"resource.type": "index_or_alias",
"resource.id": "MyNew_Index",
"index_uuid": "_na_",
"index": "MyNew_Index"
}],
...
But when I look to see what indexes are present, I see it:
$ curl -X GET "192.168.2.2:9200/_cat/indices?v" -H 'Content-Type: application/json'
health status index uuid pri rep docs.count docs.deleted store.size pri.store.size
green open MyNew_Index 71X8IOLzQaKqj7aaK5CRbA 50 1 900288822
3322978 1tb 533.4gb
What am I missing?
elasticsearch
asked Nov 14 '18 at 2:54
JonesomeJonesome
2,96763575
Elasticsearch 6.4.3
Issue: a /_search command returns:
index_not_found_exception
Specifically:
$ curl -X GET "192.168.2.2:9200/MyNew_Index/_search" -H 'Content-Type: application/json'
{
"from": 0,
"size": 40,
"sort":
...
Returns:
{
"error": {
"root_cause": [{
"type": "index_not_found_exception",
"reason": "no such index",
"resource.type": "index_or_alias",
"resource.id": "MyNew_Index",
"index_uuid": "_na_",
"index": "MyNew_Index"
}],
...
But when I look to see what indexes are present, I see it:
$ curl -X GET "192.168.2.2:9200/_cat/indices?v" -H 'Content-Type: application/json'
health status index uuid pri rep docs.count docs.deleted store.size pri.store.size
green open MyNew_Index 71X8IOLzQaKqj7aaK5CRbA 50 1 900288822
3322978 1tb 533.4gb
What am I missing?
elasticsearch
elasticsearch
asked Nov 14 '18 at 2:54
JonesomeJonesome
2,96763575
asked Nov 14 '18 at 2:54
JonesomeJonesome
2,96763575
asked Nov 14 '18 at 2:54
JonesomeJonesome
2,96763575
asked Nov 14 '18 at 2:54
JonesomeJonesome
2,96763575
asked Nov 14 '18 at 2:54
JonesomeJonesome
2,96763575
2,96763575
Weird. Try deleting the index and recreating. Maybe also try something lowercase? Can’t see anything different than what I’ve done 1000x
– John H
Nov 14 '18 at 2:57
@JohnH Drop the index... not possible, it is a 500GB index that takes days to build (and it works, just not via curl)
– Jonesome
Nov 14 '18 at 16:05
Did you encounter any memory issues recently with the cluster or any crashes? I faced the same issue once because of storage getting filled up. I have to restart the cluster to query the index. Don't know how, process dumps filled up my complete storage and faced this issue.
– BarathVutukuri
Nov 14 '18 at 17:36
@BarathVutukuri No issues of any kind. The cluster is running cleanly.
– Jonesome
Nov 14 '18 at 22:16
add a comment |
Weird. Try deleting the index and recreating. Maybe also try something lowercase? Can’t see anything different than what I’ve done 1000x
– John H
Nov 14 '18 at 2:57
@JohnH Drop the index... not possible, it is a 500GB index that takes days to build (and it works, just not via curl)
– Jonesome
Nov 14 '18 at 16:05
Did you encounter any memory issues recently with the cluster or any crashes? I faced the same issue once because of storage getting filled up. I have to restart the cluster to query the index. Don't know how, process dumps filled up my complete storage and faced this issue.
– BarathVutukuri
Nov 14 '18 at 17:36
@BarathVutukuri No issues of any kind. The cluster is running cleanly.
– Jonesome
Nov 14 '18 at 22:16
Weird. Try deleting the index and recreating. Maybe also try something lowercase? Can’t see anything different than what I’ve done 1000x
– John H
Nov 14 '18 at 2:57
Weird. Try deleting the index and recreating. Maybe also try something lowercase? Can’t see anything different than what I’ve done 1000x
– John H
Nov 14 '18 at 2:57
@JohnH Drop the index... not possible, it is a 500GB index that takes days to build (and it works, just not via curl)
– Jonesome
Nov 14 '18 at 16:05
@JohnH Drop the index... not possible, it is a 500GB index that takes days to build (and it works, just not via curl)
– Jonesome
Nov 14 '18 at 16:05
Did you encounter any memory issues recently with the cluster or any crashes? I faced the same issue once because of storage getting filled up. I have to restart the cluster to query the index. Don't know how, process dumps filled up my complete storage and faced this issue.
– BarathVutukuri
Nov 14 '18 at 17:36
Did you encounter any memory issues recently with the cluster or any crashes? I faced the same issue once because of storage getting filled up. I have to restart the cluster to query the index. Don't know how, process dumps filled up my complete storage and faced this issue.
– BarathVutukuri
Nov 14 '18 at 17:36
@BarathVutukuri No issues of any kind. The cluster is running cleanly.
– Jonesome
Nov 14 '18 at 22:16
@BarathVutukuri No issues of any kind. The cluster is running cleanly.
– Jonesome
Nov 14 '18 at 22:16
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53292526%2fhow-to-query-elasticsearch-i-keep-getting-index-not-found-exception%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
draft saved
draft discarded
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53292526%2fhow-to-query-elasticsearch-i-keep-getting-index-not-found-exception%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Weird. Try deleting the index and recreating. Maybe also try something lowercase? Can’t see anything different than what I’ve done 1000x
– John H
Nov 14 '18 at 2:57
@JohnH Drop the index... not possible, it is a 500GB index that takes days to build (and it works, just not via curl)
– Jonesome
Nov 14 '18 at 16:05
Did you encounter any memory issues recently with the cluster or any crashes? I faced the same issue once because of storage getting filled up. I have to restart the cluster to query the index. Don't know how, process dumps filled up my complete storage and faced this issue.
– BarathVutukuri
Nov 14 '18 at 17:36
@BarathVutukuri No issues of any kind. The cluster is running cleanly.
– Jonesome
Nov 14 '18 at 22:16