elasticsearch-river-mongodb

[priyanka nathani]

Hello
i have a question for the syncronization .
My ES collection has 5 colums whereas mongo collection has 3 .
but during the sync the addtional 2 colums in ES is gone.
Any way to neglect the addtional column during sync ?
the other way round is poosible in mongo as filter in river.

-- 
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 
https://groups.google.com/d/msgid/elasticsearch/2e040413-fe33-4b48-bf89-0e0ad3a680a4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Is enabling docValues and disabling index possible

[vineeth mohan]

Hi ,

I have a situation where a field is only used for aggregation , its never
used for searching.
In such cases , it doesn't make sense for this field to go to lucene
reverse index.
Rather if it can be only maintained in fieldData or docValues alone . that
would save me some good amount of space and might optimize performance.

Is this possible ?

Thanks
 Vineeth

-- 
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 
https://groups.google.com/d/msgid/elasticsearch/CAGdPd5kxgex5BwLVxz6N8gwAGCmUwSiBRPuXAu7PbqCGT%2BH0kA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Debian packages for Kibana 4 beta 2?

[Kevin Burton]

Has anyone created debian packages for Kibana 4 beta2 ?

I started working on some but if anyone hasn't created one I was just going 
to throw one together.

-- 
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 
https://groups.google.com/d/msgid/elasticsearch/100c202f-ffcf-43bc-87f0-03824faf3499%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Exporting search results in Kibana v.4

[David Kleiner]

Went through closed Kibana.4 closed tickets, found it fixed with commit to 
master. Will rebuild and redeploy. Hopefully will work then. 

On Monday, December 1, 2014 4:04:45 PM UTC-8, David Kleiner wrote:
>
> Greetings Kibana.4 fans,
>
> There is an export button in Kibana 4 (see screenshot) but it doesn't do 
> anything meaningful.  Is it just a mock-up for future functionality?  Cu's 
> are missing the ability to save searches to excel... 
>
> Thanks,
>
> David
>
>

-- 
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 
https://groups.google.com/d/msgid/elasticsearch/06b2fd43-e5ec-48d0-8897-00f263294681%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Exporting search results in Kibana v.4

[David Kleiner]

Here's the javascript error I get when I click on Export button (company 
name withheld):

"Error: Argument 1 of Blob.constructor can't be converted to a sequence.
.controller/self.exportAsCsv@http://kibana.company.com/index.js?_b=3998:98251:18
Parser.prototype.functionCall/<@http://kibana.company.com/index.js?_b=3998:20038:15
ngEventHandler/http://kibana.company.com/index.js?_b=3998:28327:17
$RootScopeProvider/this.$gethttp://kibana.company.com/index.js?_b=3998:21893:16
$RootScopeProvider/this.$gethttp://kibana.company.com/index.js?_b=3998:21991:18
ngEventHandler/<@http://kibana.company.com/index.js?_b=3998:28332:17
jQuery.event.dispatch@http://kibana.company.com/index.js?_b=3998:4408:15
jQuery.event.add/elemData.handle@http://kibana.company.com/index.js?_b=3998:4095:6
"

Not sure what's wrong :(

On Monday, December 1, 2014 4:04:45 PM UTC-8, David Kleiner wrote:
>
> Greetings Kibana.4 fans,
>
> There is an export button in Kibana 4 (see screenshot) but it doesn't do 
> anything meaningful.  Is it just a mock-up for future functionality?  Cu's 
> are missing the ability to save searches to excel... 
>
> Thanks,
>
> David
>
>

-- 
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 
https://groups.google.com/d/msgid/elasticsearch/f83bf2b1-654e-4dc2-947f-f2eabe3b776c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Can one parent type have multiple children types in one index?

[Min Zhou]

Hi all, 

>From the source code, seems that one parent type  can only have one child 
type. Can one parent type have multiple children types in one index?

Min

-- 
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 
https://groups.google.com/d/msgid/elasticsearch/449e9dcb-70e8-4176-aae9-26b72353c7d0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Exporting search results in Kibana v.4

[David Kleiner]

Greetings Kibana.4 fans,

There is an export button in Kibana 4 (see screenshot) but it doesn't do 
anything meaningful.  Is it just a mock-up for future functionality?  Cu's 
are missing the ability to save searches to excel... 

Thanks,

David

-- 
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 
https://groups.google.com/d/msgid/elasticsearch/4b137949-9a81-4340-bf2d-5f7c797db874%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Reliability of ElasticSearch

[Nikolas Everett]

99.9% uptime allows almost nine hours a year.  You could totally manage
that if you have someone on call 24/7.  Elasticsearch itself is reasonably
stable especially if you don't expose very complex queries to everyone.  We
do and we only have one person on call (me) and we've probably just made
that 99.9% uptime this year.  I imagine next year it'll be better because
we'll have a whole year of experience with it in production.

Nik

On Mon, Dec 1, 2014 at 5:54 PM, Mark Walkom  wrote:

> Have an uneven number of master eligible nodes.
> Set discovery.zen.minimum_master_nodes equal to
> ​ number masters​/2+1.
> Ensure you have monitoring setup, both on ES and the OS.
>
> There's lots more though, but that's a start.
>
> On 2 December 2014 at 05:15, Xinli Shang  wrote:
>
>> I am new to ElasticSearch and asked to design ElasticSearch for log
>> search. One of the big requirement is availability > 99.9%. If you have
>> designed elastic search, could you please share your top 3 lessons that you
>> learn to make elastic search highly available?
>>
>>
>>
>>
>>  --
>> 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
>> https://groups.google.com/d/msgid/elasticsearch/CAHsnNRh-qPc1Q1j%3DCxY6zh8e7UQ4j%2B8Oj5E4mir5TPC_1Ly0%3Dw%40mail.gmail.com
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>  --
> 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
> https://groups.google.com/d/msgid/elasticsearch/CAF3ZnZk201qXxXbp-oJTp%2BSPrK0JTVCPbVQDKnEBFk9ny%3D42DA%40mail.gmail.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 
https://groups.google.com/d/msgid/elasticsearch/CAPmjWd16UPemVx9tXKDC0m-Wu8Y3o_RGN9YPpX16frYYx9BLzw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Periodic high load after upgrading from 0.90 to 1.3.4

[Mark Walkom]

It'd be worth starting at hot threads;
http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/cluster-nodes-hot-threads.html#cluster-nodes-hot-threads

On 2 December 2014 at 08:23, Michael McGuinness 
wrote:

> I'm running a set of very simple elasticsearch instances as part of a
> graylog2 deployment. Each set has a single elasticsearch node (its own
> cluster). I recently upgraded these sets to 1.34 as part of an upgrade to
> the graylog2 server, and I immediately noticed some periodic high loads on
> the machines involved; here's a cpu and load graph from one of the upgrades:
>
>
> 
> The upgrade occurred at ~12pm (you can see the spike on the ProcessorLoad
>  graph). There are now periods of fairly high load, it goes up to ~5 on
> this graph, though when watching the machine through htop or the like, 5
> minute load tops out at about 8 at the start of any given spike. I've
> determined that the machine is not bound by cpu, memory, or I/O during
> these events, and I've also confirmed that there is no GC thrashing.
>
> I don't see anything in the logs of either elasticsearch or graylog2 that
> line up with the spikes.
>
> When the spike is going on, all 5 threads from the management pool tend to
> be active (learned this by comparing the running pids from htop to a thread
> dump from jstack). I've found it difficult to find much more concrete
> information since nothing seems to actually be 'stuck', the best I was able
> to gleam was the following result from /_cat/thread_pool during one of the
> load spikes:
>
> host  id  mas maa maq
> (graylog2)   T9hD  1   1   0
> (es-primary) YG9x  5   5 100
>
> If I repeatedly query the thread_pool during a spike I will occasionally
> get these ~100 queued management threads, though I wasn't able to capture
> what these threads are trying to do.
>
> Has anyone seen this behavior before, or recognize it? I'd be happy to
> provide more information - up until now I've been using elasticsearch
> mostly as a blackbox component of graylog, so I'm not very familiar with
> debugging it.
>
> --
> 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
> https://groups.google.com/d/msgid/elasticsearch/017f0fc5-9619-4cce-b1a4-02db44ef4b6b%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 
https://groups.google.com/d/msgid/elasticsearch/CAF3ZnZnSrXuv01-5ChoiM1mNci442-xcKoj6rjeZS5pSGVOyOQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Reliability of ElasticSearch

[Mark Walkom]

Have an uneven number of master eligible nodes.
Set discovery.zen.minimum_master_nodes equal to
​ number masters​/2+1.
Ensure you have monitoring setup, both on ES and the OS.

There's lots more though, but that's a start.

On 2 December 2014 at 05:15, Xinli Shang  wrote:

> I am new to ElasticSearch and asked to design ElasticSearch for log
> search. One of the big requirement is availability > 99.9%. If you have
> designed elastic search, could you please share your top 3 lessons that you
> learn to make elastic search highly available?
>
>
>
>
>  --
> 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
> https://groups.google.com/d/msgid/elasticsearch/CAHsnNRh-qPc1Q1j%3DCxY6zh8e7UQ4j%2B8Oj5E4mir5TPC_1Ly0%3Dw%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 
https://groups.google.com/d/msgid/elasticsearch/CAF3ZnZk201qXxXbp-oJTp%2BSPrK0JTVCPbVQDKnEBFk9ny%3D42DA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: ES java api: how to handle connectivity problems?

[msbreuer]

I am using the node client. Refering to 
http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/modules-discovery-zen.html
 
the timeout is limited and not for ever. What do you think how I should set 
the timeout?

Also I am confused: the server node got back but the client does not 
recover. Shouldn't it reconnect? Even if the client waits forever it should 
reconnect, shouldn't it?

