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
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
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
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
#%##%#%#$%#%#$%#$ 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,
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
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,
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/.
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
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 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
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
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
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
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
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
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
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
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
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,
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
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
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:
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
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
25 matches
Mail list logo
