Hi all,
This is an old post, but had the same issue today.
It is because kibana searches in all indices by default, and kibana-int
(where the kibana interface data is stored)
has no timestamp field in it.
The error is gone after putting the correct index filter in the dashboard
settings.
A.
Hi,
I am facing the same issue when I include "Histogram" in Kibana and set
@timestamp in the time field.. Here is the debug message I am getting
org.elasticsearch.search.SearchParseException: [kibana-int][3]:
from[-1],size[-1]: Parse Failure [Failed to parse source
[{"facets":{"0":{"date_histo
Hi,
I am facing the same issue when I include "Histogram" in Kibana and set
@timestamp in the time field.. Here is the debug message I am getting
org.elasticsearch.search.SearchParseException: [kibana-int][3]:
from[-1],size[-1]: Parse Failure [Failed to parse source
[{"facets":{"0":{"date_histo
Hi,
I am a little late but maybe it brings some closure...I believe you
ran into this: https://github.com/elasticsearch/elasticsearch/pull/5623
The symptoms for this bug are exactly what you describe.
Britta
On Mon, Mar 17, 2014 at 10:07 PM, Mac Jouz wrote:
>
> Finally I fixed dynamically the b
Finally I fixed dynamically the broken index but taking account your answer
I'm going to add files to avoid future problems
Thanks Karol
Regards
José
Le lundi 17 mars 2014 19:25:31 UTC+1, bizzorama a écrit :
>
> Hi, we tried both ways but:
> First worked but was temporary and worked as
Hi, we tried both ways but:
First worked but was temporary and worked as index quickfix (after
powerdown it was lost again), of course we used the rest interfaces to fix
mappings that were already broken (we could not pump all data again so we
had to fix it somehow).
We applied the mapping file as
Would either of you be able to write up the steps to reproduce this and to
open an issue about it?
thanks
On 17 March 2014 17:58, Mac Jouz wrote:
>
> Same symptom for me, neither OOM, nor full disk space, only an ES
> restart...
>
> Le lundi 17 mars 2014 14:00:11 UTC+1, bizzorama a écrit :
>>
Same symptom for me, neither OOM, nor full disk space, only an ES
restart...
Le lundi 17 mars 2014 14:00:11 UTC+1, bizzorama a écrit :
>
> No, when things are running everything is ok, indexes break during
> restart/powerdown
> 17-03-2014 13:11, "Clinton Gormley" >
> napisał(a):
>
>> Are you
Hi,
Thanks Karol, changing ES version does not change the problem indeed.
2 complementary questions if I may:
- You wrote that you copied the mapping file on ES location, did you try a
way to do so dynamically with a REST call ?
- Otherwise did you apply the modification for the specific "corru
No, when things are running everything is ok, indexes break during
restart/powerdown
17-03-2014 13:11, "Clinton Gormley" napisał(a):
> Are you sure you didn't run out of disk space or file handles at some
> stage, or have an OOM exception?
>
>
> On 16 March 2014 16:37, bizzorama wrote:
>
>> Hi,
Are you sure you didn't run out of disk space or file handles at some
stage, or have an OOM exception?
On 16 March 2014 16:37, bizzorama wrote:
> Hi,
>
> it turned out that it was not a problem of ES version (we tested on both
> 0.90.10 and 0.90.9) but just a ES bug ...
> after restarting pc or
Hi,
it turned out that it was not a problem of ES version (we tested on both
0.90.10 and 0.90.9) but just a ES bug ...
after restarting pc or even just the service indices got broken ... we
found out that this was the case of missing mappings.
We observed that broken indices had their mappings c
Hi Bizzorama,
I had a similar problem with the same configuration than you gave.
ES ran since the 11th of February and was fed every day at 6:00 AM by 2 LS.
Everything worked well (kibana reports were correct and no data loss) until
I restarted yesterday ES :-(
Among 30 index (1 per day), 4 were
Sorry for the delay.
Looks like you were right, after downgrading ES to 0.90.9 i couldn't
reproduce the issue in such manner.
Unfortunately, I found some other problems, and one looks like a blocker
After whole ES cluster powerdown, ES just started replaying 'no mapping for
... ' for ea
Your error logs seem to indicate some kind of version mismatch. Is it
possible for you to test LS 1.3.2 against ES 0.90.9 and take a sample of
raw logs from those 3 days and test them through to see if those 3 days
work in Kibana? The reason I ask is because LS 1.3.2 (specifically the
elasticse
> Really, no clue?
>
--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit
htt
Hi,
I've noticed a very disturbing ElasticSearch behaviour ...
my environment is:
1 logstash (1.3.2) (+ redis to store some data) + 1 elasticsearch (0.90.10)
+ kibana
which process about 7 000 000 records per day,
everything worked fine on our test environment, untill we run some tests
for a l
17 matches
Mail list logo
