ber of
> segments will reduce the need for IO. You may want to consider moving to a
> t2.medium which is in the same ballpark of cost, but can burst to much
> better performance.
>
> On Mon, Mar 16, 2015 at 8:58 AM, Andy Nemzek > wrote:
>
>> Good to know, thanks for the t
d"
}
}
'
Would this prevent users through kibana to execute query and get meaningful
result unless they specify field name? My understanding:
Search string: * "Andy" *would return 0 results since it gets executed on filed
"id"
Search string *name:"
Mark,
Very thanks for your answer. I am new to ES. Can i get implementation
instruction or detailed answer? Thanks,
Andy
On Monday, March 23, 2015 at 9:11:18 PM UTC-7, Mark Walkom wrote:
>
> You'll want aliases with a routing query here, but to get the full benefit
> you'
In my org, each team is creating ES index so the number of index grows very
quickly. Usually users are interested only in their 'product' data.
Currently, users execute query using Kibana w/o specifying index(it takes
_all'). To force user to specify index, what are my options? At the same
t
in bursts, but sustained EBS does not work well. It will work
> substantially better in an m3.medium and if you are using the new EBS SSD
> volumes.
>
> On Thu, Mar 12, 2015 at 10:30 PM, Andy Nemzek > wrote:
>
>> Thank you guys for your thoughts here. This is really usef
me of the smaller instance size
> significantly limit prolonged EBS throughput, in my experience.
>
> On Wednesday, March 11, 2015 at 1:12:01 AM UTC-6, Magnus Bäck wrote:
>>
>> On Monday, March 09, 2015 at 20:29 CET,
>> Andy Nemzek wrote:
>>
>> > We
ough, the optimise is a resource heavy operation, so unless you
> have a lot of resources you should only run one at a time.
>
> On 10 March 2015 at 05:18, Andy Nemzek >
> wrote:
>
>> Hello,
>>
>> My company is using the ELK stack. Right now we have a very smal
dices, eg older than 7 days, down
> to a single segment and then see if that helps.
>
> Be aware though, the optimise is a resource heavy operation, so unless you
> have a lot of resources you should only run one at a time.
>
> On 10 March 2015 at 05:18, Andy Nemzek >
> w
Hello,
My company is using the ELK stack. Right now we have a very small amount
of data actually being sent to elastic search (probably a couple hundred
logstash entries a day if that), however, the data that is getting logged
is very important. I recently set up snapshots to help protect thi
or the feature (this is not a corner
>>> case)Is this feature expected to work in some other coordinate system?
>>> Any workaround to overcome this bug? Thanks!
>>> Andy
>>>
>>> On Saturday, December 27, 2014 6:40:44 AM UTC-8, Peter Johnson wrote:
>
that way by design, then I would rather not spend the time.
Thoughts?
Thanks!
Andy Walker
--
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 elasticsea
+1 on everything. I use Sense daily and really hope it stays independent.
It's a great tool for testing queries and demoing ES to others with no
friction.
On Friday, March 28, 2014 3:37:27 AM UTC-5, Tim S wrote:
>
> I notice that https://github.com/bleskes/sense has a message saying "The
> deve
Thanks for the reply. There shouldn't be a problem in keeping the ES and
Java versions in sync. We're a .Net app so we would be totally free to run
whatever version of Java required. We're preparing to maintain the list of
nodes anyway as apparently our host doesn't allow for multi-casting, so
Hi all,
I'm sorry if this is a totally beginner question with a obvious answer, but
I just haven't found anything that explains this clearly, most tutorials
don't cover this sort of thing. We're investigating the use of Elastic
Search and was wondering what the best topology would be. My readi
14 matches
Mail list logo