Are you using the node client or the transport client?
>
> I recommend to use timeout settings. By default no timeout is set, and 
> client waits forever, in both normal and exceptional situation.
>
> With transport client, the fault detector will respond with an exception 
> when no node is connected.
>
> Jörg
>
>
> On Mon, Dec 1, 2014 at 6:48 PM, > wrote:
>
>> No, in my case the client does not continue. The one-node-cluster goes 
>> offline and comes back, but the client still hangs. The master-/data-node 
>> is 1.4.0 and the java client uses 1.3.1. 
>>
>> I tested several scenarios the get the cluster offline: killing it and 
>> and let the server run into OOM Exceptions. 
>>
>> The client may hang because I assume the cluster state got unavailable, 
>>> and minimum master condition is no longer met. If you re-add the failed 
>>> node, the cluster state will be available again, and I think the client 
>>> will continue.
>>>
>>> Jörg
>>>
>>  -- 
>> 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 elasticsearc...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/elasticsearch/0653ba92-b68e-4b7d-90bb-ae8075ea26e7%40googlegroups.com
>>  
>> 
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
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 
https://groups.google.com/d/msgid/elasticsearch/7fcad497-3380-42da-93c7-2c2a016a669d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Periodic high load after upgrading from 0.90 to 1.3.4

[Michael McGuinness]

I'm running a set of very simple elasticsearch instances as part of a 
graylog2 deployment. Each set has a single elasticsearch node (its own 
cluster). I recently upgraded these sets to 1.34 as part of an upgrade to 
the graylog2 server, and I immediately noticed some periodic high loads on 
the machines involved; here's a cpu and load graph from one of the upgrades:


The upgrade occurred at ~12pm (you can see the spike on the ProcessorLoad 
 graph). There are now periods of fairly high load, it goes up to ~5 on 
this graph, though when watching the machine through htop or the like, 5 
minute load tops out at about 8 at the start of any given spike. I've 
determined that the machine is not bound by cpu, memory, or I/O during 
these events, and I've also confirmed that there is no GC thrashing.

I don't see anything in the logs of either elasticsearch or graylog2 that 
line up with the spikes.

When the spike is going on, all 5 threads from the management pool tend to 
be active (learned this by comparing the running pids from htop to a thread 
dump from jstack). I've found it difficult to find much more concrete 
information since nothing seems to actually be 'stuck', the best I was able 
to gleam was the following result from /_cat/thread_pool during one of the 
load spikes:

host  id  mas maa maq
(graylog2)   T9hD  1   1   0
(es-primary) YG9x  5   5 100

If I repeatedly query the thread_pool during a spike I will occasionally 
get these ~100 queued management threads, though I wasn't able to capture 
what these threads are trying to do.

Has anyone seen this behavior before, or recognize it? I'd be happy to 
provide more information - up until now I've been using elasticsearch 
mostly as a blackbox component of graylog, so I'm not very familiar with 
debugging it.

-- 
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 
https://groups.google.com/d/msgid/elasticsearch/017f0fc5-9619-4cce-b1a4-02db44ef4b6b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: how to store data into index field in starts (*) like password data ?

[David Pilato]

Don't store them! 
You could use source exclude filter to remove them at index time if you really 
can't do it on a client level.

--
David ;-)
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

> Le 1 déc. 2014 à 20:57, Subbarao Kondragunta  a 
> écrit :
> 
> how to store data into index field in starts (*) like password data ?
> -- 
> 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 
> https://groups.google.com/d/msgid/elasticsearch/6198d255-3a89-4522-9626-ae2242da2da6%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
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 
https://groups.google.com/d/msgid/elasticsearch/0E9A168A-E60C-4514-B17C-8AA51BCDA9BC%40pilato.fr.
For more options, visit https://groups.google.com/d/optout.

Advices on migrating 1.3.2 to 1.4.1

[Roger de Cordova Farias]

Hello

We currently have a cluster with 50 millions of docs using ElasticSearch
version 1.3.2

We were looking for something like a persisted filter, and the filtered
aliases, added in version 1.4.0.beta1, seems perfect for it

Our infrastructure team is not happy to upgrading it in production without
doing a lot of tests before, so we have to do a lot of tests and upgrade
later

We are looking for some advices in what can go wrong with this upgrade,
what are the risks?

And also, is there a way to implement a "persistent filter" in our current
version? I mean, some of our users will have access to a part of our data,
we need something like a database view. We could send a filter in every
request, but that would be too slow with, let's say, 10 millions of ids.

-- 
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 
https://groups.google.com/d/msgid/elasticsearch/CAJp2533WXXhA4hAd4qBPWa0ZUZGBPUFQ0V4Tv_u7p2OuyCChoA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

how to store data into index field in starts (*) like password data ?

[Subbarao Kondragunta]

how to store data into index field in starts (*) like password data ?

-- 
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 
https://groups.google.com/d/msgid/elasticsearch/6198d255-3a89-4522-9626-ae2242da2da6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Node Client Protocol

[Phillip Simon]

Hi,

I am trying to use the ES node based client instead of transport and I keep 
getting this error (also, I'm coding in JAVA):


Exception in thread "Timer-0" java.lang.ExceptionInInitializerError

at com.priceline.argus.es.gds.PushGdsToES.main(PushGdsToES.java:38)

at com.priceline.argus.es.gds.GDSTimedTask.run(GDSTimedTask.java:58)

at java.util.TimerThread.mainLoop(Timer.java:555)

at java.util.TimerThread.run(Timer.java:505)

Caused by: org.elasticsearch.transport.BindTransportException: Failed to 
bind to [9300-9400]

at org.elasticsearch.transport.netty.NettyTransport.doStart(
NettyTransport.java:380)

at org.elasticsearch.common.component.AbstractLifecycleComponent.start(
AbstractLifecycleComponent.java:85)

at org.elasticsearch.transport.TransportService.doStart(
TransportService.java:92)

at org.elasticsearch.common.component.AbstractLifecycleComponent.start(
AbstractLifecycleComponent.java:85)

at org.elasticsearch.node.internal.InternalNode.start(InternalNode.java:229)

at org.elasticsearch.node.NodeBuilder.node(NodeBuilder.java:166)

at com.priceline.argus.es.gds.ArgusESClientFactory.(
ArgusESClientFactory.java:40)

... 4 more



Here is a snippet of my code:


static Settings settings = ImmutableSettings.settingsBuilder().put(
"network.host","hostName").put("cluster.name", "clusterName").build();

 private static Node node = nodeBuilder().settings(settings).client(true
).data(false).node();

 private static Client esClient = null;

public static Client getClient() {

 if (esClient == null) { esClient = node.client(); }

 return esClient;

 }


I am thinking that the only thing I'm missing is the port number when I 
create the settings but I could be wrong. When I use the transport 
protocol, everything works fine but I am also specifying the port number 
when I use that protocol. 


Thanks,

Phil

-- 
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 
https://groups.google.com/d/msgid/elasticsearch/db5de130-11a3-40ef-bd54-8e46cfd2e590%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: 'Shard Allocation' dashboard in Marvel 1.2 showing SearchParseExceptions

[Max Charas]

Hello Boaz,
Thanks for helping!

I read through your post a few times and realized that it was probably the 
master node that wasn't sending any date as you indicated. A restart of the 
node fixed the problem.

I have no idea why it wasn't shipping any data to start with, most likely 
we hadn't restarted it since we installed the plugin but I'm not completely 
sure. 

In any case its working now. 

Many thanks,
Max

Den söndagen den 30:e november 2014 kl. 23:45:15 UTC+1 skrev Boaz Leskes:
>
> Hi Teo, Max,
>
> From the query, I can see that it that cluster_state is not shipped. The 
> marvel index template adds the cluster_type with some non-default fields 
> but all fields (like @timestamp) are added when the first document is 
> shipped.
>
> Can you validate there are no documents of that type?
>
> Further a couple of clarifying questions:
> 1) Did you install the marvel agent on all cluster nodes? i.e., also 
> master nodes? The later is the ones that ship that data..
> 2) Did you upgrade from a previous version of marvel or is it a fresh 
> install?
>
> Cheers,
> Boaz
>
>
> On Wednesday, November 26, 2014 5:24:58 PM UTC+1, Teo Ruiz wrote:
>>
>> Hi guys,
>>
>> We're seeing exactly the same error. This is the error we see: 
>> org.elasticsearch.search.SearchParseException: [.marvel-2014.11.26][0]: 
>> from[-1],size[1]: Parse Failure [Failed to parse source [{"size":1,"sort"
>> :{"@timestamp":{"order":"desc"}}}]]
>>
>> Full trace here: 
>> https://gist.github.com/teoruiz/9cdb4e9cd7dc5e564346#file-es_error_log
>> Mappings here: 
>> https://gist.github.com/teoruiz/9cdb4e9cd7dc5e564346#file-marvel_index_mapping-json
>>
>> ES version on monitoring and production clusters: 1.3.4
>> Marvel version on monitoring and production clusters: 1.2.1
>>
>> I'm not sure how to proceed, since we removed and reinstalled marvel 
>> already. The problem started showing when we upgraded the production 
>> cluster from 0.90.x to 1.3.4.
>>
>> I'd appreciate some light shedding on this :)
>>
>> On Tuesday, November 25, 2014 10:29:45 AM UTC+1, Max Charas wrote:
>>>
>>> Same problem here.
>>>
>>> Log says:
>>>
>>> Parse Failure [Failed to parse source 
>>> [{"size":1,"sort":{"@timestamp":{"order":"desc"}}}]]
>>> Verified that the index(es) have the timestamp field. 
>>>
>>> Running Marvel 1.2.1 and Elasticsearch 1.3.2.
>>>
>>> Any help would be appreciated as we cant get our Marvel up and running.
>>>
>>> Den fredagen den 7:e november 2014 kl. 17:54:09 UTC+1 skrev Ryan 
>>> Hendrickson:

 I see the same error  Were you able to resolve it?

 Thanks

 On Wednesday, September 17, 2014 12:52:14 PM UTC-4, Sean Kipling wrote:
