SSD will improve overall performance very much, yes. Disk drives are the
slowest part in the chain and this will help. No more low IOPS, so it will
significantly reduce the load on CPU (less IO waits).
More RAM will not help that much. In fact, more RAM will slow down
persisting, it increases
Hi Alex ,
Thanks for replaying. gateway.expected_datanodes settings works nicely , it
starts recovery once all the datanodes (i configured) arrived.
Before performing full cluster restart , if the cluster in green state
,then no need for BalancedShardAllocator on initial recovery after
I am trying to do the follwing query but it is showing error
{
query: {
boosting: {
positive: {
term: {
name: kamal
}
},
negative: {
term: {
email: abc
}
}
}
}
}
--
You received this message because you
Thanks for the clarification Mark
On Tuesday, February 4, 2014 9:04:43 AM UTC+2, Mark Walkom wrote:
The *easiest* is to do an upgrade directly to v1.0, but I highly doubt if
that will even work after the upgrade due to the number of changes between
0.2X, 0.90.X and 1.0.0.
And frankly,
Hi Navneet,
What error you are getting while running above command?
Try following Query:
curl -XPOST localhost:9200/indexName/indexType/_search?pretty=true -d '
{
query : {
boosting : {
positive : {
term : {
name : kamal
}
},
if I am running the above command it is showing SearchPhaseExecutionException
error ... but the command you have suggested working fine.
Thanks.
On Tuesday, 4 February 2014 14:24:39 UTC+5:30, Jayesh Bhoyar wrote:
Hi Navneet,
What error you are getting while running above command?
Hello everyone ,
i am also trying to do something like this:
my intended query is like this:
select from range (dateA to dateB);
AndFilterBuilder myFilters = FilterBuilders.andFilter();
myFilters.add(FilterBuilders.rangeFilter(dateFormatted).gte(dateDebut).lte(dateFin));
howeve this
Hi
i have some documents like this
{
date : 2014-01-01,
periods : {
{ start : 0 , duration: 55 },
{ start : 1 , duration: 55 },
{ start : 2 , duration: 55 },
{ start : 3 , duration: 55 },
etc...
}
}
I do a query on a date range with a statistical facet to
If you are using M1 you should use es.resource instead of es.query in your
latest example.
es.query is supported in the upcoming 1.3.0.M2 (not in m1).
On 04/02/2014 12:01 PM, Phil gib wrote:
hello my context:
ES 0.90.3, elasticsearch-hadoop-1.3.0.M1 , eclipse- java
i am experimenting
hello my context:
ES 0.90.3, elasticsearch-hadoop-1.3.0.M1 , eclipse- java
i am experimenting ES-Hadoop and Hadoop-ES
no problem with Hadoop2ES with these 3 settings ( i see the index + data
through head plugin, perfect)
job.set(es.resource, eshindex2/eshlog2);
job.set(es.host,
Hi David, Joseph,
Marvel generates (by default) reports every 5 seconds. Depending on the
number of nodes/shards indices this can result in different amount of
data. All of marvel's data is stored (again by default) in daily indices
named .marvel-.MM.dd (replace with date). You can safely
Hi Tony,
The red color does mean it needs attention. By default, Marvel will warn
you if you have less than 50GB of free space (displayed in yellow) and will
go red if you have less than 20GB. If you had higher numbers displayed in
color, please let me know as it is a bug.
Cheers,
Boaz
On
Hey,
The unicast discovery is just a different way of doing discovery and if
configured correctly it shouldn't introduce any over head. You should think
of the list of hosts in the unicast list as a seed list, it doesn't need
to be complete. When a node starts it will ping these addresses to
A couple of points:
1) If you bring down a whole cluster and start it back up, it may be that
during the start process the cluster is red. The reason is that until all
nods have rejoined some data may not be (yet) available for searching. This
should be resolve as soon as all the nodes are
Hi
I've released a Object/Search Engine Mapping (OSEM) for ElasticSearch and
Redis Transport for ElasticSearch
https://github.com/kzwang/elasticsearch-osem
https://github.com/kzwang/elasticsearch-transport-redis
Thanks.
Kevin
--
You received this message because you are subscribed to the
Hi ,
I do give a refresh to true in my Bulk request call.
It works fine every time but then when the following logs appear in the
logs , the call get stuck -
[2014-02-04 00:04:36,715][DEBUG][index.merge.scheduler] [Richard Rider]
[relations][0] merge [_1vl] done, took [1.1m]
[2014-02-04
Maybe this helps: https://github.com/salyh/elasticsearch-security-plugin
Am Sonntag, 26. Januar 2014 05:39:59 UTC+1 schrieb David shi:
Hi guys:
I have data like: {emolument:2, partment:Financial, ACL:
{jack:rw,david:r} }
Now when user request api with DELETE or PUT (with useranme
Hello Costin,
changing to es.resource does not help... :-(
argh.. i see the socket connection closed in the ES logs.. so ES is
contacted ... the 9200 is correct ?
philippe
best regards
configuration.set(es.resource, eshindex2/eshlog2/_search?q=*);
configuration.set(es.host,
Hi,
When working with a nested type which is a list of objects, is it possible
to constrain the scope of the query to an object ay a specific index?
i.e. if 'foo' is a nested type, can I search only for foo[0] rather than
foo[1] within the parent document.
i.e. I want the path of my nested
The port and host are 9200 and localhost by default. What's your ES version?
ES-Hadoop requires 0.90 or higher (preferably the latest 0.90).
On 04/02/2014 12:59 PM, Phil gib wrote:
Hello Costin,
changing to es.resource does not help... :-(
argh.. i see the socket connection closed in the
I've loaded the same dataset in ES1.0.0.Beta2 with the same index
configuration as in the topic start.
However now the numbers are consistent if I call the same aggregation
multiple times in a row AND the number match the numbers of the facets.
This leads me to the conclusion something is
Hi Ivan,
I followed your advice and started using explain api for query_string but I
guess in process I found a bug (don't know if it really is a bug or
intended behaviour of query_string). This is going to be a long post,
please be patient with me.
I'm using a doc:{name:new delhi to goa,st:goa}
Thnaks for your reply,
my SW context is:
ES 0.90.3, elasticsearch-hadoop-1.3.0.M1 , eclipse- java, windows7
(perharps some configuration problem in Eclipse , i will investigate )
best regards
philippe
On Tuesday, February 4, 2014 12:22:54 PM UTC+1, Costin Leau wrote:
The port and host are
Maybe this helps: https://github.com/salyh/elasticsearch-security-plugin
Am Donnerstag, 23. Januar 2014 17:37:20 UTC+1 schrieb David Haimson:
Our data is stored in MongoDB 2.4.8, and indexed to ElasticSearch 0.90.7
using the ElasticSearch MongoDB River 1.7.3.
Our data indexes correctly, and
Hi Karel,
Thanks for your response, OK just seems kind of counter intuative to me,
after all I have supplied everything it would need to create the index,
type and add the map (you know being elastic and all :-)) and it can easily
be achieved via the Java API (I'm sure it used to be
Shamsul Haque, I am also getting the same error on Elastic Search console
even though the type of id is string not int in my case. Any clue ?
On Wednesday, January 8, 2014 11:06:36 AM UTC+1, shamsul haque wrote:
I have downloaded river from: https://github.com/eBay/cassandra-river
change the
To follow up,
I have a contained test suite at https://gist.github.com/thanodnl/8803745for
this problem. It contains two files:
1. aggsbug.sh
2. aggsbug.json
The .json file contains ~1M documents newline separated to load into the
database, I was not able to create a curl request to
Hi guys,
I am trying to create an index with the following code:
XContentBuilder source = XContentFactory.jsonBuilder().startObject()//
.startObject(settings)
.field(number_of_shards, 1)
.endObject()// end settings
I've restarted the cluster a couple times since and not seen what I saw
before.
Been reading more of the documentation, am going to set the min-max
master to 3 which is suggested for a 5 node cluster.
Currently speculating, although I thought I've been very careful to start
the master
Hi Tony,
It's good you're going to use the minimum_master_nodes settings. When this
number of master eligible nodes have started (more on this in a second),
one will be picked up randomly and that will stay so until that elected
master becomes unreachable (= shutdown).
If you want to control
*2) Though *not* recommended - kill -9 should not result in data loss. If
so it's a bug and should be reported.*
It *should* not, but it *may*. A kill -9 ends a process without allowing it
to flush any unwritten buffers to disk, close any open files, or even
finish writing what it started.
Thx,
For anyone who views this thread who wants to see an example how this looks
in Marvel,
I've posted a screenshot
https://github.com/putztzu/Misc_images/blob/master/screenshot.png
Tony
On Tuesday, February 4, 2014 2:16:07 AM UTC-8, Boaz Leskes wrote:
Hi Tony,
The red color does
Hi,
Just wanted to drop a note that we just release Marvel 1.0.2 which contains
a fix for this.
See http://www.elasticsearch.org/guide/en/marvel/current/#_change_list .
Cheers,
Boaz
On Friday, January 31, 2014 3:23:33 PM UTC+1, Sean Gallagher wrote:
Thanks for reporting this issue! I've
Hey Al,
We just release marvel 1.0.2, which contains support for basic auth for the
data shipping. Can you give it a spin?
See: http://www.elasticsearch.org/guide/en/marvel/current/#configuration
Cheers,
Boaz
On Thursday, January 30, 2014 11:59:00 AM UTC+1, Boaz Leskes wrote:
Hi Al,
This
Is there anyway to make elasticsearch take advantage of GPGPU, when
available? It would be nice to have some sort of plugin for this type of
thing, in the future.
See here:
http://en.wikipedia.org/wiki/General-purpose_computing_on_graphics_processing_units
--
You received this message
Just a reminder to whomever...
I'm noticing that the comments in elasticsearch.yml that reference or point
to URLs that worked in 1.0 may no longer work.
eg
Node Discovery (and viewing health)
http://localhost:9200/_cluster/nodes
I'm not sure but I think it should be changed to
Unless I'm missing something in the docs or these forums,
I've surprisingly found that if a node fails to join the cluster, it's not
sufficient to simply restart ES on the machine. I would have thought that
restarting ES thereby re-reading its config files should be sufficient to
announce its
Here is something:
http://blogs.nvidia.com/blog/2013/09/22/gpu-coming-to-java/
--
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
Hi,
I understand you probably meant to post this to one of my other threads
https://groups.google.com/forum/#!topic/elasticsearch/dC48AAeL544
Interesting late development.
Too bad it sounds like what IBM is developing will be available only on IBM
servers, but it's understandable.
Unless
There is a complete curl recreation in this gist:
https://gist.github.com/gmateev/8808650
--
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
Hi,
we are setting up a Elasticsearch 1.0 (RC2) Cluster and I think I need some
help were to start with (settings related). We have got 6 physical server
with 265GB RAM and 2TB local SAS storage (seperated in two Raid10 Groups as
LVM VGs). Those six servers are running Ubuntu 14.04. All roles
H
Looks interesting although of course for the moment is a very narrow
implementation but may pave the way for more.
At first glance it sounds like one could write a CUDA app in OpenCL and
access the JRE installed and running on the CPU (not GPU).
If I understand that correctly, then
Hello
I'm having problems with sorting. I want to get the latest data (with the
biggest date_created).
So I curl like this:
curl -vsX GET myelastic.com/notifications/notification/_search -d '{
query: {
bool: {
must: [
{
term: {
type: config_withdraw
}
}
],
must_not: [],
Hello everyone,
well i am new to elastic search and i am facing some similar difficulties
as mentioned above. i tried implementing some of the suggested solution but
to no avail.
I am posting part of codes and will be very grateful if somebody could help
me out. Thanks in advance.
the codes
John,
Same questions, did you ever figure anything out on this?
Jason
On Friday, June 7, 2013 4:35:22 AM UTC-4, John Zhang wrote:
Hi guys,
I am one newer for elasticesearch.
I am trying ElasticSearch +Kibana + Logstash for my security log
management, I also need do event correlation
Alex,
Thanks for your reply.
There are other es instance (0.90.10) running. But I have configured mine
to have a different cluster name. but still it throws failed to read
requesting data warnings. Can these warnings be safely ignored?
Thanks,
Chen
On Monday, February 3, 2014 11:47:58 PM UTC-8,
My use case is bibliographic data indexing of academic and public
libraries. There are ~100m records from various sources that I regularly
extract, transform into JSON-LD, and load into Elasticsearch. Some are
files, some are fetched by JDBC. I have six 32-core servers in our place,
organized in 2
We've had some success improving bulk insertion times using a higher value
for refresh_interval when doing bulk inserts.
However, the global nature of this setting seems to cause some problems.
We want some insertions processed with a higher value and others processed
immediately (under the
Hi,
I've been trying to make use of the Azure Cloud plugin today to enable
azure discovery of nodes, with very little success
I have two clusters and both are exhibiting the same behaviour, I'm testing
using the Head plugin
Cluster 1 - previously working fine with multicast disabled and ip
Hi,
I read with interest the news about the Azure Cloud Plugin over the
weekend and today have been trying to get it working with Windows VMs on
Azure with mixed levels of success.
I have two environments/clusters one which has been running for a few weeks
and another which is brand new
Hello there,
I tried to solve this for a while with no success and I'm asking for help
with using the geoDistanceFilter (and this problem happens both on Java as
well as on the REST api).
When I'm using geoDistanceFilter, such as here:
FilterBuilder locationFilter =
Hello everyone,
well i am new to elastic search and i am facing some similar difficulties as
mentioned above. i tried implementing some of the suggested solution but to
no avail.
I am posting part of codes and will be very grateful if somebody could help
me out. Thanks in advance.
the codes are
That looks ok, similar to how we do things with virtualised master/data
nodes.
I wouldn't specify your shard/replica count on the node though, do it in
the index as it allows you to change with ease.
Regards,
Mark Walkom
Infrastructure Engineer
Campaign Monitor
email: ma...@campaignmonitor.com
Hi,
Is it possible to do a suggestion completion on a type. im able to do it on
an index .
POST /data/_suggest
{
data : {
text : tr,
completion : {
field : sattributes,
size:50
}
}
}
when i do on a type
POST /data/suggestion/_suggest
{
data : {
text : tr,
Could you please GIST your logs on both nodes?
Also, could you change Log level to TRACE for discovery? (See
config/logging.yml file)
Thanks
--
David ;-)
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
Le 4 févr. 2014 à 22:42, Andrew Westgarth m...@hawaythelads.co.uk a écrit :
Hi,
Hi David,
here's the gist for the logs from the three nodes of Cluster 2
- https://gist.github.com/apwestgarth/8813941 first thing I noticed which
is strange is node 1 is referring to the cluster as sageerpdev_escluster
whereas node 2 and 3 are correctly referring to it as
Is there any documentation on implementing custom panels in Kibana?
--
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.
Hello,
I am trying to add elastic search to a eCommerce website based on php and
MySQL platform and spend today trying to research on elastic search. I
learnt alot and have a fairly good idea on what to do. I just wanted some
guidance if my understanding of elastic search with MySQL is
I confess that, at least for me, documentation, including purchased
books, remains a bit ambiguous, where the context is that of making my
ES client talk to two different servers.
In the end, I did nothing to the elasticsearch.yml files at each
server; it simply was not clear what needed to be
We are planning on upgrade from 0.90.5 to 0.90.10 in our live environment.
Prior to that we want to do the same in the test environment. Please find
below the environment, upgrade steps and post upgrade issue detail
Environment:
- Master Only (no data node) - 3
- data only nodes - 3
-
Good to know, I will keep this in mind, even though I will try to go for
SSD as I personally had great success with them in the past! When you say
10-12 MB/sec, is this with doc parsing/processing or just ES index time.
For my humble test on a quadcore labtop, I am pushing 6 MB/sec with
Hi Jack,
Although I'm a bit new to this, too...
1. You should take a look at your ES log files. Depending on how you
installed and are running ES, the log files could be in different places.
If I were to guess though, you should look in the following directory
/var/log/elasticsearch/
2. One
SSD is the best you can do for the persistence layer. I have such an ES
4xSSD RAID0 server at home, with 800 MB/sec sustained write I/O rate. My
servers for my day job are some years old when some TB in SSD costed a
fortune.
The higher the writing rate and IOPS capacity of the drives are, the
Can you please file a bug (https://github.com/eBay/cassandra-river/issues)
or share the stacktrace?
Thanks,
-Utkarsh
On Tue, Feb 4, 2014 at 8:54 AM, AKhan ansa...@gmail.com wrote:
cassandra-river is not working in my case too and I am getting exceptions
on server side.
Hi Mark,
I've done all that to no effect.
FYI if it makes a diff,
I'm running on a distro that uses systemd, so in theory when the Service is
started, it's supposed to create a cgroup in which the new process is run,
and if there are any processes that are spawned (including but not limited
If data is re-loaded which is identical in every way to data which already
exists in ES,
Is new metadata created that simply over-writes existing (zero net effect)?
Or is duplicate, unique metadata created?
Or, maybe since identical data is found to already exist, although the
update API was
Congrats for deciding to start indexing RDBMS data with Elasticsearch, I
hope I can be helpful.
To add to 4) - you can craft a select query (or queries) to either
overwrite old docs in ES or add timeframe based incremental updates to ES.
Autocommit is not related to updates in ES. In fact there
That's very timely.
The second-to-start node is receiving a join request from 10.1.10.80:9303
even though 10.1.10.80 does not ping from anywhere in the network
I'll look into adding http://www.elastichq.org/ to the browser and see
what it says.
Many thanks
Jack
On Tue, Feb 4, 2014 at 5:13 PM,
Did you change the cluster name as the blog suggested?
And can you clarify what client you are using as well?
Regards,
Mark Walkom
Infrastructure Engineer
Campaign Monitor
email: ma...@campaignmonitor.com
web: www.campaignmonitor.com
On 5 February 2014 12:20, Jack Park
Hi Tony,
What I have observed in my so far experience with ES that it simply
over-write the exisiting data with change in version.
Regards,
Jayesh Bhoyar
http://www.linkedin.com/in/jayeshbhoyar
On Wednesday, February 5, 2014 6:16:32 AM UTC+5:30, Tony Su wrote:
If data is re-loaded which is
Hi All,
Here is the solution for all of you:
1) You have to define your facet as multi_field value as follows
mappings: {
data: {
properties: {
name: {
type: multi_field,
fields: {
name: {
type: string,
index:
Hi,
Can you try following syntax for sorting the date value?
sort: [
{
date_created: {
order: desc
}
}
]
Let me know if this solves your problem.
I was using this syntax succesfully for integer value
Regards,
Jayesh
I started using explain api for query_string but I guess in process I found
a bug (don't know if it really is a bug or intended behaviour of
query_string). This is going to be a long post, please be patient with me.
I'm using a doc:{name:new delhi to goa,st:goa}
On using analyzer api for
Interesting topic. Not elasticsearch specific, but nevertheless
interesting. One method to calculate relevancy given the precision and
recall of a query is by using the F1 score:
http://en.wikipedia.org/wiki/F1_score
F1 would be equal to 2 * (P * R) / (P + R), where P is the precision and R
is
Hi Clinton,
We are also facing the issue , I verified recovery starts only after
expected nodes arrived. In case of full cluster restart , initially all the
shards become unavailable and master starts allocate unassigned nodes.
While allocation BalancedShardAllocator comes to play which
Hi Mark,
thank you for your answer.
Am Dienstag, 4. Februar 2014 23:08:32 UTC+1 schrieb Mark Walkom:
That looks ok, similar to how we do things with virtualised master/data
nodes.
I wouldn't specify your shard/replica count on the node though, do it in
the index as it allows you to change
hey thanks ivan :)
On Wednesday, 5 February 2014 12:44:46 UTC+5:30, Ivan Brusic wrote:
Interesting topic. Not elasticsearch specific, but nevertheless
interesting. One method to calculate relevancy given the precision and
recall of a query is by using the F1 score:
Ivan but
On Wednesday, 5 February 2014 11:36:50 UTC+5:30, Navneet Mathpal wrote:
Hi,
I want to know how do we calculate relevancy with the help of precision
and reacall,
for example:-
A = The number of relevant records retrieved,
B = The number of relevantrecords not retrieved, and
C
Hi Hiro,
I think you should use script term statistics.
http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/modules-advanced-scripting.html#_term_statistics
I post sample json and query DSL to gist.
https://gist.github.com/johtani/8818938
Note: Term “Java” is indexed just
79 matches
Mail list logo
