There was nothing in the master logs. It’s like they were asleep.
From: Boaz Leskes b.les...@gmail.commailto:b.les...@gmail.com
Reply-To:
elasticsearch@googlegroups.commailto:elasticsearch@googlegroups.com
elasticsearch@googlegroups.commailto:elasticsearch@googlegroups.com
Date: Monday,
No, I use unicast discovery, not the Azure plugin.
From: Boaz Leskes b.les...@gmail.commailto:b.les...@gmail.com
Reply-To:
elasticsearch@googlegroups.commailto:elasticsearch@googlegroups.com
elasticsearch@googlegroups.commailto:elasticsearch@googlegroups.com
Date: Monday, November 10, 2014 at
Hello
I'm new to elasticsearch. I succeeded to run it on my Mac, but failed to
run on Linux (error is as below). Anyone knows why it failed and how to
solve it? Thanks
$ bin/elasticsearch
[2014-11-11 08:03:12,313][INFO ][node ] [Midnight Man]
version[1.4.0], pid[31913],
Hi,
I have a search request that uses a couple of filters. I'm using bool+must,
and I'm trying to optimize the request as much as possible.
- Some filters are used by all users of my platform, but aren't very
selective.
- Some filters are very specific to individual users, and are highly
Hello,
I'm currently thinking of creating VM nodes for the masters.
Today, several nodes have master and data node roles.
But I have OOM memory errors and so masters crashed frequently.
What would be the correct hardware sizing for a master node only (like 2
CPUs, 4GB RAM) for managing a
Hello,
On one of my ELS cluster, i have node with different hardware capacity.
1 node : 8 GB RAM and 200GB disk
1 node : 4 GB RAM and 20GB disk
2 node : 64GB RAM with 4To Disk
I find that ELS tries to balance the same amount of data on each node.
The 2 smaller node are near full (disks and cpu)
I'd suggest you go for 8GB system RAM with a small disk and then also use
these nodes as clients - ie query management.
You may need more RAM, but that should be a good start.
On 11 November 2014 19:35, lagarutte via elasticsearch
elasticsearch@googlegroups.com wrote:
Hello,
I'm currently
You can balance, to a degree, based on disk space, but not heap/system RAM.
There might be other options, like playing with shard allocation.
See
http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/index-modules-allocation.html
for some ideas.
On 11 November 2014 19:43,
I see. Do you mind sharing the logs somewhere of the nodes? (privately via
e-mail also possible). I'd love to understand what happend.
On Tue Nov 11 2014 at 9:01:39 AM Janet Sullivan jan...@nairial.net wrote:
No, I use unicast discovery, not the Azure plugin.
From: Boaz Leskes
If you want to translate battle-axe into battle axe, note that the
correct method would be to introduce a phrase search with slop 0. The and
operator may also work in most cases but the word positions will be lost,
you get an more unprecise search for docs that contain battle and axe
anywhere in
I now know that Marvel creates a lot of data per day of monitoring - in our
case around 1Gb.
What I'm just starting to get my head around is the imbalance of disk usage
that this caused on my 5 node cluster.
I've now removed Marvel and deleted the indexes for now (great tool, but I
don't have
I know from the FAST Search engine ten years ago there was a two-phase
commit for distributed search and indexing. One server could listen on the
API and keep the (compressed) input stored, and all the other indexing
servers were supplied by this input in another phase to create binary
indexes,
Hello Mark,
I am indexing through logstash in the following way:
output {
elasticsearch {
protocol = http
cluster = CLUSTER
}
}
The data is in json format and i am filtering the data as follows:
filter {
json {
source = message
}
}
Thank you for your
Hello to all!
Note: I'm new to ELK :)
I'm using elasticsearch 1.4.0 and I'm trying to enable http.cors feature
in elasticsearch. When I set http.cors.enabled: true and
http.cors.allow-origin: * in config file and then restart, the
http.cors feature doesn't enabled yet and I can't use kibana
Hi,
I'm considering using the warmer API for caching date range filters. Most
users will use last 30 days or last 7 days in their filters so it's a
good candidate for warming, at least with a boxed date range that only
changes once every day.
Is this possible to do with the warmer API? I'm
Hi David,
did you manage to fix your issue? I'm observing exactly the same symptoms
as you with one of my indices. Hardware seems to be OK.
Thanks
Christoph
Am Mittwoch, 3. September 2014 23:13:26 UTC+2 schrieb David Kleiner:
Another data point, replica shard that's trying to initialized
I think it's related to
this: https://github.com/elasticsearch/elasticsearch/pull/8270 which I
believe was released with 1.4.
We see the same thing, with hot spots on some nodes. You can poke the
cluster to rebalance itself, which that #8270 fixes permanently, using
curl -XPOST
Elasticsearch doesn't let you weight nodes for balance and the disk space
allocation decider really just puts soft limits on the amount of space
elasticsearch can take up per machine. There really isn't anything to do
it automatically.
You could use a combination of allocation awareness,
I have dedicated client nodes for some really intense queries and
aggregations. Clients typically have 2GB of heap. Our experience is that
2GB of Heap is sufficient, the client node doesn't do a whole lot. The bulk
of the work is done on the data nodes.
cheers
mike
On Monday, November 10,
Interesting - I thought I'd narrowed it down to Marvel. I had big
imbalances with Marvel running, now it all seems flat (although to be fair,
the disk usage has dropped to around 5Gb used in a 32Gb partition, so
there's large amounts of free space).
Same as you though - I could do nothing to
Hello
I'm trying to use Swedish stemming in elasticsearch and I keep getting
problem with it. I could need some advice about how to deal with this stuff.
The main problem is that the stemmers stems some words in a weird way which
makes my hits either go through the roof or not match at all.
At
Reza,
for me I had to set enabled to true and leave out the allow-origin as it
defaults to * anyways.
On Tuesday, November 11, 2014 6:21:05 AM UTC-6, Reza Samee wrote:
Hello to all!
Note: I'm new to ELK :)
I'm using elasticsearch 1.4.0 and I'm trying to enable http.cors feature
in
I believe it is not implemented yet
(https://github.com/elasticsearch/kibana/issues/1526). There are a number
of missing features that are scheduled on the roadmap plus a ton of bugs
still to be fixed. It really is a beta 1
Hi,
I need, for each document I index, to store the exact currency conversion
rates that apply when the document was index. My first naïve idea was to
index, along the documents, the list of all conversion rates relative to
the currency of the indexed document. However, I realize that it can
Hi,
I am using php elasticsearch client , almost very often I see this
exception
Elasticsearch\Common\Exceptions\Curl\CouldNotConnectToHost
Am I losing my data ?
Our server doesn't have high traffic . Its max 50 request per second in any
time.
Is there any default retry logic has
Hi @ All
First of all, Kibana 4 beta looks very nice, great work!
I'm trying to use the experimental groovy code scripting engine
What i try:
curl -XPOST 'http://localhost:9200/info/_search' -d '{
query: {
match_all : {}
},
aggs: {
result: {
Got the solution.
The Problem is that groovy code is implemented as a closure so you should
do it this way:
scripted_metric: {
init_script : {_agg - _agg['res'] = []},
map_script : {_agg - _agg.res.add(
doc['checkoutAmount'] ?: 0) }
}
--
You received this message
I suddenly remembered when using facets that I had to apply the same query
filter as a facet filter with the join option disabled. Turns out it is
somewhat identical with aggregations. My problem was that the scope of my
nested aggregation with not under the scope of the filter aggregation. I
hope
Hi all,
I'm getting some strange behavior from the ES server when using a term
query + a geo distance filter + a sort. I've tried this with 1.3.2,
1.3.5, as well as 1.4.0. All exhibit this same behavior. I'm using the
Java transport client. Here is my SearchRequestBuilder payload in
Quite the opposite: the Elasticsearch team and others have said that
authentication belongs outside of the application. Or at least, security
was not a high priority.
It seems like they are working on security and a release should be
forthcoming:
ok, thanks,so if i understand, the best is to have the same hardware
capacity for all the nodes involved in the cluster.
ELS need more polish with this, perhaps it will come later
Le mardi 11 novembre 2014 14:30:44 UTC+1, Nikolas Everett a écrit :
Elasticsearch doesn't let you weight nodes for
I am not aware of FAST but the idea looks promising.
However it might not be that easy to just have plugin for ES, as the data
itself is distributed on different machines.
So it will not be possible to have just one server with the data, as it
will become single point of failure.
regards and
Ok, since the master doesn't contain any data, and don't do lot ofs IOs:
For 8GB RAM, what's the recommended HEAP_SIZE ? 7GB
and i don't fully understand the client (query management node).
Today, i have set node.master=true and node.data=true.
and with new master only, i will have masters only
Hi Guys and Gals,
Sorry, I hope y'all will not consider this spam, but i have a job posting
to list (below).
This is a permanent position in Austin, TX offering great benefits, a laid
back atmosphere, and very competitive salary and equity. If you are
interested please feel free to contact
I just noticed I had a typo in my query, this is the query payload I'm
executing if I run it in HTTP (which works)
{
from : 0,
size : 10,
query : {
term : {
ug_context :
c2d2d78a-69cc-11e4-b22e-81db7b9aa660__user__zzzconnzzzlikes
}
},
The error says local checksum OK... what version of elasticsearch
are you running?
If its before 1.3.2, please read this:
http://www.elasticsearch.org/blog/elasticsearch-1-3-2-released/
On Wed, Sep 3, 2014 at 12:58 AM, David Kleiner david.klei...@gmail.com wrote:
Greetings,
I tried to
I'm running 1.3.1. Thanks a lot for the hint. I will try to upgrade and let
you know.
What is the recommended way of upgrading? One minor version at a time or
can I do a rolling upgrade to 1.3.5?
Thanks!
Christoph
Am Dienstag, 11. November 2014 19:38:55 UTC+1 schrieb Robert Muir:
The error
With existing Elastic Search I can think of an architecture like this.
Index : indexForDataDump : No mapping(Is it possible?) or minimum mapping.
Use only to dump data from external system. There is some primary key.
There are different search indexes with different mapping : search-index1,
Maybe the question to ask will be how do you determine which part of phrase
will be searched as case sensitive and which will be not.
If that logic is consistent it can be applied at indexing itself, and same
analyzer used for search.
regards and thanks
amish
On Monday, November 10, 2014
First, i would try the workaround mentioned in the article: disable
the compression and see if fixes the issue.
On Tue, Nov 11, 2014 at 1:42 PM, Christoph Tavan
christoph.ta...@gmail.com wrote:
I'm running 1.3.1. Thanks a lot for the hint. I will try to upgrade and let
you know.
What is the
Hi,
I implemented ES plugin and set its version in es-plugin.properties.
version=${project.version}
I build project using maven but when I start plugin in ES and check plugin
version using ES API I see version without resolved project.version
property. Do you have any idea how I can avoid
Change in pom.xml and add filtering.
https://github.com/elasticsearch/elasticsearch-analysis-icu/blob/master/pom.xml#L111
https://github.com/elasticsearch/elasticsearch-analysis-icu/blob/master/pom.xml#L111
--
David Pilato | Technical Advocate | Elasticsearch.com
@dadoonet
Thanks
On Tue, Nov 11, 2014 at 8:16 PM, David Pilato da...@pilato.fr wrote:
Change in pom.xml and add filtering.
https://github.com/elasticsearch/elasticsearch-analysis-icu/blob/master/pom.xml#L111
--
*David Pilato* | *Technical Advocate* | *Elasticsearch.com
http://Elasticsearch.com*
Looks like a bug in org.apache.usergrid.persistence.index.impl.
EsEntityIndexImpl
Check if the types are set to a non-null value in the SearchRequest. If
you force them to be a null value, SearchRequest will throw the NPE you
posted.
Jörg
On Tue, Nov 11, 2014 at 6:11 PM, Todd Nine
FAST stored the source data in distributed machines, only the control API
was not distributed (similar to ES HTTP curl requests, which also connect
to one host only).
Of course you could index raw JSON to a preparer index with a single field,
_all disabled, and field set to not indexed so there
Hello Christoph,
Yes, I did - I removed a huge index we no longer needed and reduced # of
replicas to 1 then 2 and that seems to have fixed it. I also upgraded to
1.3.4 so that could be a factor as well.
Cheers,
David
On Tuesday, November 11, 2014 5:21:50 AM UTC-8, Christoph Tavan wrote:
The status filter cache will indeed contain all entries. And technically,
the cache is per segment, and not across all documents, but this should be
transparent.
Caching is enabled by default for the term filters, but disabled for the
bool filter. You can enable it if you think users will be
Hi:
What is the syntax for using the scroll API for searches using the
scala interface (elastic4s) ?
I am not able to find suitable documentation for this and any help is
appreciated.
Thanks
Ramdev
--
You received this message because you are subscribed to the Google Groups
You're right Jorg. There was an issue where types was incorrectly set to
null because more than 1 was specified. As a result, it passed the check
for at least 1 element in the array, even though the type itself in element
0 was null. Thank you for your help!
On Tuesday, November 11, 2014
You should use 50% of your system memory for heap.
A client is just a node that is neither a master or a data node, though
once you set a node to master, you can leverage it as a client as well.
On 12 November 2014 05:02, lagarutte via elasticsearch
elasticsearch@googlegroups.com wrote:
Ok,
Thanks for the explanation.
A follow-up question. If caching the filter for a specific value, say {
term: { status: paid } }, will this somehow magically speed up the
query if searching for status: unpaid? I'm not talking about a not
operation, but simply replacing the value with something else
I have an index that will end up containing a few hundred types. I'm
dynamically creating these types based on some app logic. Each one can have
a different mapping, but they have some similarities.
One of these similarities is that all the documents across all the types
can be soft-deleted.
I have just a general question for the group. Is it possible to perform an
aggregation on the matched_queries field array from a named filter? I
have the the query at the bottom that I would like to perform (I simplified
it here). I can have potentially a number of user defined queries
Hi Peter,
Unfortunately elasticsearch does not support storing object fields (the
fact that it did not fail the mapping update that you sent is due to the
fact that parsing is lenient and ignores unknown parameters).
In your case, I think an option could be to keep _source enabled, and to
also
Hi Ivan,
You indeed ned to repeat the filter under a nested aggregation to make it
work. If we ever allow queries to return nested documents, I agree that
filters should not be repeated under aggs, but since now queries only
return the root documents, I think it is actually consistent to return
Thanks Jorg, make sense.
Few minor questions :
a) With the current ES architecture is this the best/recommended way?
b) Is there any project in roadmap to provide more support for it.
regards and thanks
amish
On Tuesday, November 11, 2014 12:08:24 PM UTC-8, Jörg Prante wrote:
FAST stored the
Hi Ankur,
I assume that your revenueFilter aggregation uses an actual filter and not
a match_all filter? Otherwise you could just remove it.
Are you actually interested in the top hits that match your query? If not,
you could switch to the `count` search type and move the filter from your
I'm also running into this issue. Is this expected behavior for
`ignoreUnavailable`?
On Wednesday, July 9, 2014 12:54:32 AM UTC-7, T Vinod Gupta wrote:
Hi,
Im on ES 1.2.1 and the below usage is not working for me. even if i pass
the option of ignoring unavailable or closed indices, i get an
i got no success and no responses from anybody.. im still clueless on this
one.. is this a bug?
thanks
On Tue, Nov 11, 2014 at 4:23 PM, Girish Sastry g.sas...@gmail.com wrote:
I'm also running into this issue. Is this expected behavior for
`ignoreUnavailable`?
On Wednesday, July 9, 2014
I'm having a the same problem. Kibana is on server A and elasticsearch is
on server B. Both servers are in a AWS VPC.
I can curl server B from server A: curl http://ipaddress:9200/_nodes?pretty
and I get the following results:
$ curl http://ipaddress:9200/_nodes?pretty
{
cluster_name :
Term filters already use lucene's term dictionary as an index. Almost
everything Elasticsearch does uses it. In fact term queries are so fast
that Elasticsearch switched them from being cached by default to uncached
by default (don't have version number handy). For the most part I wouldn't
worry
Hi,
In my application, i have huge set of records in ES. I am querying 50
records and writing to a file, it is working fine. After the file has been
generated, I tried the same query. But the memory is not released because
of the first query, SO i am getting out of memory error.
I have
The workaround described in the release notes fixed my issue! Thanks a lot!
Am Dienstag, 11. November 2014 20:11:57 UTC+1 schrieb rcmuir:
First, i would try the workaround mentioned in the article: disable
the compression and see if fixes the issue.
On Tue, Nov 11, 2014 at 1:42 PM,
63 matches
Mail list logo
