Re: Problem of ElasticSearch on ZFS

Hi we are running on Linux (ubuntu). The ZFS is set to standard (default). On Wednesday, January 1, 2014 12:43:35 AM UTC+8, Jörg Prante wrote: > > Do you run ZFS in sync mode? Are you on Solaris? > > Jörg > > -- You received this message because you are subscribed to the Google Groups "e

Re: Dumb Question on bouncing nodes

I do not think there is a way, but perhaps someone else can correct me. One potential way is to instead of disabling allocation, to set a timeout value high enough that the node can fully restart before the cluster drops the node. However, I am not sure if a node that is being cleanly shutdown will

Re: Feedback on docs

some of the API methods are interchangeable (more or less) to support different coding styles, so for example to index document, you can: - client.*prepareIndex*("test", "test").setSource(...).*get*() or - client.*prepareIndex*("test", "test").setSource(...).*execute*(). *actionGet*() or - client

Re: Dumb Question on bouncing nodes

Reading the description of that issue, I don't think they're the same. Looking at the code... Yeah, that's only about moving primaries around. So is there a way to restart a node without it going to zero shards and then back again? -- You received this message because you are subscribed to t

shard stucked in initializing state (elasticsearch crash test)

Hi, im doing crash test of small elasticsearch cluster): - 3 ubuntu micro instance (EC2, 3 zones) - 2 replicas (one per zone) - 10 indexes (with 10 shards per index) - 30k documents indexed in bulks (100 per batch) in parallel on every node - swap disabled im using micro instances to simulate a

Feedback on docs

Hi guys, I've recently gotten into Elasticsearch because the old search engine at my site http://ookaboo.com/ is horribly slow and I need something better. I've done a lot of work with Lucene and Solr in the past and particular I've been involved with projects that m

Re: Dumb Question on bouncing nodes

Unless I misread the post, your scenario seems to be the normal behavior. If you restart a node with allocation disabled, it will have no shards. Re-enabling allocation will force the shards on the node to be active. This behavior is at least what I have experienced. Perhaps there should be a setti

Re: Compared to Solr (with Solr Cloud), what is the advantage(s) of Elasticsearch?

We use both SOLR and Elasticsearch at Chegg. The search for www.chegg.com is powered by SOLR, because that's done by the search team, who are are more hard-core search nerds, like XML instead of JSON, etc. They have one master and a whole bunch of slaves, and rebuild the master continuously.

Re: Bulk throughput issues

I forgot to mention that the reason I went with multiple clients is that when doing some monitoring I was seeing a lot of blocked threads for org.elasticsearch.action.bulk.BulkProcessor.internalAdd(). Looking at the code this appears to be synchronized so my guess is we are just sending too muc

Dumb Question on bouncing nodes

Q: Is using the automatic node naming where every time I bounce a node I get a new node name interfering with restarting from the local gateway? Q Background: So previously, I asked about bouncing nodes, because it seems that whenever I bounce a node, it has to regenerate the node from the ot

Re: How to save Query JSON as it is in an Index?

I want to save the queries my users are executing and let them re-run at a later time. Thanks, On Tuesday, December 31, 2013 1:21:16 AM UTC-5, Daniel Guo wrote: > > I don't get your point, can you describe more detail? > > On Tuesday, December 31, 2013 8:23:22 AM UTC+8, Search User wrote: >> >>

Re: upgrade elasticsearch using the service wrapper?

There is no explicit documentation about where to place the data directory, but I find it best if you should keep as much as possible (configs/data/logs) from outside of the installation directory. I believe installing from a deb/rpm package might enforce a directory structure (never tried). The r

Re: upgrade elasticsearch using the service wrapper?

As for all updates, you should consider that if you are unable to use the new version for whatever reason, there is no guarantee that you can put the data back to the old version. So please consider a backup of your data, and do not forget to read the changelog / release notes of the new version h

Re: OR query