>
> I am on Marvel 1.2.1 and had the same error (see below). The time on 
> one of my nodes was off a fair bit. Fixed that and the problem went away.
>
> [2014-09-17 11:55:14,615][DEBUG][action.search.type   ] [Pip the 
> Troll] All shards failed for phase: [query_fetch]
> [2014-09-17 12:16:00,532][DEBUG][action.search.type   ] [Pip the 
> Troll] [.marvel-2014.09.17][0], node[2d8iMl4tRHSS8JFPJMN01A], [P], 
> s[STARTED]: Failed to execute 
> [org.elasticsearch.action.search.SearchRequest@769694e9]
> org.elasticsearch.search.SearchParseException: 
> [.marvel-2014.09.17][0]: from[-1],size[1]: Parse Failure [Failed to parse 
> source [{"size":1,"sort":{"@timestamp":{"order":"desc"}}}]]
> at 
> org.elasticsearch.search.SearchService.parseSource(SearchService.java:664)
> at 
> org.elasticsearch.search.SearchService.createContext(SearchService.java:515)
> at 
> org.elasticsearch.search.SearchService.createAndPutContext(SearchService.java:487)
> at 
> org.elasticsearch.search.SearchService.executeFetchPhase(SearchService.java:328)
> at 
> org.elasticsearch.search.action.SearchServiceTransportAction$11.call(SearchServiceTransportAction.java:308)
> at 
> org.elasticsearch.search.action.SearchServiceTransportAction$11.call(SearchServiceTransportAction.java:305)
> at 
> org.elasticsearch.search.action.SearchServiceTransportAction$23.run(SearchServiceTransportAction.java:517)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: org.elasticsearch.search.SearchParseException: 
> [.marvel-2014.09.17][0]: from[-1],size[1]: Parse Failure [No mapping 
> found 
> for [@timestamp] in order to sort on]
> at 
> org.elasticsearch.search.sort.SortParseElement.addSortField(SortParseElement.java:198)
> at 
> org.elasticsearch.search.sort.SortParseElement.addCompoundSortField(SortParseElement.java:172)
> at 
> org.elasticsearch.search.sort.SortParseElement.parse(SortPar

Re: ES java api: how to handle connectivity problems?

[joergpra...@gmail.com]

Are you using the node client or the transport client?

I recommend to use timeout settings. By default no timeout is set, and
client waits forever, in both normal and exceptional situation.

With transport client, the fault detector will respond with an exception
when no node is connected.

Jörg


On Mon, Dec 1, 2014 at 6:48 PM,  wrote:

> No, in my case the client does not continue. The one-node-cluster goes
> offline and comes back, but the client still hangs. The master-/data-node
> is 1.4.0 and the java client uses 1.3.1.
>
> I tested several scenarios the get the cluster offline: killing it and and
> let the server run into OOM Exceptions.
>
> The client may hang because I assume the cluster state got unavailable,
>> and minimum master condition is no longer met. If you re-add the failed
>> node, the cluster state will be available again, and I think the client
>> will continue.
>>
>> Jörg
>>
>  --
> 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
> https://groups.google.com/d/msgid/elasticsearch/0653ba92-b68e-4b7d-90bb-ae8075ea26e7%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 
https://groups.google.com/d/msgid/elasticsearch/CAKdsXoE83t2fsb5WVNoPJ4PH1Ng%2B_bb3vNk8L5DGDssQdsh0ZA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reliability of ElasticSearch

[Xinli Shang]

I am new to ElasticSearch and asked to design ElasticSearch for log search.
One of the big requirement is availability > 99.9%. If you have designed
elastic search, could you please share your top 3 lessons that you learn to
make elastic search highly available?

-- 
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 
https://groups.google.com/d/msgid/elasticsearch/CAHsnNRh-qPc1Q1j%3DCxY6zh8e7UQ4j%2B8Oj5E4mir5TPC_1Ly0%3Dw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: ES java api: how to handle connectivity problems?

[msbreuer]

No, in my case the client does not continue. The one-node-cluster goes 
offline and comes back, but the client still hangs. The master-/data-node 
is 1.4.0 and the java client uses 1.3.1. 

I tested several scenarios the get the cluster offline: killing it and and 
let the server run into OOM Exceptions. 

The client may hang because I assume the cluster state got unavailable, and 
> minimum master condition is no longer met. If you re-add the failed node, 
> the cluster state will be available again, and I think the client will 
> continue.
>
> Jörg
>

-- 
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 
https://groups.google.com/d/msgid/elasticsearch/0653ba92-b68e-4b7d-90bb-ae8075ea26e7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Marvel Sense is not working over https

[Andrew Rimmer]

Marvel Sense is not working, it hangs when it tried to connect to the 
Elasticsearch API.The rest of Marvel seems to be working fine, as does the 
Elasticsearch API if called directly.

I am using a freshly installed Elasticsearch 1.4.1 and the latest Marvel. 

Elasticsearch is exposed on the internet over SSL as https://mydomain/.

When I profile the javascript in the browser, I can see that Marvel Sense 
actually tries to make the calls to the API over http, even though the API 
and Marval are using https. My Elasticsearch installation is not available 
over the internet to anything other than https. I have nginx installed, 
which passes the elasticsearch calls from 443 to 9200. Again this all works 
fine when calling the Elasticsearch API or the plugins etc.

Any ideas?
 



-- 
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 
https://groups.google.com/d/msgid/elasticsearch/c1672223-3a03-48a2-bf12-90f7938fa12c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Disk Watermark issues with 1.4.0

[Chris Neal]

Thanks for the quick reply Nik :)

I've got updating to 1.4.1 on my TODO list for today, as I see there were
some updates in the Release notes pertaining to this as well.  I might let
things fill up again in Dev and see what happens.

Maybe I wasn't patient enough for the rerouting to start on its own.  It
seems like I waited several minutes before I did it manually, but I'll pay
more attention the next time.

Thanks again for the input.
Chris

On Mon, Dec 1, 2014 at 10:35 AM, Nikolas Everett  wrote:

