Java API : Transport client not complaining when no cluster is on
Hi, Can anyone tell me why my Elasticsearch Transport Client does not complain when not finding a cluster ? Code here : https://github.com/YannBrrd/json-import/blob/master/src/main/java/org/yaba/curbside/ESInjector.java#L92 Thanks. Regards, 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 to elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/c8919e59-dd62-45a1-a7f0-2b39f1beebd5%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Not part of cluster
Hi, Do we have an option to be notified if we are not connected to a cluster ? Thanks. Le vendredi 14 octobre 2011 14:09:04 UTC+2, kimchy a écrit : When happens is that you use the TransportClient, and connect to a node that does not have the same cluster name as the TransportClient. You need to make sure to configure the transport client with the correct set of nodes. I guess it make sense to be able to register a callback to be notified that the listed node is not part of the cluster, or something similar, open an issue. On Thu, Oct 13, 2011 at 12:05 PM, dominik symonowicz dmsp...@gmail.comjavascript: wrote: Hello folks. So i have problem i see warning... WARNING: [Johnny Ohm] Node [Smuggler II][4rNtWrqJSLKKkOB0uhXntg] [inet[/10.0.5.69:9300]] not part of the cluster Cluster [dom], ignoring... 13-Oct-2011 10:57:27 org.elasticsearch.common.logging.slf4j.Slf4jESLogger internalWarn which appear endlessly which means somebody screw up settings which what can happen and it is expected ,but i want handle that by throw exception .Yes,i want... if somebody mess name of cluster ,then i want put to logic to handle that .. (for example switch off server , send email to Mr. Kimchy with complain that finding useful docs about elasticsearch is like looking for needle in the hay in dark room -- 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/c59a34c4-f1e5-4df7-9e4e-7b5503bf16c0%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Java API : Transport client not complaining when no cluster is on
Yes. In the end Shay told me to use conectedNodes from the client API. Code avalable at github https://github.com/YannBrrd/json-import/blob/master/src/main/java/org/yaba/curbside/ESInjector.java#L95 Cordialement, Yann Barraud 2013/12/30 joergpra...@gmail.com joergpra...@gmail.com Is it the same with client.transport.sniff set to false? Jörg -- You received this message because you are subscribed to a topic in the Google Groups elasticsearch group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/elasticsearch/2jLq6iuS3po/unsubscribe. To unsubscribe from this group and all its topics, send an email to elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAKdsXoHPdeR26En8qimLj%2BEdRQS8mTPwi0X-AGrswskUOS1SDA%40mail.gmail.com . For more options, visit https://groups.google.com/groups/opt_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 elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CA%2BhvuXd%3DmC5d%2BOQG0Bu_7vri%2BLL%2BztQG3Zr%3DRyrmP%2B6U94iXNA%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Not part of cluster
Hi, I also opened an issue after talking to Shay https://github.com/elasticsearch/elasticsearch/issues/4569 Cordialement, Yann Barraud 2013/12/30 joergpra...@gmail.com joergpra...@gmail.com After client.addTransportAddress(...), you can check if client.connectedNodes() is not null and is not empty, then TransportClient is connected. Jörg -- You received this message because you are subscribed to a topic in the Google Groups elasticsearch group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/elasticsearch/br8ZXUGni20/unsubscribe. To unsubscribe from this group and all its topics, send an email to elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAKdsXoEHuXKJ2QTaHZgEGASw3PTOi3u2XzLDG_6AWO1j_vV-2g%40mail.gmail.com . For more options, visit https://groups.google.com/groups/opt_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 elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CA%2BhvuXcuXNZh4P50y8MT9xFrCv6VL9Ju3NR3bRHw1rLodqRr5g%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
Non Alphanumeric character searching
#%##%#%#$%#%#$%#$ my data contain this string.
I am firing this query, but not able to search the data. any clues why it
is not searching? if I put abc in between #%##%#%#abc$%#%#$%#$ and fire the
same query which this query string it find out the result for me.
{
from : 0,
size : 3,
query : {
filtered : {
query : {
bool : {
should : {
query_string : {
query : \#%##%#%#$%#%#$%#$\,
default_field : DATA
}
}
}
},
filter : {
range : {
timestamp : {
from : 0,
to : 1388412035468,
include_lower : true,
include_upper : true
}
}
}
}
}
}
--
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/b13816bb-e08b-4627-a517-dce0f90ca581%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
query_string queries don't handle multiple types
Hello everyone,
I'm trying to implement a search for one of my indices using the following
query:
{
query : {
query_string : {
query : some text,
fields : [collected.*]
}
}
}
The documents in the index have a field named collected which is dynamic
and changes between documents.
When I try to run this query I get NumberFormatException since some of the
fields are Numeric and I guess elasticsearch tries to cast the input string
to a number.
Is there any possibility to make the query_string parameter perform a 'best
effort' search without raising that exception so that it will ignore the
fields that he can't cast,
Thanks,
Yarin
--
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/d4492b49-b299-4eae-92a7-07026e19be66%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: Finding duplicate documents or its count based on some field names
More Like This could work, especially if using non-analyzed fields: http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/search-more-like-this.html -- Ivan On Sat, Dec 28, 2013 at 5:14 AM, joergpra...@gmail.com joergpra...@gmail.com wrote: If you can use 1.0.0.Beta2, aggregations might be a solution. Demo: https://gist.github.com/jprante/8159379 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/CAKdsXoGExLpeiBcMxcemFDo9oqOLjCj9zq4Db8_mNrp8n%2BV3-w%40mail.gmail.com . For more options, visit https://groups.google.com/groups/opt_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 elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CALY%3DcQAmk5sUPgDd_1eA_pF%2BU%2B0ud0C9n4xVgsmHZmjvFM__gg%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
default-mapping.json on Centos ?
I have a default-mapping.json file working fine in Ubuntu by placing it in /usr/local/elasticsearch/config/. I also have Centos install of ES, but I can't figure out where to put the default-mapping.json file. I have tried /usr/share/elasticsearch/config/ and /etc/elasticsearch/config/. Neither cause the mapping to take affect. Could have something to do with naming the cluster something other than elasticsearch? There is no /usr/local/elasticsearch/ on the Centos system. 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/e67cd23f-7849-4db6-a16f-19b9a477fb8a%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Problem transitioning from S3 to EBS
Steinar Bang s...@dod.no:
[snip! Attempted transitioning from S3 to local gateway on EBS]
Unfortunately ES came up again, but without any indices. Should this
have worked? Or will it fail, because if things I don't understand
about how gateways work?
I googled a bit, and came up with the gateway.local.auto_import_dangled
setting, which I tried setting to yes, and restarting ES. But still no
luck, it finds the two indexes, but it's unable to load them since it
doesn't find the metadata:
[2013-12-30 17:19:08,305][INFO ][node ] [Tefral the
Surveyor] stopping ...
[2013-12-30 17:19:08,384][INFO ][node ] [Tefral the
Surveyor] stopped
[2013-12-30 17:19:08,385][INFO ][node ] [Tefral the
Surveyor] closing ...
[2013-12-30 17:19:08,401][INFO ][node ] [Tefral the
Surveyor] closed
[2013-12-30 17:19:10,714][INFO ][node ] [Senor Muerte]
version[0.90.7], pid[1699], build[36897d0/2013-11-13T12:06:54Z]
[2013-12-30 17:19:10,714][INFO ][node ] [Senor Muerte]
initializing ...
[2013-12-30 17:19:10,738][INFO ][plugins ] [Senor Muerte]
loaded [river-datagen, cloud-aws], sites [head]
[2013-12-30 17:19:13,211][DEBUG][discovery.zen.ping.multicast] [Senor Muerte]
using group [224.2.2.4], with port [54328], ttl [3], and address [null]
[2013-12-30 17:19:13,216][DEBUG][discovery.zen.ping.unicast] [Senor Muerte]
using initial hosts [], with concurrent_connects [10]
[2013-12-30 17:19:13,218][DEBUG][discovery.ec2] [Senor Muerte]
using ping.timeout [3s], master_election.filter_client [true],
master_election.filter_data [false]
[2013-12-30 17:19:13,219][DEBUG][discovery.zen.elect ] [Senor Muerte]
using minimum_master_nodes [-1]
[2013-12-30 17:19:13,220][DEBUG][discovery.zen.fd ] [Senor Muerte]
[master] uses ping_interval [1s], ping_timeout [30s], ping_retries [3]
[2013-12-30 17:19:13,226][DEBUG][discovery.zen.fd ] [Senor Muerte]
[node ] uses ping_interval [1s], ping_timeout [30s], ping_retries [3]
[2013-12-30 17:19:13,838][DEBUG][discovery.ec2] [Senor Muerte]
using host_type [PRIVATE_IP], tags [{}], groups [[]] with any_group [true],
availability_zones [[]]
[2013-12-30 17:19:15,177][DEBUG][gateway.local] [Senor Muerte]
using initial_shards [quorum], list_timeout [30s]
[2013-12-30 17:19:15,563][DEBUG][gateway.local.state.meta ] [Senor Muerte]
using gateway.local.auto_import_dangled [YES], with
gateway.local.dangling_timeout [2h]
[2013-12-30 17:19:15,578][DEBUG][gateway.local.state.meta ] [Senor Muerte]
[_river] failed to find metadata for existing index location
[2013-12-30 17:19:15,578][DEBUG][gateway.local.state.meta ] [Senor Muerte]
[my_index] failed to find metadata for existing index location
[2013-12-30 17:19:15,578][DEBUG][gateway.local.state.meta ] [Senor Muerte] took
14ms to load state
[2013-12-30 17:19:15,580][DEBUG][gateway.local.state.shards] [Senor Muerte]
took 1ms to load started shards state
[2013-12-30 17:19:15,606][INFO ][node ] [Senor Muerte]
initialized
[2013-12-30 17:19:15,606][INFO ][node ] [Senor Muerte]
starting ...
[2013-12-30 17:19:15,751][INFO ][transport] [Senor Muerte]
bound_address {inet[/0:0:0:0:0:0:0:0:9300]}, publish_address
{inet[/172.31.31.127:9300]}
[2013-12-30 17:19:15,757][TRACE][discovery] [Senor Muerte]
waiting for 30s for the initial state to be set by the discovery
[2013-12-30 17:19:16,661][TRACE][discovery.ec2] [Senor Muerte]
building dynamic unicast discovery nodes...
[2013-12-30 17:19:16,661][DEBUG][discovery.ec2] [Senor Muerte]
using dynamic discovery nodes []
[2013-12-30 17:19:18,334][TRACE][discovery.ec2] [Senor Muerte]
building dynamic unicast discovery nodes...
[2013-12-30 17:19:18,334][DEBUG][discovery.ec2] [Senor Muerte]
using dynamic discovery nodes []
[2013-12-30 17:19:20,002][TRACE][discovery.ec2] [Senor Muerte]
building dynamic unicast discovery nodes...
[2013-12-30 17:19:20,002][DEBUG][discovery.ec2] [Senor Muerte]
using dynamic discovery nodes []
[2013-12-30 17:19:20,003][TRACE][discovery.ec2] [Senor Muerte] full
ping responses: {none}
[2013-12-30 17:19:20,003][DEBUG][discovery.ec2] [Senor Muerte]
filtered ping responses: (filter_client[true], filter_data[false]) {none}
[2013-12-30 17:19:20,011][INFO ][cluster.service ] [Senor Muerte]
new_master [Senor Muerte][66JvcflfSBKhkS-eUoJNzg][inet[/172.31.31.127:9300]],
reason: zen-disco-join (elected_as_master)
[2013-12-30 17:19:20,058][TRACE][discovery] [Senor Muerte]
initial state set from discovery
[2013-12-30 17:19:20,058][INFO ][discovery] [Senor Muerte]
csisearch-cluster/66JvcflfSBKhkS-eUoJNzg
[2013-12-30 17:19:20,066][DEBUG][gateway.local.state.meta ] [Senor Muerte]
[_river] failed to find
Re: how does facets work
After reading your scenario again, I have modified slightly my suggestion. You would still need to use a post filter since the facets need to work on set of documents that is greater than the set returned. You can apply the same post filter as a facet filter on the facet you want to reduce. Here is an example: https://gist.github.com/brusic/8185134 -- Ivan On Mon, Dec 30, 2013 at 7:57 AM, Volker s...@klest.de wrote: Hopefully this makes sense. :) after reading through your provided links... not totally ;-) If I apply the selected facet before the the facet calculation, the facet will count only elements, that are part of the result. That would mean, that I would not get numbers for the not selected models (in this case no numbers for bmw and ford). If I apply the selected facet as a post_filter, I will get the correct numbers for the unselected models, but the facets for the color does not represent the numbers for the selected model, but for all models. But probably I have not understood it, as it was meant. :-) Could you please elaborate further, how the query/filter for a selected facet should be formulated? I have not found any example for this. If there is one online, I would appreciate a link to that example. Kind regards Am Freitag, 27. Dezember 2013 18:58:13 UTC+1 schrieb Ivan Brusic: Facets work on the documents returned by the query. This behavior will not work in your case since you would like to gather facets on a greater set of documents, not just the ones returned by the query. To solve this issue, elasticsearch provides a post filter, which affects the result document set, but not the set of documents that the facets work on. The term filter is a bit overloaded in elasticsearch, so the team renamed the post filter to a more explicit post_filter: http://www.elasticsearch.org/guide/en/elasticsearch/ reference/current/search-request-post-filter.html https://github.com/elasticsearch/elasticsearch/issues/4119 The post filter documentation has some insight on how the filters affect the facets. In your case, you want a filtered query ( http://www.elasticsearch.org/guide/en/elasticsearch/ reference/current/query-dsl-filtered-query.html ) with the color as the filter, but the model filter will be applied as a post filter. Hopefully this makes sense. :) Cheers, Ivan On Fri, Dec 27, 2013 at 9:41 AM, Volker s...@klest.de wrote: Dear Readers I have a question about facets and doing some filtering based on facets. In the moment I am using hibernate search in combination with bobobrowse for facetting and I am thinking about switching to ES. But before that I would like to check whether I can still get the same functionality. lets asume that I have an index about cars and some facets -- eg. model and color. color [ ] red (10) [ ] blue (5) [ ] green (2) model [ ] bmw (4) [ ] vw (5) [ ] ford (8) if I select a model I would like to get only color facets for that model, but I still would like to get facets for all models. eg: color [ ] red (2) [ ] blue (2) [ ] green (1) model [ ] bmw (4) [x] vw (5) [ ] ford (8) I have searched I did not find an example about this usecase. Is this possible and if yes, how do I filter a query to get these results? Kind regards -- 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/9d1f3008-aff2-4936-8e6c-7611734e7418% 40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_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 elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/2609a3ee-1124-4bc1-95e6-c6e7cdb06128%40googlegroups.com . For more options, visit https://groups.google.com/groups/opt_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 elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CALY%3DcQC1i0wUL2gMVEt37PdZLNZXyTi7PTNGKUzDedR6Gpx-5w%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Problem transitioning from S3 to EBS
Is this a way that could be used, perhaps? http://tech.superhappykittymeow.com/?p=296 Ie. 1. Put the S3 stuff back into /etc/elasticsearch/elasticsearch.yml 2. Restart ES, and hopefully it will find the stuff it needs in S3 and come up with the two indexes 3. Use the curl/sed commands in the above URL to extract metadata from port 9200 4. Remove the S3 stuff from /etc/elasticsearch/elasticsearch.yml 5. Restart ES, and it again will be unable to load the indexes, because of the missing metadata 6. Use curl to PUT the saved metadata into port 9200 I think I will try this. Worst case is that I scrap the indexes on disk, and build up new indexes from S3. (And an even worse case is that I will have to refeed the data, but even that is no tragedy) -- 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/874n5qdyoi.fsf%40dod.no. For more options, visit https://groups.google.com/groups/opt_out.
Re: how does facets work
Dear Ivan thank you very much for your fast and helpful response. I will create some demo data and play with your snippet. I really appreciate your help! btw... I think my scenario is a very standard scenario for working with facets -- e.g. every online shop is working in this fashion with facets. kind regards Volker Am Montag, 30. Dezember 2013 18:36:31 UTC+1 schrieb Ivan Brusic: After reading your scenario again, I have modified slightly my suggestion. You would still need to use a post filter since the facets need to work on set of documents that is greater than the set returned. You can apply the same post filter as a facet filter on the facet you want to reduce. Here is an example: https://gist.github.com/brusic/8185134 -- Ivan -- 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/18a41661-021b-4833-86f1-423223da7a20%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Reports and Notifications.
Is there a way to install Logsene on premises, looking for something opensource (no budget at this time)? On Thu, Dec 26, 2013 at 11:42 AM, Otis Gospodnetic otis.gospodne...@gmail.com wrote: Aha, alerts. We have that in SPM (does performance monitoring, so alerts on your performance metrics) and will be adding it to Logsene (log analytics, like how people typically use Splunk). Feel free to email directly if you have any questions. Otis -- Performance Monitoring * Log Analytics * Search Analytics Solr Elasticsearch Support * http://sematext.com/ On Tuesday, December 24, 2013 11:12:19 PM UTC-5, CP wrote: In splunk there is the ability to create a report or notification if a certain threshold/event/trigger is captured. Then a script or report is triggered/sent. We are looking for simuliar functionality. I will check out what you sent. On Dec 24, 2013 7:31 PM, Otis Gospodnetic otis.gos...@gmail.com wrote: Hi, Could you please describe what you mean by reports? Are you looking for daily/weekly email with graphs or something else? We have that in SPM (monitoring) and Logsene (log analytics) is getting it, too. Kibana has this as well via phantomjs, I believe, though I'm not sure how/if it's hooked up to email. Otis -- Performance Monitoring * Log Analytics * Search Analytics Solr Elasticsearch Support * http://sematext.com/ On Tuesday, December 24, 2013 2:53:22 PM UTC-5, CP wrote: We have a HUGE splunk install and constantly are running into our limits. We have decided to go with a tiered solution using kibana+logstash+elasticsearch. The one thing that we really need is a way to have reports generated like we can with splunk. Does anyone know if there is a plugin or third party app to do this sort of thing? Thanks, CP -- You received this message because you are subscribed to a topic in the Google Groups elasticsearch group. To unsubscribe from this topic, visit https://groups.google.com/d/ topic/elasticsearch/CrmmeHqa-HY/unsubscribe. To unsubscribe from this group and all its topics, send an email to elasticsearc...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/ msgid/elasticsearch/4b231a64-52b4-4c23-b87c-bd3680ac44ac% 40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to a topic in the Google Groups elasticsearch group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/elasticsearch/CrmmeHqa-HY/unsubscribe. To unsubscribe from this group and all its topics, send an email to elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/dbf1ff5d-059c-418a-8b00-82368193d0cb%40googlegroups.com . For more options, visit https://groups.google.com/groups/opt_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 elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CANVfK9LO%2Bga_XX75Gi1CXkvF5giOjsF8t-Ly7VXXuXux%3D5oxGg%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Problem transitioning from S3 to EBS
Steinar Bang s...@dod.no: Is this a way that could be used, perhaps? http://tech.superhappykittymeow.com/?p=296 I tried, but no luck, I'm afraid. Ie. 1. Put the S3 stuff back into /etc/elasticsearch/elasticsearch.yml 2. Restart ES, and hopefully it will find the stuff it needs in S3 and come up with the two indexes 3. Use the curl/sed commands in the above URL to extract metadata from port 9200 4. Remove the S3 stuff from /etc/elasticsearch/elasticsearch.yml 5. Restart ES, and it again will be unable to load the indexes, because of the missing metadata 6. Use curl to PUT the saved metadata into port 9200 At this stage I had the metadata for the indexes in place, but no documents in either index. Then I took a restart of ES, and it came up with the two indexes empty still, and the old data om /data/elasticsearch removed. -- 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/87zjnichtg.fsf%40dod.no. For more options, visit https://groups.google.com/groups/opt_out.
Re: Problem transitioning from S3 to EBS
One thing I could try, is snapshot to volatile storage, scrap the index and restore from volatile storage. http://www.elasticsearch.org/guide/en/elasticsearch/reference/master/modules-snapshots.html Is that viable, with a 25.5GB index on an EC2 instance? -- 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/87vby6chbw.fsf%40dod.no. For more options, visit https://groups.google.com/groups/opt_out.
Re: Problem transitioning from S3 to EBS
Steinar Bang s...@dod.no: Steinar Bang s...@dod.no: One thing I could try, is snapshot to volatile storage, scrap the index and restore from volatile storage. http://www.elasticsearch.org/guide/en/elasticsearch/reference/master/modules-snapshots.html Trying to set up the backup repository according to the above document, fails: [snip!] Do I need to enable the backup/restore module in some way? Nope, looks like I would need 1.0.0-beta2, rather than the 0.9.7 I have currently installed: http://www.elasticsearch.org/blog/1-0-0-beta2-released/ -- 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/87mwjicfeh.fsf%40dod.no. For more options, visit https://groups.google.com/groups/opt_out.
Re: message: [WARN ][cluster.service ] [node1] failed to reconnect to node [node1][I4Wltlc9RSm0jJhumBRtpQ][inet[/10.10.10.1:9300]]
Is/was there another elasticsearch node no the network? If you will only have 1 node, you can disable mutlicast discovery. -- Ivan On Mon, Dec 30, 2013 at 3:33 AM, HansPeterSloot hanspeter.sl...@gmail.comwrote: Hi, I have a 1 node elasticsearch cluster which seems to run fine. But I see the following messages in the logfile: [2013-12-30 12:17:35,905][WARN ][cluster.service ] [node1] failed to reconnect to node [node1][I4Wltlc9RSm0jJhumBRtpQ][inet[/10.10.10.1:9300 ]] org.elasticsearch.transport.ConnectTransportException: [node1][inet[/ 10.10.10.1:9300]] connect_timeout[30s] What can I do to get rid of it? Regards HansP -- 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/3f9fe20f-6fed-475d-88f3-7441d01ff816%40googlegroups.com . For more options, visit https://groups.google.com/groups/opt_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 elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CALY%3DcQDwKkiCA%2BZ5uWv1Kk_BUXpHUVs3UUDr8WLc_perNN%3DGww%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
upgrade elasticsearch using the service wrapper?
Hi, Does anyone know how to upgrade elasticsearch by using the service wrapper? https://github.com/elasticsearch/elasticsearch-servicewrapper I tried googling around and did not find anything documented. Thanks, Allen Chan -- 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/2b7a350b-7f62-4c5e-b51b-ab60bb645a15%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Problem transitioning from S3 to EBS
Steinar Bang s...@dod.no: Nope, looks like I would need 1.0.0-beta2, rather than the 0.9.7 I have currently installed: http://www.elasticsearch.org/blog/1-0-0-beta2-released/ I'm now up and running on EBS storage on ES 1.0.0-beta2, after having first created a snapshot with volatile storage+S3 gateway, then switched to EBS storage and no S3 gateway, and restored the snapshot. The restored index seems to be identical to the original index, with all of the tests I've been able to apply to it. Thanks for the snapshot/restore facility! Good work! :-) -- 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/87iou6cb40.fsf%40dod.no. For more options, visit https://groups.google.com/groups/opt_out.
Re: Possible to make ES Node Name same as Hostname?
You can just download the tar.gz, unpack it, and start ES with ./bin/elasticsearch -Des.node.name=... or set ES_JAVA_OPTS to - Des.node.name=..., in any startup script you prefer. There is no need to build from source. ES behaves just like any Java app I know of that uses Java system properties, for example, JBoss or Tomcat. Since interpreting Java system properties have no relationship with System V or systemd, I'm not sure how I can follow you. FWIW I use ES on RHEL with the service wrapper https://github.com/elasticsearch/elasticsearch-servicewrapper by just adding a symlink in the /etc/init.d folder. 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/CAKdsXoH_QE8_GYBjTbGSZUXrr56Cqb7%3DVhz%3DySYudOQyTgyG9g%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: upgrade elasticsearch using the service wrapper?
That is pretty straightforward, copy the service wrapper into the bin folder of the new ES version, adjust paths and symlinks, and there you are. Stopping and starting the cluster and migrating the index data is no difference to not using the service wrapper. 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/CAKdsXoEsGf%2BQKx-bm1sGoXX_O-Nfu_i2O4v%3DH9yiQcJYEg1B5Q%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: upgrade elasticsearch using the service wrapper?
i never did an upgrade before. Are there instructions for migrating the index data? On Mon, Dec 30, 2013 at 1:35 PM, joergpra...@gmail.com joergpra...@gmail.com wrote: That is pretty straightforward, copy the service wrapper into the bin folder of the new ES version, adjust paths and symlinks, and there you are. Stopping and starting the cluster and migrating the index data is no difference to not using the service wrapper. 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/CAKdsXoEsGf%2BQKx-bm1sGoXX_O-Nfu_i2O4v%3DH9yiQcJYEg1B5Q%40mail.gmail.com . For more options, visit https://groups.google.com/groups/opt_out. -- Allen Michael Chan -- 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/CAPTHB%2BDu%3D8JtMg%3DsVmcD_ovzVvVGVV_cJGr-bo-xb-%3D6suUzAQ%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
Plain filter and constant_score
Hi,
We are currently benchmarking our ES setup so I've got some new questions:
1. We found out that, for the same query (filter actually), when put like
this:
{
filter: {...},
fields: [...]
}
is consistently slower than this form:
{
query: {
constant_score: {
filter: {...},
...
}
}
}.
All filter and fields part are identical, but the performance is different,
especially when caches are warm, filters wrapped in a constant_score are
nearly 10x faster than when they are put directly.
So what happens behind this? How ElasticSearch interpret filters that are
put directly (not wrapped in any outer structure)?
Thanks in advance.
--
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/ad91095f-7e7b-4def-8570-73dbccaa7cb2%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: Plain filter and constant_score
The outer filter is basically a post filter, ie. filtering happens after
all the documents have been collected via the query. This should not
really be used unless you are trying to do something like multi-select
faceting where you don't want facet counts to be affected by the filter.
You should be using a filtered query [1] or as you discovered a constant
score query if you only want to execute a filter.
BTW, in elasticsearch 1.0, this outer filter has been renamed to
post_filter to avoid some of the confusion.
Thanks,
Matt Weber
On Mon, Dec 30, 2013 at 2:53 PM, Han JU ju.han.fe...@gmail.com wrote:
Hi,
We are currently benchmarking our ES setup so I've got some new questions:
1. We found out that, for the same query (filter actually), when put like
this:
{
filter: {...},
fields: [...]
}
is consistently slower than this form:
{
query: {
constant_score: {
filter: {...},
...
}
}
}.
All filter and fields part are identical, but the performance is
different, especially when caches are warm, filters wrapped in a
constant_score are nearly 10x faster than when they are put directly.
So what happens behind this? How ElasticSearch interpret filters that are
put directly (not wrapped in any outer structure)?
Thanks in advance.
--
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/ad91095f-7e7b-4def-8570-73dbccaa7cb2%40googlegroups.com
.
For more options, visit https://groups.google.com/groups/opt_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 elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/CAJ3KEoBhOub8U5zc_DzsecE4LrsxF40PUBaDCvnwX%3DWrO4f50w%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: upgrade elasticsearch using the service wrapper?
I missed the part about placing the data directory outside of the elasticsearch installation. To correct it, will it be as simple as doing a mv command to move all the files to new dir and modify the elasticsearch config to use new dir? On Mon, Dec 30, 2013 at 2:48 PM, Ivan Brusic i...@brusic.com wrote: There should be no need to migrate the index data unless you are moving between two major Lucene versions. Since elasticsearch has never used Lucene 2, the old indices should be readable. Best practices dictate that you place your data directory outside of the elasticsearch installation so that you can maintain the same directory between installations. -- Ivan On Mon, Dec 30, 2013 at 2:39 PM, allen chan allen.michael.c...@gmail.comwrote: i never did an upgrade before. Are there instructions for migrating the index data? On Mon, Dec 30, 2013 at 1:35 PM, joergpra...@gmail.com joergpra...@gmail.com wrote: That is pretty straightforward, copy the service wrapper into the bin folder of the new ES version, adjust paths and symlinks, and there you are. Stopping and starting the cluster and migrating the index data is no difference to not using the service wrapper. 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/CAKdsXoEsGf%2BQKx-bm1sGoXX_O-Nfu_i2O4v%3DH9yiQcJYEg1B5Q%40mail.gmail.com . For more options, visit https://groups.google.com/groups/opt_out. -- Allen Michael Chan -- 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/CAPTHB%2BDu%3D8JtMg%3DsVmcD_ovzVvVGVV_cJGr-bo-xb-%3D6suUzAQ%40mail.gmail.com . For more options, visit https://groups.google.com/groups/opt_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 elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CALY%3DcQBYv4OEWiyGQSODxRvX-EgisJ%2BNvLR%2BKx%3DV40hO6rBDFg%40mail.gmail.com . For more options, visit https://groups.google.com/groups/opt_out. -- Allen Michael Chan -- 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/CAPTHB%2BAiGNd9UPda8kEQBTTiT6yq0x6jZAyy8NwfAo%3Dj%3DDurHQ%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
