I understand the concept of how docs are checked against existing
percolators. One thing I am not clear on, does elasticSearch run against
percolators again for same un-changed documents?
eg.
I just indexed 5 million docs and ran it against all percolators.
The next day, I ran the same 5 millio
@campaignmonitor.com
> web: www.campaignmonitor.com
>
>
> On 9 July 2014 09:03, sabdalla80 > wrote:
>
> I upgraded to the latest version V 1.1.0 and I started getting new
> errors/Exceptions as showing below.
> Any ideas?
>
>
>
>
>
>
gt; https://github.com/elasticsearch/curator
>
> http://www.elasticsearch.org/blog/elasticsearch-curator-version-1-1-0-released/
>
> You would still need to use cron to schedule tasks, but it would be a
> curator task instead of a direct curl request.
>
> Cheers,
>
> Ivan
I am able to take a snapshot of the index and back it up to AWS S3. What is
the best way to automate this approach and have it done daily say every
days at 12 midnight?
I am aware that I can probably do it with crontab, but curious if other are
doing it differently?
--
You received this messa
://twitter.com/dadoonet> | @elasticsearchfr
> <https://twitter.com/elasticsearchfr>
>
>
> Le 4 juillet 2014 à 16:47:03, sabdalla80 (sabda...@gmail.com )
> a écrit:
>
> My cluster has two instances, I have the same setup on both instances. To
> answer Ross's
I also meant to mention that I commented out the credentials in the yml
file, I was still getting same message, meaning that credentials aren't
probably getting read for whatever reason.
On Friday, July 4, 2014 10:46:58 AM UTC-4, sabdalla80 wrote:
>
> My cluster has two instances,
t;,"base_path":"prod_backups","region":"us-east","bucket":"..."}}'
> {"acknowledged":true}
>
> In your latest post, it looks like you're running the command on a remote
> ES host (10.211.154.24). Does that sp
to backup our index to S3.
On Wednesday, July 2, 2014 3:36:58 PM UTC-4, sabdalla80 wrote:
>
> Unfortunately, I tried with and without the region setting, no difference.
>
> On Tuesday, July 1, 2014 7:43:21 PM UTC-4, Glen Smith wrote:
>>
>> I'm not sure it matters, but I
uesday, July 1, 2014 7:08:28 PM UTC-4, sabdalla80 wrote:
>>
>> I am not sure the version is the problem, I guess I can upgrade from V1.1
>> to latest.
>> "Not able to load credential from supply chain", Any idea this error is
>> generated, Is there any
oonet / @elasticsearchfr / @scrutmydocs
>
>
> Le 1 juil. 2014 à 22:13, Glen Smith >
> a écrit :
>
> According to
> https://github.com/elasticsearch/elasticsearch-cloud-aws/tree/es-1.1
> you should use v2.1.0 of the plugin with ES 1.1.0.
>
> On Tuesday, July 1, 2014
I am having a problem setting up backup and restore part of AWS on S3.
I have 2.1.1 AWS plugin & ElasticSearch V1.1.0
My yml:
cloud:
aws:
access_key: #
secret_key: #
discovery:
type: ec2
When I try to register a repository:
PUT /_snaps
11 matches
Mail list logo