>
>
> On Mon, Dec 1, 2014 at 11:28 AM, Chris Neal 
> wrote:
>
>> Hi all,
>>
>> I'm running 1.4.0. and using the default settings for:
>>
>> cluster.routing.allocation.disk.watermark.low
>> and
>> cluster.routing.allocation.disk.watermark.high
>>
>> I hit an OOME which caused me to need to cycle a node, and then all
>> shards that should live on that node stayed unallocated once I brought it
>> back up.
>>
>> There was no notification anywhere that I had hit any dis space limits,
>> at least that I could find.  I tried cycling again, nothing.  It wasn't
>> until I tried to manually reroute one of the shards that I got an
>> indication of what was going on:
>>
>>
>> root@ip-10-0-0-45:bddevw07[1038]:~> ./reroute
>>
>> {"error":"RemoteTransportException[[elasticsearch-ip-10-0-0-12][inet[/10.0.0.12:9300]][cluster:admin/reroute]];
>> nested: ElasticsearchIllegalArgumentException[[allocate] allocation of
>> [derbysoft-20141130][0] on node
>> [elasticsearch-ip-10-0-0-45][Li1yyXUHR8qQn6QHCSahCg][ip-10-0-0-45.us-west-2.compute.internal][inet[ip-10-0-0-45.us-west-2.compute.internal/10.0.0.45:9300]]{master=true}
>> is not allowed, reason: [YES(shard is not allocated to same node or
>> host)][YES(node passes include/exclude/require filters)][YES(primary is
>> already active)][YES(below shard recovery limit of [2])][YES(allocation
>> disabling is ignored)][YES(allocation disabling is ignored)][YES(no
>> allocation awareness enabled)][YES(total shard limit disabled: [-1] <=
>> 0)][YES(target node version [1.4.0] is same or newer than source node
>> version [1.4.0])][NO(less than required [15.0%] free disk on node, free:
>> [15.0%])][YES(shard not primary or relocation disabled)]];
>> ","status":400}
>>
>> Then I cleaned up some disk space, but there was no auto re-allocation
>> afterwards.  Once I again tried to manually re-route a shard, then ALL of
>> them began rerouting.
>>
>> My questions are:
>>
>>- Is there a notification log message somewhere that I missed that
>>would have let me know what was going on?  If not, there sure should be!
>>
>>
> A WARN query log every 30 seconds was added in the very last release.
>
>
>>
>>-
>>- Should the shard allocation process have started automatically once
>>I got the disk space issue resolved?
>>
>>
> If you have unallocated shards it should kick in after a few seconds.  It
> takes a few seconds for the cluster to notice the change in disk free.  If
> there aren't unallocated shards I've sometime found that I need to manually
> shift a shard around to prime the pump.  I'm not sure if that has been
> fixed recently though.
>
> I don't think that disk space should prevent a shard from coming up on a
> node that already has it though.  I imagine that depends on how much data
> has to be copied to that node but I'm not sure.
>
> Nik
>
> --
> 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
> https://groups.google.com/d/msgid/elasticsearch/CAPmjWd2YSZo4%3D2_J2quT_aR3F_SGH9p8WPEf-uMUy1W52H-L1g%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 
https://groups.google.com/d/msgid/elasticsearch/CAND3DpgLsPhJBXWFUV8SNN8LR%2ByTdKrFgf6LpceyfDddxqCvxg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Disk Watermark issues with 1.4.0

[Nikolas Everett]

On Mon, Dec 1, 2014 at 11:28 AM, Chris Neal 
wrote:

> Hi all,
>
> I'm running 1.4.0. and using the default settings for:
>
> cluster.routing.allocation.disk.watermark.low
> and
> cluster.routing.allocation.disk.watermark.high
>
> I hit an OOME which caused me to need to cycle a node, and then all shards
> that should live on that node stayed unallocated once I brought it back up.
>
>
> There was no notification anywhere that I had hit any dis space limits, at
> least that I could find.  I tried cycling again, nothing.  It wasn't until
> I tried to manually reroute one of the shards that I got an indication of
> what was going on:
>
>
> root@ip-10-0-0-45:bddevw07[1038]:~> ./reroute
>
> {"error":"RemoteTransportException[[elasticsearch-ip-10-0-0-12][inet[/10.0.0.12:9300]][cluster:admin/reroute]];
> nested: ElasticsearchIllegalArgumentException[[allocate] allocation of
> [derbysoft-20141130][0] on node
> [elasticsearch-ip-10-0-0-45][Li1yyXUHR8qQn6QHCSahCg][ip-10-0-0-45.us-west-2.compute.internal][inet[ip-10-0-0-45.us-west-2.compute.internal/10.0.0.45:9300]]{master=true}
> is not allowed, reason: [YES(shard is not allocated to same node or
> host)][YES(node passes include/exclude/require filters)][YES(primary is
> already active)][YES(below shard recovery limit of [2])][YES(allocation
> disabling is ignored)][YES(allocation disabling is ignored)][YES(no
> allocation awareness enabled)][YES(total shard limit disabled: [-1] <=
> 0)][YES(target node version [1.4.0] is same or newer than source node
> version [1.4.0])][NO(less than required [15.0%] free disk on node, free:
> [15.0%])][YES(shard not primary or relocation disabled)]]; ","status":400}
>
> Then I cleaned up some disk space, but there was no auto re-allocation
> afterwards.  Once I again tried to manually re-route a shard, then ALL of
> them began rerouting.
>
> My questions are:
>
>- Is there a notification log message somewhere that I missed that
>would have let me know what was going on?  If not, there sure should be!
>
>
A WARN query log every 30 seconds was added in the very last release.


>
>-
>- Should the shard allocation process have started automatically once
>I got the disk space issue resolved?
>
>
If you have unallocated shards it should kick in after a few seconds.  It
takes a few seconds for the cluster to notice the change in disk free.  If
there aren't unallocated shards I've sometime found that I need to manually
shift a shard around to prime the pump.  I'm not sure if that has been
fixed recently though.

I don't think that disk space should prevent a shard from coming up on a
node that already has it though.  I imagine that depends on how much data
has to be copied to that node but I'm not sure.

Nik

-- 
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 
https://groups.google.com/d/msgid/elasticsearch/CAPmjWd2YSZo4%3D2_J2quT_aR3F_SGH9p8WPEf-uMUy1W52H-L1g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Disk Watermark issues with 1.4.0

[Chris Neal]

Hi all,

I'm running 1.4.0. and using the default settings for:

cluster.routing.allocation.disk.watermark.low
and
cluster.routing.allocation.disk.watermark.high

I hit an OOME which caused me to need to cycle a node, and then all shards
that should live on that node stayed unallocated once I brought it back up.


There was no notification anywhere that I had hit any dis space limits, at
least that I could find.  I tried cycling again, nothing.  It wasn't until
I tried to manually reroute one of the shards that I got an indication of
what was going on:


root@ip-10-0-0-45:bddevw07[1038]:~> ./reroute
{"error":"RemoteTransportException[[elasticsearch-ip-10-0-0-12][inet[/10.0.0.12:9300]][cluster:admin/reroute]];
nested: ElasticsearchIllegalArgumentException[[allocate] allocation of
[derbysoft-20141130][0] on node
[elasticsearch-ip-10-0-0-45][Li1yyXUHR8qQn6QHCSahCg][ip-10-0-0-45.us-west-2.compute.internal][inet[ip-10-0-0-45.us-west-2.compute.internal/10.0.0.45:9300]]{master=true}
is not allowed, reason: [YES(shard is not allocated to same node or
host)][YES(node passes include/exclude/require filters)][YES(primary is
already active)][YES(below shard recovery limit of [2])][YES(allocation
disabling is ignored)][YES(allocation disabling is ignored)][YES(no
allocation awareness enabled)][YES(total shard limit disabled: [-1] <=
0)][YES(target node version [1.4.0] is same or newer than source node
version [1.4.0])][NO(less than required [15.0%] free disk on node, free:
[15.0%])][YES(shard not primary or relocation disabled)]]; ","status":400}

Then I cleaned up some disk space, but there was no auto re-allocation
afterwards.  Once I again tried to manually re-route a shard, then ALL of
them began rerouting.

My questions are:

   - Is there a notification log message somewhere that I missed that would
   have let me know what was going on?  If not, there sure should be!
   - Should the shard allocation process have started automatically once I
   got the disk space issue resolved?


Thanks!
Chris

-- 
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 
https://groups.google.com/d/msgid/elasticsearch/CAND3DphhmWn-amiDBrmYi4rB_tYZa7%3Dn2M9PF5jVY%3DfhPTqMpg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Spaces issue in pie chart

[Pavan Elthepu]

Here is my mapping:
{
"mappings" : {
"*default*" : {
"properties" : {
"state" : {"type": "string", "index" : "not_analyzed" }
}
}
}
}
';

On Monday, December 1, 2014 8:00:01 PM UTC+5:30, Pavan Elthepu wrote:
>
> Hi,
> I have an issue with pie chart. Whenever I have a content with space, it 
> is treating as separate values.
> Ex: I have, 'United States'
> It is showing two slices in pie chart. One is 'United', and another one, 
> 'States'.
>
> here is my mapping
> {
> "mappings" : {
> "*default*" : {
> "properties" : {
> "state" : {"type": "string", "index" : "not_analyzed" }
> }
> }
> }
> }
> ';
>
> may i know where I am doing wrong?
>

-- 
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 
https://groups.google.com/d/msgid/elasticsearch/f3779d74-53c6-499a-8826-bb7fe581669f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Is the Filters aggregation supposed to work in Kibana 4?

[Stefan Meisner Larsen]

When selecting the Filters sub aggregation in Kibana 4, I only has a Query 
field for the specification. I really dont know what to do with that.
What I want is shown in the query below, which I execute directly against 
elasticsearch 1.4.0.

Is the Filters sub aggregation working? If yes, how do I use it?

Is there any way to import a "hand made" query as the one below into Kibana?

Thanks for any help!

/Stefan

My elasticsearch query:

GET _search
{
  "query": {
"filtered": {
  "query": {
"match_all": {}
  },
  "filter": {
"bool": {
  "must": [
{
  "term": {
"type": "jmx"
  }
},
{
  "term": {
"variable": "MeanProcessingTime"
  }
}
  ]
}
  }
}
  },
  "aggs": {
"histogram_agg": {
  "date_histogram": {
"field": "@timestamp",
"interval": "hour"
  },
  "aggs": {
"component_agg": {
  "filters": {
"filters": {
  "engineReceiver": {
"bool": {
  "must": [
{
  "term": {
"mbeanalias": "receiverChannelCamelRoute"
  }
},
{
  "term": {
"group": "eti.engine"
  }
}
  ]
}
  },
  "engineSender": {
"bool": {
  "must": [
{
  "term": {
"mbeanalias": "senderChannelCamelRoute"
  }
},
{
  "term": {
"group": "eti.engine"
  }
}
  ]
}
  },
  "incomingAmqp": {
"bool": {
  "must": [
{
  "term": {
"mbeanalias": "camelRoute"
  }
},
{
  "term": {
"group": "eti.gateway.incoming.amqp"
  }
}
  ]
}
  },
  "outgoingAmqp": {
"bool": {
  "must": [
{
  "term": {
"mbeanalias": "camelRoute"
  }
},
{
  "term": {
"group": "eti.gateway.outgoing.amqp"
  }
}
  ]
}
  }
}
  },
  "aggs": {
"my_average": {
  "avg": {
"field": "metric_value_number"
  }
}
  }
}
  }
}
  }
}

-- 
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 
https://groups.google.com/d/msgid/elasticsearch/d8478257-1819-451f-97ed-617a4956c805%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Spaces issue in pie chart

[David Pilato]

Hard to say without a full repro.

But you are right, the way for doing this is by setting your field as not 
analyzed.


-- 
David Pilato | Technical Advocate | Elasticsearch.com
@dadoonet  | @elasticsearchfr 
 | @scrutmydocs 




> Le 1 déc. 2014 à 15:30, Pavan Elthepu  a écrit :
> 
> Hi,
> I have an issue with pie chart. Whenever I have a content with space, it is 
> treating as separate values.
> Ex: I have, 'United States'
> It is showing two slices in pie chart. One is 'United', and another one, 
> 'States'.
> 
> here is my mapping
> {
> "mappings" : {
> "default" : {
> "properties" : {
> "state" : {"type": "string", "index" : "not_analyzed" }
> }
> }
> }
> }
> ';
> 
> may i know where I am doing wrong?
> 
> -- 
> 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 
> https://groups.google.com/d/msgid/elasticsearch/a08c3105-d14e-458b-9edc-64aaf3c2eafb%40googlegroups.com
>  
> .
> For more options, visit https://groups.google.com/d/optout 
> .

-- 
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 
https://groups.google.com/d/msgid/elasticsearch/B9990667-AA86-4DE3-AD47-289858A01C87%40pilato.fr.
For more options, visit https://groups.google.com/d/optout.

Spaces issue in pie chart

[Pavan Elthepu]

Hi,
I have an issue with pie chart. Whenever I have a content with space, it is 
treating as separate values.
Ex: I have, 'United States'
It is showing two slices in pie chart. One is 'United', and another one, 
'States'.

here is my mapping
{
"mappings" : {
"*default*" : {
"properties" : {
"state" : {"type": "string", "index" : "not_analyzed" }
}
}
}
}
';

may i know where I am doing wrong?

-- 
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 
https://groups.google.com/d/msgid/elasticsearch/a08c3105-d14e-458b-9edc-64aaf3c2eafb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: routing vs aliasing

[Mohamed Hedi ABIDI]

thanks David!



Le lundi 1 décembre 2014 13:46:48 UTC+1, David Pilato a écrit :
>
> Option 3: both.
>
> Routing is "in which shard I want to send a doc or in which shards I want 
> to run a search?"
>
> Aliases are shortcuts to know in which indices/shards you want to query. 
> It can be a simple list of indices and it may contain a routing key.
>
> Alias with routing is a very good approach IMHO.
>
>
>
> --
> David ;-)
> Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
>
> Le 1 déc. 2014 à 13:49, Mohamed Hedi ABIDI > 
> a écrit :
>
> Hello,
>
>
> I'm planning a strategy for querying millions of docs :
>
>- Option 1 - time based indexation + aliasing : explaned here => 
>
> http://www.elasticsearch.org/guide/en/elasticsearch/guide/current/time-based.html
>
>
>- Option 2 - custom document routing : Explaned here => 
>http://www.elasticsearch.org/blog/customizing-your-document-routing/
>
> What are the differences or advantages when using routing or aliasing?
>
> -- 
> 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 elasticsearc...@googlegroups.com .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/elasticsearch/fb5ad148-3f23-409f-8fc0-b991eb0e73c1%40googlegroups.com
>  
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>
>

-- 
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 
https://groups.google.com/d/msgid/elasticsearch/d9e5f0f8-cf8a-4bba-bd5a-081210712e94%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Controlling users to change the Kibana dashboard settings and saving.

[Pillalamarri Kaushik]

Hi All,

I would like to control the changes that are being made to the Kibana 
dashboard by users. I would like to authenticate the user doing that by 
asking for username and password before making changes or before saving the 
changes made.

I am using windows operating system.

Kindly help me on this by throwing some insights on the same.

Thanks,
Kaushik

-- 
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 
https://groups.google.com/d/msgid/elasticsearch/fd04b909-4fec-40ed-887e-e9be5a2245f2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Trouble formulating a query with Java API

[Roger de Cordova Farias]

You can use the toString() method of the SearchRequestBuilder to see the
generated query. With your example it was:

{
  "size" : 10,
  "query" : {
"multi_match" : {
  "query" : "searchterm",
  "fields" : [ "FIELD1.not_analyzed", "FIELD2.partial" ]
}
  },
  "sort" : [ {
"SCORE" : {
  "order" : "desc"
}
  } ]
}

This query looks ok. Are you not receiving any results? Not even the
"total" value?

2014-11-28 16:11 GMT-02:00 Maarten Roosendaal :

> Hi,
>
> I have the following (json) query i use:
> {
> "fields": ["ID","ID2"],
> "query": {
> "filtered": {
> "query": {
> "multi_match": {
>"query": "",
>"fields": ["FIELD1.not_analyzed","FIELD2.partial"]
> }
> },
> "filter": {
> "bool": {
> "must": [
> { "term" : { "FIELD2": "No" } },
> { "term" : {"FIELD3": "Yes" } }
>  ]
> }
> }
> }
> },
> "sort": [
>{
>   "SCORE": {
>  "order": "desc"
>   }
>}
> ]
> }
>
> but my attempts a building the same query with the Java API hasn't been
> fruitful.The goal is to search for a match based on a searchterm in several
> fields and some fields are more important than others.
>
> I know the basic setup:
>
> .client
> .prepareSearch()
> .setSearchType(SearchType.QUERY_AND_FETCH)
> .setQuery(QueryBuilders.multiMatchQuery(searchterm, "FIELD1.not_analyzed",
> "FIELD2.partial"))
> .addSort("SCORE", SortOrder.DESC)
> .setSize(10)
> .execute()
> .actionGet();
>
> but there are no results while the json query has a returnvalue. So 2
> questions:
> 1) i could use some help formulating the right Java query
> 2) why is the json return stuff and the java query not?
>
> Thanks,
> Maarten
>
>  --
> 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
> https://groups.google.com/d/msgid/elasticsearch/166a43b2-d92c-4307-abed-2ce95ae87fb2%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 
https://groups.google.com/d/msgid/elasticsearch/CAJp2532Z8bataicKD%2BrUECd4yoJkXZd47MMVssgoE%3DK8opXhCg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Aggregates filters

