I keep getting an error like this: "Courier Fetch: 5 of 270 shards failed."
in Kibana 4.0.1.
After some Googling, I think it has something to do with @timestamp not
existing for some of my data. But I'm not sure, because https://groups.google.com/d/topic/elasticsearch/L6AG3dZOGJ8/discussion was
solved by not searching the kibana indexes. I'm only searching my logstash
indexes. And I'm still getting that error.
In kibana 4 I went to Settings->Indices and made sure I only have
logstash-* listed under Index Patterns.
I did recently update the template to what was in the logstash git HEAD.
See http://pastebin.com/w7PmHxXS for my /var/log/elasticsearch/index.log
output. As well as the template I'm using. It's at the bottom of the paste.
On Tue, Mar 17, 2015 at 11:19 PM, David Reagan jerrac@gmail.com wrote:
I keep getting an error like this: "Courier Fetch: 5 of 270 shards
failed." in Kibana 4.0.1.
After some Googling, I think it has something to do with @timestamp not
existing for some of my data. But I'm not sure, because https://groups.google.com/d/topic/elasticsearch/L6AG3dZOGJ8/discussion
was solved by not searching the kibana indexes. I'm only searching my
logstash indexes. And I'm still getting that error.
In kibana 4 I went to Settings->Indices and made sure I only have
logstash-* listed under Index Patterns.
I did recently update the template to what was in the logstash git HEAD.
See http://pastebin.com/w7PmHxXS for my /var/log/elasticsearch/index.log
output. As well as the template I'm using. It's at the bottom of the paste.
@timestamp has always been applied automatically. Only time I've ever
touched it is when I've adjusted the date to what the log message holds,
rather than when the log message is processed by logstash.
So, I have no idea where it comes from, or how I could have turned it off
on something.
Is that in the template?
--David Reagan
On Tue, Mar 17, 2015 at 2:24 PM, Itamar Syn-Hershko itamar@code972.com
wrote:
Like the error suggests, "No mapping found for [@timestamp] in order to
sort on"
Kibana expects a @timestamp field - make sure to push that in your source
On Tue, Mar 17, 2015 at 11:19 PM, David Reagan jerrac@gmail.com wrote:
I keep getting an error like this: "Courier Fetch: 5 of 270 shards
failed." in Kibana 4.0.1.
After some Googling, I think it has something to do with @timestamp not
existing for some of my data. But I'm not sure, because https://groups.google.com/d/topic/elasticsearch/L6AG3dZOGJ8/discussion
was solved by not searching the kibana indexes. I'm only searching my
logstash indexes. And I'm still getting that error.
In kibana 4 I went to Settings->Indices and made sure I only have
logstash-* listed under Index Patterns.
I did recently update the template to what was in the logstash git HEAD.
See http://pastebin.com/w7PmHxXS for my /var/log/elasticsearch/index.log
output. As well as the template I'm using. It's at the bottom of the paste.
On Wed, Mar 18, 2015 at 12:51 AM, David Reagan jerrac@gmail.com wrote:
@timestamp has always been applied automatically. Only time I've ever
touched it is when I've adjusted the date to what the log message holds,
rather than when the log message is processed by logstash.
So, I have no idea where it comes from, or how I could have turned it off
on something.
Is that in the template?
--David Reagan
On Tue, Mar 17, 2015 at 2:24 PM, Itamar Syn-Hershko itamar@code972.com
wrote:
Like the error suggests, "No mapping found for [@timestamp] in order to
sort on"
Kibana expects a @timestamp field - make sure to push that in your source
On Tue, Mar 17, 2015 at 11:19 PM, David Reagan jerrac@gmail.com wrote:
I keep getting an error like this: "Courier Fetch: 5 of 270 shards
failed." in Kibana 4.0.1.
After some Googling, I think it has something to do with @timestamp not
existing for some of my data. But I'm not sure, because https://groups.google.com/d/topic/elasticsearch/L6AG3dZOGJ8/discussion
was solved by not searching the kibana indexes. I'm only searching my
logstash indexes. And I'm still getting that error.
In kibana 4 I went to Settings->Indices and made sure I only have
logstash-* listed under Index Patterns.
I did recently update the template to what was in the logstash git HEAD.
See http://pastebin.com/w7PmHxXS for my
/var/log/elasticsearch/index.log output. As well as the template I'm using.
It's at the bottom of the paste.
On Wed, Mar 18, 2015 at 12:51 AM, David Reagan jerrac@gmail.com wrote:
@timestamp has always been applied automatically. Only time I've ever
touched it is when I've adjusted the date to what the log message holds,
rather than when the log message is processed by logstash.
So, I have no idea where it comes from, or how I could have turned it off
on something.
Is that in the template?
--David Reagan
On Tue, Mar 17, 2015 at 2:24 PM, Itamar Syn-Hershko itamar@code972.com
wrote:
Like the error suggests, "No mapping found for [@timestamp] in order to
sort on"
Kibana expects a @timestamp field - make sure to push that in your source
On Tue, Mar 17, 2015 at 11:19 PM, David Reagan jerrac@gmail.com wrote:
I keep getting an error like this: "Courier Fetch: 5 of 270 shards
failed." in Kibana 4.0.1.
After some Googling, I think it has something to do with @timestamp not
existing for some of my data. But I'm not sure, because https://groups.google.com/d/topic/elasticsearch/L6AG3dZOGJ8/discussion
was solved by not searching the kibana indexes. I'm only searching my
logstash indexes. And I'm still getting that error.
In kibana 4 I went to Settings->Indices and made sure I only have
logstash-* listed under Index Patterns.
I did recently update the template to what was in the logstash git HEAD.
See http://pastebin.com/w7PmHxXS for my
/var/log/elasticsearch/index.log output. As well as the template I'm using.
It's at the bottom of the paste.
This is probably due to Kibana trying to load an empty index and therefor
missing 5 shards (ES creates 5 shards for an index by default). I stumbled
upon the same issue as Logstash created empty indices in Elasticsearch
under certain circumstances.
On Wed, Mar 18, 2015 at 12:51 AM, David Reagan <jer...@gmail.com
<javascript:>> wrote:
@timestamp has always been applied automatically. Only time I've ever
touched it is when I've adjusted the date to what the log message holds,
rather than when the log message is processed by logstash.
So, I have no idea where it comes from, or how I could have turned it
off on something.
Is that in the template?
--David Reagan
On Tue, Mar 17, 2015 at 2:24 PM, Itamar Syn-Hershko <ita...@code972.com
<javascript:>> wrote:
Like the error suggests, "No mapping found for [@timestamp] in order
to sort on"
Kibana expects a @timestamp field - make sure to push that in your
source
On Tue, Mar 17, 2015 at 11:19 PM, David Reagan <jer...@gmail.com
<javascript:>> wrote:
I keep getting an error like this: "Courier Fetch: 5 of 270 shards
failed." in Kibana 4.0.1.
After some Googling, I think it has something to do with @timestamp
not existing for some of my data. But I'm not sure, because https://groups.google.com/d/topic/elasticsearch/L6AG3dZOGJ8/discussion
was solved by not searching the kibana indexes. I'm only searching my
logstash indexes. And I'm still getting that error.
In kibana 4 I went to Settings->Indices and made sure I only have
logstash-* listed under Index Patterns.
I did recently update the template to what was in the logstash git
HEAD.
See http://pastebin.com/w7PmHxXS for my
/var/log/elasticsearch/index.log output. As well as the template I'm using.
It's at the bottom of the paste.
This is probably due to Kibana trying to load an empty index and therefor
missing 5 shards (ES creates 5 shards for an index by default). I stumbled
upon the same issue as Logstash created empty indices in Elasticsearch
under certain circumstances.
That was exactly it! I found my empty index, deleted it, and the error
message went away. Thanks!
This is probably due to Kibana trying to load an empty index and therefor
missing 5 shards (ES creates 5 shards for an index by default). I stumbled
upon the same issue as Logstash created empty indices in Elasticsearch
under certain circumstances.
On Wed, Mar 18, 2015 at 12:51 AM, David Reagan jer...@gmail.com wrote:
@timestamp has always been applied automatically. Only time I've ever
touched it is when I've adjusted the date to what the log message holds,
rather than when the log message is processed by logstash.
So, I have no idea where it comes from, or how I could have turned it
off on something.
On Tue, Mar 17, 2015 at 11:19 PM, David Reagan jer...@gmail.com
wrote:
I keep getting an error like this: "Courier Fetch: 5 of 270 shards
failed." in Kibana 4.0.1.
After some Googling, I think it has something to do with @timestamp
not existing for some of my data. But I'm not sure, because https://groups.google.com/d/topic/elasticsearch/
L6AG3dZOGJ8/discussion was solved by not searching the kibana
indexes. I'm only searching my logstash indexes. And I'm still getting that
error.
In kibana 4 I went to Settings->Indices and made sure I only have
logstash-* listed under Index Patterns.
I did recently update the template to what was in the logstash git
HEAD.
See http://pastebin.com/w7PmHxXS for my /var/log/elasticsearch/index.log
output. As well as the template I'm using. It's at the bottom of the paste.
I did check with curl -XGET 'http://localhost:9200/_cat/
shards?pretty=true' to see if any shards had issues. They all had
"STARTED" as their status.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.