Robin Clarke ro...@robinclarke.net:
I just pasted output from uname there - that's kernel 3.2.54-2 you're
reading there.
I think the Debian release is Wheezy (7.0)
OK. The OS version can be found in the /etc/debian_version file.
--
You received this message because you are subscribed to
Is it possible to do a tail-like query on an ES index? Ie. find the
newest entries, when I don't know the time stamp of the indexed items?
(It's actually the time stamp I'm looking for, as well as the actual
data indexed at that point in time)
Thanks!
- Steinar
--
You received this message
Steinar Bang s...@dod.no:
[snip! Attempted transitioning from S3 to local gateway on EBS]
Unfortunately ES came up again, but without any indices. Should this
have worked? Or will it fail, because if things I don't understand
about how gateways work?
I googled a bit, and came up
Is this a way that could be used, perhaps?
http://tech.superhappykittymeow.com/?p=296
Ie.
1. Put the S3 stuff back into /etc/elasticsearch/elasticsearch.yml
2. Restart ES, and hopefully it will find the stuff it needs in S3 and
come up with the two indexes
3. Use the curl/sed commands in
Steinar Bang s...@dod.no:
Is this a way that could be used, perhaps?
http://tech.superhappykittymeow.com/?p=296
I tried, but no luck, I'm afraid.
Ie.
1. Put the S3 stuff back into /etc/elasticsearch/elasticsearch.yml
2. Restart ES, and hopefully it will find the stuff it needs in S3
One thing I could try, is snapshot to volatile storage, scrap the index
and restore from volatile storage.
http://www.elasticsearch.org/guide/en/elasticsearch/reference/master/modules-snapshots.html
Is that viable, with a 25.5GB index on an EC2 instance?
--
You received this message because
Steinar Bang s...@dod.no:
Steinar Bang s...@dod.no:
One thing I could try, is snapshot to volatile storage, scrap the index
and restore from volatile storage.
http://www.elasticsearch.org/guide/en/elasticsearch/reference/master/modules-snapshots.html
Trying to set up the backup
Steinar Bang s...@dod.no:
Nope, looks like I would need 1.0.0-beta2, rather than the 0.9.7 I have
currently installed:
http://www.elasticsearch.org/blog/1-0-0-beta2-released/
I'm now up and running on EBS storage on ES 1.0.0-beta2, after having
first created a snapshot with volatile storage
Platform: ES 0.9.7 on Ubuntu 12.04 on AWS EC2 instance
I now have the EC2 clustering stuff working on itself.
What I'm trying to do now, is index on ephemeral storage (where I have
space) and save the index to s3, and restore it on EC2 instance startup.
Note: I am only running a single node in
Steinar Bang s...@dod.no:
Ross Simpson simps...@gmail.com:
Ok, thanks! I will try giving it a bit longer time and see what
happens.
I gave it 1h 40minutes last night, but all that came out in the log file
was:
[2013-12-21 19:39:42,205][INFO ][node ] [Stem Cell]
version
Steinar Bang s...@dod.no:
I gave it 1h 40minutes last night, but all that came out in the log file
was:
[2013-12-21 19:39:42,205][INFO ][node ] [Stem Cell]
version[0.90.7], pid[1317], build[36897d0/2013-11-13T12:06:54Z]
[2013-12-21 19:39:42,205][INFO ][node
Karel Minařík karel.mina...@gmail.com:
Very good option on EC2 are EBS volumes, notably the IOPS (optimized
or high I/O) ones. You can easily create snapshots, unmount the volume
and mount it at different instance, etc.
Ok, I will study up on EBS volumes. Thanks!
(Some people also use
David Pilato da...@pilato.fr:
Wondering if you have something wrong in elasticsearch.yml file.
Except for adding the EC2 stuff from the EC2 page, it is the file of the
.deb package:
http://www.elasticsearch.org/tutorials/elasticsearch-on-ec2/
Also, if I don't attempt to use either EC2
Karel Minařík karel.mina...@gmail.com:
The EC2 plugin doesn't mess with networking settings, so the behaviour
you're describing is weird.
I got the same behaviour when /var/lib/elasticsearch/elasticsearch was a
dangling symlink to /mnt/var/lib/elasticsearch/elasticsearch (from an
experiment
Ross Simpson simps...@gmail.com:
How long did you wait after starting with AWS settings before checking the
lsof output?
A minute or two or three, or maybe five. In any case much longer than
the normal ES startup time on the EC2 instance.
I've found that startup time on AWS can be quite
I am running ES 0.90.4 on an Ubuntu 12.04 LTS EC2 instance.
Starting this instance, it starts listening to port 9200:
ubuntu@ip-172-31-31-127:/var/lib/elasticsearch$ sudo lsof -i TCP | grep 9200
java1982 elasticsearch 102u IPv6 12069 0t0 TCP *:9200 (LISTEN)
16 matches
Mail list logo