[Robert Gardam]

I have a query that i'm trying to run against ES 1.3.4 and i'm not able to 
use the filters buckets.

Here is my query. It's actually pulled straight from the documentation with 
some small changes.

{
"aggs" : {
"messages" : {
  "filters" : {
"filters" : {
  "errors" :   { "term" : { "request" : " blah.json"   }},
  "warnings" : { "term" : { "domain" : "blah" }}
}
  },
  "aggs" : {
"monthly" : {
  "histogram" : {
"field" : "timestamp",
"interval" : "1M"
  }
}
  }
}
  
 }
}

I get back quite a few errors, but this one seems most likely to be the 
most important.

SearchParseException[[logstash-2014.12.01.12][2]: from[-1],size[-1]: Parse 
Failure [Could not find aggregator type [filters] in [messages]]]; }]",
   "status": 400

-- 
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 
https://groups.google.com/d/msgid/elasticsearch/62353474-16e9-4c5d-9a26-b552e3617ccc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: routing vs aliasing

[David Pilato]

Option 3: both.

Routing is "in which shard I want to send a doc or in which shards I want to 
run a search?"

Aliases are shortcuts to know in which indices/shards you want to query. It can 
be a simple list of indices and it may contain a routing key.

Alias with routing is a very good approach IMHO.



--
David ;-)
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

> Le 1 déc. 2014 à 13:49, Mohamed Hedi ABIDI  a écrit :
> 
> Hello,
> 
> 
> I'm planning a strategy for querying millions of docs :
> 
> Option 1 - time based indexation + aliasing : explaned here => 
> http://www.elasticsearch.org/guide/en/elasticsearch/guide/current/time-based.html
> Option 2 - custom document routing : Explaned here => 
> http://www.elasticsearch.org/blog/customizing-your-document-routing/
> What are the differences or advantages when using routing or aliasing?
> 
> -- 
> 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 
> https://groups.google.com/d/msgid/elasticsearch/fb5ad148-3f23-409f-8fc0-b991eb0e73c1%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
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 
https://groups.google.com/d/msgid/elasticsearch/D38CE760-3A29-4561-95DA-B66BF0BD%40pilato.fr.
For more options, visit https://groups.google.com/d/optout.

Re: Unassigned Shards Of A Newer Elasticsearh Version

[Umutcan]

Yes, I am sure that there is enough disk space. Also, I have tested 
before that I can solve this by upgrading other nodes.


On 01-12-2014 10:24, David Pilato wrote:

Are you sure you are not running low on disk space?

If you have less than 15% free, elasticsearch won’t allocate replicas.



--
*David Pilato* | /Technical Advocate/ | *Elasticsearch.com 
*
@dadoonet  | @elasticsearchfr 
 |@scrutmydocs 





Le 1 déc. 2014 à 09:21, Umutcan > a écrit :


Hi,

When I was doing some experiments on my Elasticsearch cluster, I 
found that cluster cannot assign replicas of a shards on the node 
which have a new version of Elasticsearch (1.4.1). I have seen this 
before and I can fix this by upgrading old nodes. But, I am wondering 
that if there is a way to fix this issue without upgrade.


Is there any idea or a solution?

Thanks,

Umutcan

PS: Other nodes in the cluster have Elasticsearch 1.4.

--
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 
https://groups.google.com/d/msgid/elasticsearch/547C251B.9060809%40gamegos.com.

For more options, visit https://groups.google.com/d/optout.


--
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 
https://groups.google.com/d/msgid/elasticsearch/C12508F1-79F2-4346-B6C0-3F020CE7E567%40pilato.fr 
.

For more options, visit https://groups.google.com/d/optout.


--
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 
https://groups.google.com/d/msgid/elasticsearch/547C5D82.60304%40gamegos.com.
For more options, visit https://groups.google.com/d/optout.

Re: heap size/filter cache

[Nikolas Everett]

Cache keys are pretty much the input filter by default. Specifying your own
keys can certainly help.
On Dec 1, 2014 7:05 AM, "Audrius Bugas"  wrote:

