Hey all,
I have a testing machine that queries an elasticsearch node that is locally
on the very same machine.
The node has a single index with 2 primary shards and no replicas.
We've recently started running simultaneous tests on the machine and we
noticed that the elasticsearch node randomly
Great idea!
Close, but didn't work, but that got me to playing with
QueryBuilders.matchQuery, landing on this:
{
match : {
label.en : {
query : Ontology Inverse Functional Property Type,
type : boolean
}
}
}
which worked fine!
It did not occur to me that one could treat
Hi all,
New to Logstash and Elasticsearch so pardon any silliness on my end with
this configuration issue I'm currently having. I'm receiving the following
error when I try to startup the elasticsearch as suggested via the guide
linked below the following error code:
[root@server01 ~]#
Hi all,
New to Logstash and Elasticsearch so pardon any silliness on my end with
this configuration issue I'm currently having. I'm receiving the following
error when I try to startup the elasticsearch as suggested via the guide
linked below the following error code:
[root@server01 ~]#
Well.
I use the 1.0.0.RC1 this is what I get. ES still not working. What is
missing? I installed elasticsearch-cloud-aws.
/var/log/elasticsearch# service elasticsearch start
* Starting Elasticsearch Server
...done.
root@aws-elasticsearch-east-development:/var/log/elasticsearch#
Hi,
I have the following (simplified) structure:
{
id: 571344ad-c234-4144-92c2-94efa991240c,
name: MyDocument.pdf,
metaDataValueLst: [
{
metaDataFieldID: 19a2c920-013c-4a9f-91c7-d1a16a168779,
metaDataFieldName: BillNr,
metaDataValue: 5514
},
{
Unfortunately the problem will still not be addressed in the upcoming 1.0
release. Judging by recent comments from the elasticsearch team, they are
truly looking into the matter. The change will require changing the
underlying consensus algorithm to something like Paxos/Raft.
That said, the
Hello All,
I have tried Elasticsearch + fs-river plugin to read the local directory
and file system. I have a file about 2.5 gb text file. While reading this
file, it gives error and dump the heap to elastic search folder. I have
started the es server with 6gb memory as given in elastic search
I don't think the challenge for network disruptions are the same like for
node failures. Network disruptions can result in different and even
contradictory cluster views while all nodes stay intact, and the challenge
is that all nodes do not agree on one view. Consensus on a quorum or
timeouts
Do you want a 2.5G file being a single hit?
The correct method is to write code for reading the file in a stream-like
manner and extract the relevant content into JSON documents for search
hits.
If not, you have to prepare the file and partition it into docs by a domain
specific parser, a task
I have country codes in an index and there are country codes like AT, BE,
NO which are also in the English Stop words. For this reason, my search for
these countries are not working.
I need to have this query working (Search records with AT mentioned in any
of the files - AT=Austria)
POST
I never tested fsriver with such files.
What kind of file is it?
If it's not really indexable, I would exclude it.
--
David ;-)
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
Le 25 janv. 2014 à 20:14, joergpra...@gmail.com joergpra...@gmail.com a
écrit :
Do you want a 2.5G file being
That was exactly it thank you, I relied on 'yum install java' and for some
reason it threw up 1.6 previously, ran it again today and bam 1.7. Great
catch everything came up as soon as I threw that on the box, very much
appreciated. :)
--
You received this message because you are subscribed
It looks like it's happening every 33-34 minutes.
You might want to check if there is a scheduled task that is causing this
(eg cron).
Regards,
Mark Walkom
Infrastructure Engineer
Campaign Monitor
email: ma...@campaignmonitor.com
web: www.campaignmonitor.com
On 26 January 2014 00:59, Yarin
What java version are you using?
Also it's better to set min and max memory to be the same for ES.
Regards,
Mark Walkom
Infrastructure Engineer
Campaign Monitor
email: ma...@campaignmonitor.com
web: www.campaignmonitor.com
On 26 January 2014 02:58, Gabriel Blankenship dup...@mypcpros.net
On Sat, Jan 25, 2014 at 7:58 AM, Gabriel Blankenship
dup...@mypcpros.net wrote:
at java.lang.Class.initializeClass(libgcj.so.10)
at org.elasticsearch.bootstrap.Bootstrap.main(Bootstrap.java:155)
at org.elasticsearch.bootstrap.ElasticSearch.main(ElasticSearch.java:32)
Caused by:
Hi,
I think the per-shard stats are still not available, unless it got added
recently and I missed it?
Have a look at SPM for Elasticsearch, it may be detailed enough for you.
SPM doesn't show timing for individual queries, but our free Search
Analytics service does give you per-query timing
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 like.
jack, david), I will check permission with username in ACL.
But how to do it would be more convenient to perform this check by
Yeah that's the interval this is happening,
I've checked the cronjobs on the machine, there's nothing there.
On 26 January 2014 00:35, Mark Walkom ma...@campaignmonitor.com wrote:
It looks like it's happening every 33-34 minutes.
You might want to check if there is a scheduled task that is
19 matches
Mail list logo