Thanks Mark,
auth.log doesnt show any login or sudo at the time of the elastic
stopping...
nothing else is running on that machine - it is a dedicated ES server.
what i did find in the auth log is that someone is trying to hack into the
system, yet i dont see how it got to do with elastic
I did find the shutdown request in the syslog:
Aug 23 16:49:01 medisafelog2 kernel: [3361057.489168] hv_utils: Shutdown
request received - graceful shutdown initiated
yet i have no idea who or what initiated it... how can i dig in?
On Sunday, August 24, 2014 12:01:50 PM UTC+3, Eitan Vesely
The company which is providing the hosting service had shut down the
virtual machine, hv_utils is a message from the hypervisor.
This is not related to Elasticsearch at all.
Jörg
On Sun, Aug 24, 2014 at 11:19 AM, Mark Walkom ma...@campaignmonitor.com
wrote:
What version of ES are you
HI all,
I am using ELK stack to visualising our monitoring data, yesterday i came
across a weird problem: ElasticSearch date_histogram facet returned
floating results that look like an overflow (min : 4.604480259023595*E*
18).
Our dataflow is : collectd (cpu/memory) - sends it to riemann -
what is your logstash configuration?
did you tried the json codec http://logstash.net/docs/1.4.2/codecs/json?
On Sunday, August 24, 2014 4:54:08 PM UTC+3, Didjit wrote:
Hi,
The following is a debug from Logstash:
{
message =
{\EventTime\:\2014-08-24T09:44:46-0400\,\URI\:\
I ran into the same issue when using Integer.MAX_VALUE as the size
parameter (migrating from a DB-based search). Perhaps someone can come up
with a proper reference, I cannot, but according to a comment in this SO
Pretty simple (below). . I just added to json codec and tried again and
received the same results. Thank you!
elasticsearch {
host = localhost
cluster = cjceswin
node_name = cjcnode
codec = json
index = logstash-dwhse-%{+.MM.dd}
workers = 3
}
}
On Sunday, August 24, 2014 10:11:44 AM
Exactly. Filters do not use scores. They also use bit sets which makes them
reusable and fast.
I wasn't talking about a filter added to a query, I mean filtered queries.
This is a huge difference.
This query
{
query : {
bool: {
must: {
match : { body : big }
Hi,
Is the indices.memory.index_buffer_size configuration a cluster wide
configuration or per node configuration? Do I need to set it on every node?
Or just the master (eligible) node?
Thanks.
Yongtao
--
You received this message because you are subscribed to the Google Groups
elasticsearch
Interesting.
so, set a payload on the term, in this case the topic/entity, and the
payload is the relevancy value. Then, you can do your function score on the
query of the main documents themselves, no need for parent/child.
Have you done this? any concerns to performance with this sort of
Thanks Vineeth, I can certainly build something with the query string :-)
On Fri, Aug 22, 2014 at 8:50 PM, vineeth mohan vm.vineethmo...@gmail.com
wrote:
Hello Jeremy ,
You can try query_string then.
Query as Brown^2 dog
Adrien,
Thanks so much for the response. It was very helpful. I will check out
those links on capacity planning for sure.
One followup question. You mention that tens of shards per node would be
ok. Are you meaning tens of shards from tens of indexes? Or tens of
shards for a single index?
http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/modules-indices.html
states It is a global setting that bubbles down to all the different
shards allocated on a specific node.
Regards,
Mark Walkom
Infrastructure Engineer
Campaign Monitor
email: ma...@campaignmonitor.com
web:
Hello Albert ,
Few things here
1. Yes , you cal tell Elasticsearch which fileds to index and which
field not to index. You can use index : yes/no property for each field
in the schema to specify this. -
Hey guys,
I am trying to use the function score but I am getting the following error:
ElasticsearchIllegalArgumentException[No field found for [fsot] in mapping
with types [tst]];
I have used function score before and it worked like a charm so I started
digging what was wrong. I found out that
If the cluster is that open to users I don't think it'd be easy to prevent
a malicious user from intentionally DOSing it. But in this case I think you
could make the default for all fields be non-dynamic. That way users have
to intentionally send all mapping updates. It'd prevent this short of
Hello Sang ,
As this is a question answer forum , we highly recommend you to take a shot
yourself and post questions if you have hit a dead end.
Thanks
Vineeth
On Mon, Aug 25, 2014 at 7:56 AM, Sang Dang zkid...@gmail.com wrote:
Hi All,
I am going to build a log central using
Hello Pablo ,
Lucene ( the underlying library library on which ES is build upon) has only
key value concept and it does not keep object level information.
This means that on Lucene side , data would be stored as
fsot.testObjects : [ test1 , test2 ]
And there is not field names as fsot on lucene
It worked. Thank you very much.
* copying the final code for future referece:
POST test/tst/_search
{
query: {
function_score: {
boost_mode: replace,
query: {
filtered: {
query: {
match_all: {}
},
filter: {
exists:
Hi Adrien,
My elasticsearch version is : elasticsearch-1.2.1
The Maven dependency for hadoop:
dependency
groupIdorg.elasticsearch/groupId
artifactIdelasticsearch-hadoop-mr/artifactId
version2.0.1/version
/dependency
The full stack trace is given below:
[2014-08-25
20 matches
Mail list logo