> Thank you for answer. We had lot's of cache evictions so we increased
> cache size. Should I use custom cache keys and try to make it smaller?
> What cache keys are generated by default? Is it full filter query dsl
> string?
>
> 2014 m. lapkritis 29 d., šeštadienis 13:01:59 UTC+2, Adrien Grand rašė:
>>
>> When you cache filters, there are two things that can take memory: the
>> cached bitsets and the filter itself (which is used as a key). And while we
>> have APIs to estimate the memory usage for bitsets, we do not have anything
>> for filters unfortunately. So if you happen to have lots of small segments
>> on your machine or if you use filters that can have a high memory footprint
>> (like terms filters with lots of terms) then the memory usage of your
>> filter cache might be underestimated because of the filters which are not
>> taken into account.
>>
>> By the way, 20% is a bit high for a filter cache size. Recent versions of
>> elasticsearch have a default value of 10% (http://www.elasticsearch.org/
>> guide/en/elasticsearch/reference/current/index-modules-cache.html) which
>> should already allow for caching lots of caches.
>>
>> On Fri, Nov 28, 2014 at 9:58 AM, Audrius Bugas 
>> wrote:
>>
>>> Hello, I have 8GB dedicated for heap, 20% heap is dedicated for filters
>>> cache. When clear filter cache from api it clears ~4GB memory from heap
>>> (way more then filters cache). Is it normal, or I have some problems with
>>> cached filters? We are using warmers, but this should not be a reason...
>>>
>>> --
>>> 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 elasticsearc...@googlegroups.com.
>>> To view this discussion on the web visit https://groups.google.com/d/
>>> msgid/elasticsearch/9467f35b-b48c-4a49-949d-250ea6ea8e5d%
>>> 40googlegroups.com
>>> 
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>>
>> --
>> Adrien Grand
>>
>  --
> 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
> https://groups.google.com/d/msgid/elasticsearch/32533606-c3d8-48fe-8020-d2bef3ee42c7%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 
https://groups.google.com/d/msgid/elasticsearch/CAPmjWd0s%3DS5kZbw_cug2LB1Lt%2BekOGGGzmGF_uAJRkW6yN5s%3Dg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: DocumentMissingException ScanScroll

[eunever32]

yikes found it! 

But in *my* code, ES is fine!

On Saturday, November 29, 2014 12:08:19 PM UTC, eune...@gmail.com wrote:

> Hi
>
> Client JavaAPI
> Version 1.2.1
> Requests: bulk
> (no parent child mapping)
> Does use nested structure.
>
> Using scan and scroll to populate thousands (maybe millions) of delete 
> requests. It works like this:
>
> Scan Search  (for all documents with field f = 'the value')
>> Scroll in batches of say 1000:
>> create bulk delete requests and execute;
>> repeat until the end
>
>
> This used to work no problem.
>
> But now giving apparently random DocumentMissingException
>
> Can't think why this might happen.
>
> The mappings have been added to over time. Would that matter? I have heard 
> of the need to re-index.
>
> I'm not even sure if the DocumentMissingException meant that the document 
> was there initially.
>
> It could be a bug in the code. But it's single threaded and I can't see 
> how, if the document was there during the scan it's not there at the delete?
>
> Anybody suggest what might be happening? 
>
> Obvious workaround is to simply ignore DocumentMissingException on delete 
> .. but why 
>
> Thanks.
>  
>

-- 
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 
https://groups.google.com/d/msgid/elasticsearch/d94413ef-bc1e-4879-a607-62ca1f802203%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: heap size/filter cache

[Audrius Bugas]

Thank you for answer. We had lot's of cache evictions so we increased cache 
size. Should I use custom cache keys and try to make it smaller?  What 
cache keys are generated by default? Is it full filter query dsl string?

2014 m. lapkritis 29 d., šeštadienis 13:01:59 UTC+2, Adrien Grand rašė:
>
> When you cache filters, there are two things that can take memory: the 
> cached bitsets and the filter itself (which is used as a key). And while we 
> have APIs to estimate the memory usage for bitsets, we do not have anything 
> for filters unfortunately. So if you happen to have lots of small segments 
> on your machine or if you use filters that can have a high memory footprint 
> (like terms filters with lots of terms) then the memory usage of your 
> filter cache might be underestimated because of the filters which are not 
> taken into account.
>
> By the way, 20% is a bit high for a filter cache size. Recent versions of 
> elasticsearch have a default value of 10% (
> http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/index-modules-cache.html)
>  
> which should already allow for caching lots of caches.
>
> On Fri, Nov 28, 2014 at 9:58 AM, Audrius Bugas  > wrote:
>
>> Hello, I have 8GB dedicated for heap, 20% heap is dedicated for filters 
>> cache. When clear filter cache from api it clears ~4GB memory from heap 
>> (way more then filters cache). Is it normal, or I have some problems with 
>> cached filters? We are using warmers, but this should not be a reason...
>>
>> -- 
>> 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 elasticsearc...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/elasticsearch/9467f35b-b48c-4a49-949d-250ea6ea8e5d%40googlegroups.com
>>  
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> -- 
> Adrien Grand
>  

-- 
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 
https://groups.google.com/d/msgid/elasticsearch/32533606-c3d8-48fe-8020-d2bef3ee42c7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

routing vs aliasing

[Mohamed Hedi ABIDI]

Hello,


I'm planning a strategy for querying millions of docs :

   - Option 1 - time based indexation + aliasing : explaned here => 
   
http://www.elasticsearch.org/guide/en/elasticsearch/guide/current/time-based.html


   - Option 2 - custom document routing : Explaned here 
   => http://www.elasticsearch.org/blog/customizing-your-document-routing/

What are the differences or advantages when using routing or aliasing?

-- 
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 
https://groups.google.com/d/msgid/elasticsearch/fb5ad148-3f23-409f-8fc0-b991eb0e73c1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Compatibility between elasticsearch 1.4.1 and elasticsearch client 1.3.5

[David Pilato]

Yes.

--
David ;-)
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

> Le 1 déc. 2014 à 12:02, Noam Gazit  a écrit :
> 
> Hi,
> 
> Is the elasticsearch 1.3.5 client compatible with elasticsearch 1.4.1?
> Is it possible to use the 1.3.5 client against a 1.4.1 cluster?
> 
> Thanks,
> Noam 
> -- 
> 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 
> https://groups.google.com/d/msgid/elasticsearch/7f88edaf-16f7-4795-9b3a-aae0f5ea47b6%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
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 
https://groups.google.com/d/msgid/elasticsearch/B29F7C57-F8E3-4826-AA2E-5C438A6D6993%40pilato.fr.
For more options, visit https://groups.google.com/d/optout.

Re: What does the "aggs" field in my index settings represent.

[Anil Karaka]

Oh, things like that happen?

Thanks.

On Monday, December 1, 2014 3:14:27 PM UTC+5:30, Adrien Grand wrote:
>
> "aggs" makes no sense in the context of index settings, it looks to me 
> like someone mistakenly submitted a search request with aggregations to the 
> update settings endpoint instead of the search endpoint.
>
> On Mon, Dec 1, 2014 at 8:08 AM, Anil Karaka  > wrote:
>
>> {
>>
>>- test_index: 
>>{
>>   - settings: 
>>   {
>>  - index: 
>>  {
>> - creation_date: "1416836998944",
>> - warmer: 
>> {
>>- enabled: "false"
>>},
>> - uuid: "R2eL4uvvQbGtLKAaDPrmaQ",
>> - number_of_replicas: "1",
>> - aggs: 
>> {
>>- group_by_age: 
>>{
>>   - aggs: 
>>   {
>>  - group_by_gender: 
>>  {
>> - aggs: 
>> {
>>- average_balance: 
>>{
>>   - avg: 
>>   {
>>  - field: "balance"
>>  }
>>   }
>>},
>> - terms: 
>> {
>>- field: "gender",
>>- order: 
>>{
>>   - average_balance: "desc"
>>   }
>>}
>> }
>>  },
>>   - range: 
>>   {
>>  - field: "age",
>>  - ranges: 
>>  [
>> - 
>> {
>>- to: "29",
>>- from: "20"
>>},
>> - 
>> {
>>- to: "39",
>>- from: "30"
>>},
>> - 
>> {
>>- to: "49",
>>- from: "40"
>>}
>> ]
>>  }
>>   }
>>},
>> - number_of_shards: "5",
>> - refresh_interval: "5s",
>> - version: 
>> {
>>- created: "1040099"
>>},
>> - size: "0"
>> }
>>  }
>>   }
>>
>> }
>>
>> I'm a little confused by "aggs" in my index settings, what does it mean? 
>> Is it related to index warmers, or index aliases..?
>>
>> Thank you.
>>
>> -- 
>> 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 elasticsearc...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/elasticsearch/1c5dbc63-9d1a-434f-b0b9-0311b2efa21a%40googlegroups.com
>>  
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> -- 
> Adrien Grand
>  

-- 
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 
https://groups.google.com/d/msgid/elasticsearch/e7f63b61-41e5-4fd8-93f6-6f12df6499d1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

number of results in aggregate

[isart . montane]

Hi All,

At the company I work for we are evaluating ES to replace certain type of 
queries that we run now on DB. On database we have more than 40k tables and 
we run queries like this one.

SELECT
t1.user_id
FROM 
table1 t1 join table2 t2 on t1.user_id = t2.user_id 
WHERE 
t1.name like "%am%" 
AND t2.followers_count>1;

For that query we need the user_id and the number of users affected (count).

On ES I've created an index with an extra field that contains the table 
name, and I've managed to write the query like that:

{
  "query": {
"bool": {
  "should": [
{
  "terms": {
"table_name": [ "t1" ],
"minimum_should_match": 1
  }
},
{
  "terms": {
"table_name": [ "t2" ],
"minimum_should_match": 1
  }
}
  ]
}
  },
  "size": 0,
  "aggs" : {
"user_ids": {
"terms" : { 
"field" : "user_id",
"min_doc_count": 2
}
}
}
}


The problem I'm facing here is that I cannot get the number of user user_id 
affected. I get the user_ids as an aggregate, but I couldn't find the way 
to get the number of them. I've tried to get the count on the client side, 
but sometimes that list can get really big (millions) so it's quite a waste 
of memory.

Any help? Is there a better way to do that?

Thanks,
Isart Montane Mogas


-- 
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 
https://groups.google.com/d/msgid/elasticsearch/05ecf5f0-6313-4ee4-84a7-d36c0cc844ff%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Unix-like permissions and confidential documents in Elasticsearch

[dylan . bowden]

