way of addressing
these indices without the mapping in question? I'd really hate to have to
go through and hand update them all to have the mapping :(
On Friday, March 6, 2015 at 8:27:48 AM UTC-8, Alex Schokking wrote:
Hi there,
We're just getting started with ELK and are using
Probably super evident but the output above was actually from
_cat/allocation?v not /recovery, sorry about that.
On Wednesday, April 29, 2015 at 5:19:08 PM UTC-7, Alex Schokking wrote:
Hi guys, I would really appreciate some help understanding what's going
down with shard allocation
Hi guys, I would really appreciate some help understanding what's going
down with shard allocation in this case:
Elasticsearch version: 1.4.4
We had 3 nodes with 1 shard and 1 replica per index (so net 2 copies of
everything). 1 node went down and the cluster went red. It started to
Were you ever able to figure out a solution to this? I'm in a similar boat.
On Thursday, September 11, 2014 at 2:14:29 AM UTC-7, Kushal Zamkade wrote:
Hello,
I have created a location filed by using below code
if [latitude] and [longitude] {
mutate {
rename = [ latitude,
Woah crazy, never would've thought of that, thanks a lot for following up!
On Wed, Apr 1, 2015 at 12:31 PM, Pascal VINCENT pasvinc...@gmail.com
wrote:
I finally come up with :
if [latitude] and [longitude] {
mutate {
add_field = [ [location], %{longitude} ]
add_field = [
Hi there,
We're just getting started with ELK and are using:
Elasticsearch 1.4.4
Kibana 4.0
on
Ubuntu 14.04
We needed to create a scripted field to calculate the ratio between two
numeric fields. These fields are not on all events and only started
appearing at all a day ago (so older indexes