You are better of using a proper boolean filter for better performance. Queries cannot be cached and query string query analyzes the terms. Here is an example of your filter with a nested bool (should) filter: "filter": { "and": { "filters": [ { "bool": { "must": [

Re: Bulk throughput issues

Jason, you have to measure the docs at the indexing API with your client code. You can use the _cluster/stats or /_cluster/stats/nodes/{nodeId} endpoint to inspect the node caches (store, fielddata, filter_cache, id_cache, completion). The indexing buffer and the translog buffer state can not be i

Re: 16Gb RAM / 8 cores : best config ?

No easy answer, it depends on your OS and your requirements - indexing load, searching load, analytics ... you should start with ES default settings and heap size increased to 50% of RAM, that is 8G Jörg -- You received this message because you are subscribed to the Google Groups "elasticsearc

Re: Problem of ElasticSearch on ZFS

Do you run ZFS in sync mode? Are you on Solaris? 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

Re: Highlight values from one field in another field

Thanks for your reply. I have another question: Is it possible in highlight_query (I'm using version 0.90.9) to use few highlight tags? For example I want to highlight "text" field with for one sub query and with for another sub query? On Tuesday, December 31, 2013 4:42:20 PM UTC+2, Nikol

Re: Bulk throughput issues

Sorry for the delay, I had to take some unplanned leave and I wasn't able to get to this while I was out. With some more testing I was able to get ~10k documents a second but I had to make some code changes. 1: I changed to the transport client in our Java code 2: It seemed as if one client wasn

Re: Plain filter and constant_score

Thanks Matt. It seems that we've done terrible things ... effectively `post_filter` is a better name. 在 2013年12月31日星期二UTC+1上午12时16分43秒，Matt Weber写道： > > The "outer" filter is basically a post filter, ie. filtering happens after > all the documents have been collected via the query. This should

Re: Highlight values from one field in another field

You mean you want the terms highlighted in one field to come from the contents of another field rather than the query? If so, then Elasticsearch doesn't support that already but you could write a custom highlighter to do that. Nik On Tue, Dec 31, 2013 at 9:40 AM, mayap wrote: > Hi All, > > We

Highlight values from one field in another field

Hi All, We have multi value field - "name". We would like to highlight those values in anther field - "text". For example, for the values: "name" : ["name1", "name2", "name3", "name4"] "text" : "name1 is a friend of name2" we would like to get the result: highlight: { text : [name1 is a fr

Facet autocomplete for field with multiple values

Hi, I have problem finding solution for specific usage scenario where I want to autocomplete facet for field that has array of values. Documents in my index are some objects that can be owned by 0..n people, so I have field 'owner' containing zero to few strings of following format: first_n

Re: Elastic search range dates

Your query looks good. However, the way your hit is formatted in the results of the second query seems to indicate that your dates are indexed as strings instead of dates. How did you get your data from mongo to Elasticsearch? On Tue, Dec 31, 2013 at 11:42 AM, melasticsearch < melasticsea...@mail

Re: Finding duplicate documents or its count based on some field names

Hi, You can check this : http://github.com/yannbrrd/elasticsearch-entity-resolution Le samedi 28 décembre 2013 06:16:16 UTC+1, Narinder Kaur a écrit : > > Hi All, > > I need to know, if Elasticsearch has some feature to find the > duplicate documents or documents counts if I want to se

16Gb RAM / 8 cores : best config ?

Hi What would be the best cubic for ES running on a dedicated machine with 16 Gb of RAM & 8 cores ? Thanks, Yann -- 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

Re: message: [WARN ][cluster.service ] [node1] failed to reconnect to node [node1][I4Wltlc9RSm0jJhumBRtpQ][inet[/10.10.10.1:9300]]

Yes that worked. Thanks a lot. Op dinsdag 31 december 2013 12:12:43 UTC+1 schreef David Pilato: > > Sorry. Wrong answer. > > It sounds like you have 2 network cards on your computer: > > inet[/10.192.21.69:9200]}, publish_address {inet[/10.10.10.1:9200]} > > You should set network.host > > See:

Re: message: [WARN ][cluster.service ] [node1] failed to reconnect to node [node1][I4Wltlc9RSm0jJhumBRtpQ][inet[/10.10.10.1:9300]]

Well the 10.10.10.1 is just another nic on the same node. Op dinsdag 31 december 2013 12:11:04 UTC+1 schreef David Pilato: > > Thanks! > > > So you have your node running under IP: 10.192.21.69 > It's trying to access another node at 10.10.10.1 > > So may be you modify elasticsearch.yml file or y

Re: message: [WARN ][cluster.service ] [node1] failed to reconnect to node [node1][I4Wltlc9RSm0jJhumBRtpQ][inet[/10.10.10.1:9300]]

Sorry. Wrong answer. It sounds like you have 2 network cards on your computer: inet[/10.192.21.69:9200]}, publish_address {inet[/10.10.10.1:9200]} You should set network.host See:  http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/modules-network.html#tcp-settings --  David

Re: message: [WARN ][cluster.service ] [node1] failed to reconnect to node [node1][I4Wltlc9RSm0jJhumBRtpQ][inet[/10.10.10.1:9300]]

Thanks! So you have your node running under IP: 10.192.21.69 It's trying to access another node at 10.10.10.1 So may be you modify elasticsearch.yml file or you have another node running with a different version on your network. Could you run  curl http://10.10.10.1:9200/  ? --  David Pilat

Re: message: [WARN ][cluster.service ] [node1] failed to reconnect to node [node1][I4Wltlc9RSm0jJhumBRtpQ][inet[/10.10.10.1:9300]]

Sorry for the confusion. The file was so long I just thought that you only needed the error message. Can you access this one? nl19856 / *gist:8195337 * 2013/12/31 David Pilato > Sorry if I am unclear but I would like

Re: message: [WARN ][cluster.service ] [node1] failed to reconnect to node [node1][I4Wltlc9RSm0jJhumBRtpQ][inet[/10.10.10.1:9300]]

Sorry if I am unclear but I would like to see all the lines in your log file, from when you start the node to this issue. --  David Pilato | Technical Advocate | Elasticsearch.com @dadoonet | @elasticsearchfr Le 31 décembre 2013 at 11:59:25, HansPeterSloot (hanspeter.sl...@gmail.com) a écrit:

Re: message: [WARN ][cluster.service ] [node1] failed to reconnect to node [node1][I4Wltlc9RSm0jJhumBRtpQ][inet[/10.10.10.1:9300]]

Never did that. Is this what you need? nl19856 / *gist:8195274 * Op dinsdag 31 december 2013 11:41:05 UTC+1 schreef David Pilato: > > Could you GIST (gist.github.com) the full log file please? > > -- > *David Pilato* |

Re: Elastic search range dates

no one? -- View this message in context: http://elasticsearch-users.115913.n3.nabble.com/Elastic-search-range-dates-tp4046565p4046854.html Sent from the ElasticSearch Users mailing list archive at Nabble.com. -- You received this message because you are subscribed to the Google Groups "elast

Re: message: [WARN ][cluster.service ] [node1] failed to reconnect to node [node1][I4Wltlc9RSm0jJhumBRtpQ][inet[/10.10.10.1:9300]]

Could you GIST (gist.github.com) the full log file please? --  David Pilato | Technical Advocate | Elasticsearch.com @dadoonet | @elasticsearchfr Le 31 décembre 2013 at 10:41:32, HansPeterSloot (hanspeter.sl...@gmail.com) a écrit: There is really no other elasticsearch node in the network. I a

Re: message: [WARN ][cluster.service ] [node1] failed to reconnect to node [node1][I4Wltlc9RSm0jJhumBRtpQ][inet[/10.10.10.1:9300]]

There is really no other elasticsearch node in the network. I am sure about that. There is also only one daemon running: ps -ef|grep elast 101 1769 1 1 08:27 ?00:02:14 /usr/bin/java -Xms256m -Xmx1g -Xss256k -Djava.awt.headless=true -XX:+UseParNewGC -XX:+UseConcMarkSweepGC -X

Re: message: [WARN ][cluster.service ] [node1] failed to reconnect to node [node1][I4Wltlc9RSm0jJhumBRtpQ][inet[/10.10.10.1:9300]]

I agree with Ivan. You should have another running. Is 10.10.10.1 your IP address? Could you gist your full log? --  David Pilato | Technical Advocate | Elasticsearch.com @dadoonet | @elasticsearchfr Le 31 décembre 2013 at 09:38:26, HansPeterSloot (hanspeter.sl...@gmail.com) a écrit: It seems

Re: message: [WARN ][cluster.service ] [node1] failed to reconnect to node [node1][I4Wltlc9RSm0jJhumBRtpQ][inet[/10.10.10.1:9300]]

It seems that it is not enough. The message keeps appearing. Op dinsdag 31 december 2013 08:43:08 UTC+1 schreef HansPeterSloot: > > No there is only 1 node. > Is is sufficient to remove the # in the elasticsearch.yml before the > following entry: > discovery.zen.ping.multicast.enabled: false >