You're right, I will correct the blog accordingly.

However, if I'm understanding the nginx solution correctly, it does require 
that each document is indexed with all the people that can access it or 
doesn't it? The downside of that would be that each time a user is added/ 
removed to/ from a user group then all relevant documents would need to be 
re-indexed (which could be massive). Also, there may be thousands or tens 
of thousands of people that could access a particular document.
Also, if I decided to use the nginx solution (with user groups instead of 
users) then I would still need a custom script to handle "the user must be 
a member of this or that combination of user groups" scenario, wouldn't I? 


Le lundi 1 décembre 2014 10:30:31 UTC, Jörg Prante a écrit :
>
> From your blog:
>
> "Elasticsearch has no in-built way to say that only certain people can 
> find certain documents and there's no indication that will change."
>
> This is not true. Elasticsearch is multi-tenant. You can user filter 
> aliases to forward requests to the docs a tenant is restricted to.
>
> Examples:
>
>
> http://www.elasticsearch.org/blog/restricting-users-kibana-filtered-aliases/
>
>
> http://opennomad.com/content/controlling-access-elasticsearch-filtered-aliases-nginx-and-tokens
>
> Jörg
>
> On Mon, Dec 1, 2014 at 11:23 AM, > 
> wrote:
>
>> Hi,
>>
>> I have been trying to find a way to handle document access rights in 
>> Elasticsearch. I have come up with a solution and written a few words 
>> trying to explain it in a blog.
>> https://www.tuleap.org/elasticsearch-dealing-complex-permissions
>>
>> In order to avoid duplication, I'm not going to repeat it all here but 
>> the general idea is to create a script that checks a document's user groups 
>> against a list passed in the query.
>> I'm posting it here because it would be good to have feedback from people 
>> who know a lot more about elasticsearch than I do. Also, would anyone know 
>> if there is a way of optimising it?
>> Thanks
>>
>> -- 
>> 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 elasticsearc...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/elasticsearch/94ec8170-89e1-4f85-af1d-bf0828e5d7d2%40googlegroups.com
>>  
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
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 
https://groups.google.com/d/msgid/elasticsearch/0bd7d7b2-d38c-43ed-a65a-5764fb6abef1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Unix-like permissions and confidential documents in Elasticsearch

[joergpra...@gmail.com]

>From your blog:

"Elasticsearch has no in-built way to say that only certain people can find
certain documents and there's no indication that will change."

This is not true. Elasticsearch is multi-tenant. You can user filter
aliases to forward requests to the docs a tenant is restricted to.

Examples:

http://www.elasticsearch.org/blog/restricting-users-kibana-filtered-aliases/

http://opennomad.com/content/controlling-access-elasticsearch-filtered-aliases-nginx-and-tokens

Jörg

On Mon, Dec 1, 2014 at 11:23 AM,  wrote:

> Hi,
>
> I have been trying to find a way to handle document access rights in
> Elasticsearch. I have come up with a solution and written a few words
> trying to explain it in a blog.
> https://www.tuleap.org/elasticsearch-dealing-complex-permissions
>
> In order to avoid duplication, I'm not going to repeat it all here but the
> general idea is to create a script that checks a document's user groups
> against a list passed in the query.
> I'm posting it here because it would be good to have feedback from people
> who know a lot more about elasticsearch than I do. Also, would anyone know
> if there is a way of optimising it?
> Thanks
>
> --
> 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
> https://groups.google.com/d/msgid/elasticsearch/94ec8170-89e1-4f85-af1d-bf0828e5d7d2%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 
https://groups.google.com/d/msgid/elasticsearch/CAKdsXoFQKkZxCzQL%2BZpeH9bAQGtBCMcQK30b2zE6hA8HtXX6rw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Unix-like permissions and confidential documents in Elasticsearch

[dylan . bowden]

Hi,

I have been trying to find a way to handle document access rights in 
Elasticsearch. I have come up with a solution and written a few words 
trying to explain it in a blog.
https://www.tuleap.org/elasticsearch-dealing-complex-permissions

In order to avoid duplication, I'm not going to repeat it all here but the 
general idea is to create a script that checks a document's user groups 
against a list passed in the query.
I'm posting it here because it would be good to have feedback from people 
who know a lot more about elasticsearch than I do. Also, would anyone know 
if there is a way of optimising it?
Thanks

-- 
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 
https://groups.google.com/d/msgid/elasticsearch/94ec8170-89e1-4f85-af1d-bf0828e5d7d2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Indices not recovering after elasticsearch upgrade (1.0.2 -> 1.4.1)

[Michel Conrad]

Hi,

I just updated our test environment from 1.0.2 to 1.4.1 and some
indices failed to recover, which seems to be related to the checksum
verfication introduces in 1.3.

 [2014-11-28 09:40:48,019][WARN ][cluster.action.shard ] [NODE1]
[index][0] received shard failed for [index][0],
node[CWq_uCPhRKqGEAvtS1jkug], [P], s[INITIALIZING], indexUUID
[yJBShgqGQgi0q5NbMms0Sg], reason [Failed to start shard, message
[IndexShardGatewayRecoveryException[[index][0] failed to fetch index
version after copying it over]; nested:
CorruptIndexException[[index][0] Preexisting corrupted index
[corrupted_JysmZSaLRXWN_BgqpRSo6Q] caused by:
CorruptIndexException[checksum failed (hardware problem?) :
expected=16ncx91 actual=1xc6e7g
resource=(org.apache.lucene.store.FSDirectory$FSIndexOutput@1afc89e8)]
org.apache.lucene.index.CorruptIndexException: checksum failed
(hardware problem?) : expected=16ncx91 actual=1xc6e7g
resource=(org.apache.lucene.store.FSDirectory$FSIndexOutput@1afc89e8)
at 
org.elasticsearch.index.store.LegacyVerification$Adler32VerifyingIndexOutput.verify(LegacyVerification.java:73)
at org.elasticsearch.index.store.Store.verify(Store.java:365)
at 
org.elasticsearch.indices.recovery.RecoveryTarget$FileChunkTransportRequestHandler.messageReceived(RecoveryTarget.java:599)
at 
org.elasticsearch.indices.recovery.RecoveryTarget$FileChunkTransportRequestHandler.messageReceived(RecoveryTarget.java:536)
at 
org.elasticsearch.transport.netty.MessageChannelHandler$RequestHandler.run(MessageChannelHandler.java:275)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)

In order to get the indices to recover I check them using
org.apache.lucene.index.CheckIndex, the indices seemed ok, as no error
was reported. Reopening the indices did not solve the issue.

After deleting the checksums file as well as the corrupted_XXX marker
file, the indices finally recovered correctly. I suppose that the
verfication step here is simply skipped as there are no checksums to
compare against.

I am currently trying to understand the issue. Might it be that the
checksums file itself might have been corrupted. Also, while I did not
see any direct consequences of deleting the checksums file, I just
want to be sure that deleting them does not cause any issues.

Any thoughts or help is greatly appreciated,
Michel

-- 
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 
https://groups.google.com/d/msgid/elasticsearch/CAH0sEYgS7ts_t%3DFHkBvHk0vyt_NXDsE_v4iLergwP0g0sy6kGw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: AutoCompletion Suggester - Duplicate record in suggestion return

[Tom]

Hi,

i still have same problems with completion suggest duplicates of old and 
updates data using ES 1.4.x
Only way that fixed it so far was using _optimize?max_num_segments=1 which 
has performance and maybe other impacts i assume.

Is there another solution than _optimize?max_num_segments=1?

Thx
Tom


Am Montag, 28. April 2014 11:21:49 UTC+2 schrieb Kaspars Sprogis:
>
> Hi,
>
> I have exactly same problem.
> I resolved duplicates and appearance of deleted items by running 
> "_optimize?only_expunge_deletes=true" on daily basis.
>
> However i have still problem with updates. Even if data have been updated 
> for items in index, they still show old data when searching.
> Only solution i found is running: "_optimize?max_num_segments=1'".
>
> However i have quite a lot of updates and this get me worried, because of 
> Alexander's note:
>
>> if you do regular updates on that index, you should not update down to 
>> one single segment
>
>
> Alexander Reelsen, could you please advise, why we shouldn't do that or 
> does this create some permanent damage for optimization logic or does it 
> affects performance for search later?
> What should we do instead?
>
> Thank you.
>
> On Wednesday, April 23, 2014 1:52:16 AM UTC+3, Alexander Reelsen wrote:
>>
>> Hey
>>
>> if you do regular updates on that index, you should not update down to 
>> one single segment. Do you have an example, where the updates do not work 
>> as expected?
>>
>>
>> --Alex
>>
>>
>> On Tue, Apr 22, 2014 at 10:51 AM, kidkid  wrote:
>>
>>> Hey Alexander,
>>> Thanks for your reply.
>>> Currently I also manual do optimize by running optimize: 
>>> host:9200/completion_index/_optimize?max_num_segments=1 
>>> I think it's a work around solution. I would like to make it better.
>>>
>>> Sometime, I also have problem with update payload, when I change 
>>> payload, the completion is not change too.
>>>
>>>
>>> On Monday, April 21, 2014 7:26:13 PM UTC+7, Alexander Reelsen wrote:
>>>
 Hey,

 the output is used to unify the search results, otherwise the input is 
 used. The payload itself is just meta information.
 The main reason, why you see the suggestion twice is, that even though 
 a document is deleted and cannot be found anymore, the suggest data 
 structures are only cleaned up during merges/optimizations. Running 
 optimize should fix this.

 Makes sense?


 --Alex



 On Sun, Apr 13, 2014 at 12:49 PM, kidkid  wrote:

> I have figure out the problem.
> The main problem is I have used the same output for all input then ES 
> have been wrong in this case.
>
> I still trying to improve the performance. I am just test on 64Gb Ram 
> server (32Gb for ES 1.0.1) 24 core.
> Have only 2 record but it took me 3ms to suggest.
>
>
>
>
>
>
> On Sunday, April 13, 2014 4:53:21 PM UTC+7, kidkid wrote:
>>
>> There are something really strange.
>> I don't know whether anyone have worked with this such feature or 
>> it's just not-stable feature.
>> If we do index same input, and different output,payload, then only 
>> one result found.
>>
>> Do anyone tell me how could I fix it ?
>>
>>
>>  -- 
> 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 elasticsearc...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/elasticsearch/f6547a58-c002-4ff3-80c9-2052e1d14ddd%
> 40googlegroups.com 
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

  -- 
>>> 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 elasticsearc...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/elasticsearch/b3bf74ad-c729-4e78-9ebd-364c6c000819%40googlegroups.com
>>>  
>>> 
>>> .
>>>
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>

-- 
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 
https://groups.google.com/d/msgid/elasticsearch/bf7ccf72-d65c-4e1c-a6ec-b3a11c56f834%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Why is Kibana 4.0 no longer a status webapp?

[Matt Dainty]

* Kevin Burton  [2014-11-30 12:29:33]:
> Curious why Kibana 4.0 is no longer a static webap and why it requires a 
> Java daemon. 
> 
> Is this strictly required?  I guess I'm fine if it is but why?  What does 
> the Java daemon provide?

The Java daemon is just because it's a Ruby web application running with
JRuby. As the application is Rack-based, you can run it under any
Rack-compatible server if you're prepared to hack about with it.

>From my experimentation I got it running under Apache & Passenger and
from what I can tell there's very little that is dynamic; it still is just
HTML/Javascript under the hood. There are a couple of URLs that are dynamic
although I'm not convinced they could be made static too.

It just comes with its own webserver to minimise the barrier to entry.

I put my findings and configuration here:

https://github.com/elasticsearch/kibana/issues/1991

when I asked if it was possible.

> I guess I liked that it was a static webapp as it allows for easier 
> integration on our end.

Same, I didn't want to run Yet Another Webserver that has fewer features,
etc. etc. and I liked how v3 was easy to deploy & integrate.

Matt

-- 
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 
https://groups.google.com/d/msgid/elasticsearch/20141201100656.GD28742%40simulant.bodgit-n-scarper.com.
For more options, visit https://groups.google.com/d/optout.

Compatibility between elasticsearch 1.4.1 and elasticsearch client 1.3.5

[Noam Gazit]

Hi,

Is the elasticsearch 1.3.5 client compatible with elasticsearch 1.4.1?
Is it possible to use the 1.3.5 client against a 1.4.1 cluster?

Thanks,
Noam 

-- 
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 
https://groups.google.com/d/msgid/elasticsearch/7f88edaf-16f7-4795-9b3a-aae0f5ea47b6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: After using term aggregation search api will not get the desired result. Tried everything ??Help me out

[bharat bisht]

Actually I am not getting the desired result by using the below mentioned 
aggregation.

"username   ip  (which is used more)  count (how many time that ip used)" 
that would be my expected result and i dont want to use more then one curl 
call for this result. I want only one search api by this i can get what i 
want.
 
So, i tried this aggregation but didn't get the count (how many times that 
IP used) and also want to show only the IP who have TOP count. For further 
understanding see below.

User 1 ---IP1 --- count (11) mean that IP used most by user1
  ---IP2 ---count(4)
  ---IP3 ---count(1)

User 2 ---IP1 --- count (8) mean that IP used most by user2
  ---IP2 ---count(7)
  ---IP3 ---count(3)

User 3 ---IP1 --- count (10) mean that IP used most by user3
  ---IP2 ---count(9)
  ---IP3 ---count(8)

So the result would be like this using only one query,

User 1 ---IP1 --- count (11) mean that IP used most by user1
User 2 ---IP1 --- count (8) mean that IP used most by user2
User 3 ---IP1 --- count (10) mean that IP used most by user3

Note : IPs are different for each user.

On Saturday, November 29, 2014 3:45:46 AM UTC+5:30, Adrien Grand wrote:
>
> What is the issue with this aggregation?
>
> On Fri, Nov 28, 2014 at 7:41 PM, bharat bisht  > wrote:
>
>> Hey guys,
>> I am stuck in the problem like currently i'm using the term aggregation 
>> nested condition to search the top IP address count used by each users.
>> My condition is like that in my data i have users and each user 
>> performing n number of activities using more then one IP's.
>>
>> So, my desired result would be like below
>> username   ip  (which is used more)  count (how many time that ip used)
>>
>> array{ 
>>"aggs" : {
>> "group_by_username" : {
>> "terms":{
>> "field" : "username"
>> },
>> "aggs":{
>> "src_ip":{
>> "terms":{
>> "field":"src_ip"
>> }
>> }
>> }
>> }
>> },
>> "size":0
>> }
>>
>> But didn't get the desired result. Can anyone help me out?
>>
>> -- 
>> 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 elasticsearc...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/elasticsearch/da705866-99d5-41d9-8e28-76298bb0645a%40googlegroups.com
>>  
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> -- 
> Adrien Grand
>  

-- 
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 
https://groups.google.com/d/msgid/elasticsearch/7407fa4f-4b29-44cf-8cfa-0b2b44a52171%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Upgrading ES from 1.0.3

[Dunaeth]

Hi,

I can't find informations related to query / features syntax updates 
between old ES versions and more recent ones. Since we're using search and 
percolator queries, I want to be sure we won't have any bad surprise after 
upgrade. Are there any informations on this subject ?

-- 
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 
https://groups.google.com/d/msgid/elasticsearch/20bed21b-d354-43ec-88d6-cbb91c3c2f3f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: What does the "aggs" field in my index settings represent.

[Adrien Grand]

"aggs" makes no sense in the context of index settings, it looks to me like
someone mistakenly submitted a search request with aggregations to the
update settings endpoint instead of the search endpoint.

On Mon, Dec 1, 2014 at 8:08 AM, Anil Karaka  wrote:

> {
>
>- test_index:
>{
>   - settings:
>   {
>  - index:
>  {
> - creation_date: "1416836998944",
> - warmer:
> {
>- enabled: "false"
>},
> - uuid: "R2eL4uvvQbGtLKAaDPrmaQ",
> - number_of_replicas: "1",
> - aggs:
> {
>- group_by_age:
>{
>   - aggs:
>   {
>  - group_by_gender:
>  {
> - aggs:
> {
>- average_balance:
>{
>   - avg:
>   {
>  - field: "balance"
>  }
>   }
>},
> - terms:
> {
>- field: "gender",
>- order:
>{
>   - average_balance: "desc"
>   }
>}
> }
>  },
>   - range:
>   {
>  - field: "age",
>  - ranges:
>  [
> -
> {
>- to: "29",
>- from: "20"
>},
> -
> {
>- to: "39",
>- from: "30"
>},
> -
> {
>- to: "49",
>- from: "40"
>}
> ]
>  }
>   }
>},
> - number_of_shards: "5",
> - refresh_interval: "5s",
> - version:
> {
>- created: "1040099"
>},
> - size: "0"
> }
>  }
>   }
>
> }
>
> I'm a little confused by "aggs" in my index settings, what does it mean?
> Is it related to index warmers, or index aliases..?
>
> Thank you.
>
> --
> 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
> https://groups.google.com/d/msgid/elasticsearch/1c5dbc63-9d1a-434f-b0b9-0311b2efa21a%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Adrien Grand

-- 
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 
https://groups.google.com/d/msgid/elasticsearch/CAL6Z4j6Mcejo%3DLSU4er4H1rLq8b3uhnr8NqbTiMBBhCFcGn1RA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Unassigned Shards Of A Newer Elasticsearh Version

[David Pilato]

Are you sure you are not running low on disk space?

If you have less than 15% free, elasticsearch won’t allocate replicas.



-- 
David Pilato | Technical Advocate | Elasticsearch.com
@dadoonet  | @elasticsearchfr 
 | @scrutmydocs 




> Le 1 déc. 2014 à 09:21, Umutcan  a écrit :
> 
> Hi,
> 
> When I was doing some experiments on my Elasticsearch cluster, I found that 
> cluster cannot assign replicas of a shards on the node which have a new 
> version of Elasticsearch (1.4.1). I have seen this before and I can fix this 
> by upgrading old nodes. But, I am wondering that if there is a way to fix 
> this issue without upgrade.
> 
> Is there any idea or a solution?
> 
> Thanks,
> 
> Umutcan
> 
> PS: Other nodes in the cluster have Elasticsearch 1.4.
> 
> -- 
> 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 
> https://groups.google.com/d/msgid/elasticsearch/547C251B.9060809%40gamegos.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
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 
https://groups.google.com/d/msgid/elasticsearch/C12508F1-79F2-4346-B6C0-3F020CE7E567%40pilato.fr.
For more options, visit https://groups.google.com/d/optout.

Unassigned Shards Of A Newer Elasticsearh Version

[Umutcan]

Hi,

When I was doing some experiments on my Elasticsearch cluster, I found 
that cluster cannot assign replicas of a shards on the node which have a 
new version of Elasticsearch (1.4.1). I have seen this before and I can 
fix this by upgrading old nodes. But, I am wondering that if there is a 
way to fix this issue without upgrade.


Is there any idea or a solution?

Thanks,

Umutcan

PS: Other nodes in the cluster have Elasticsearch 1.4.

--
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 
https://groups.google.com/d/msgid/elasticsearch/547C251B.9060809%40gamegos.com.
For more options, visit https://groups.google.com/d/optout.