I currently am running 3 small instance EC2 nodes and I want to move
to 2 large EC2 instances.
What is the best way to migrate the data? I brought up a large EC2
instance already but if I shut down one of my small instances, then
half the documents disappear. Again, I'm not too clear how the
failover and sharding is working behind the scenes.
Shards are allocated between nodes started, and I find it strange that half
your docs disappeared when you shut down one node. They should not, since
you have replicas on the other node. In general, as long as you don't do
full cluster shutdown, you can bring more nodes into play and then shut down
the other nodes. Shards will be allocated automatically between the nodes
(with the replicas).
Do you use unicast discovery in amazon? How do you configure it?
I currently am running 3 small instance EC2 nodes and I want to move
to 2 large EC2 instances.
What is the best way to migrate the data? I brought up a large EC2
instance already but if I shut down one of my small instances, then
half the documents disappear. Again, I'm not too clear how the
failover and sharding is working behind the scenes.
Here's another weird happenstance. On the node that I shutdown, all of
the index files disappeared. Poof, gone.
This happened once before too. I realized that I needed more disk
space so I moved the entire elasticsearch directory ... when I started
up again, all of the index files were gone.
Shards are allocated between nodes started, and I find it strange that half
your docs disappeared when you shut down one node. They should not, since
you have replicas on the other node. In general, as long as you don't do
full cluster shutdown, you can bring more nodes into play and then shut down
the other nodes. Shards will be allocated automatically between the nodes
(with the replicas).
Do you use unicast discovery in amazon? How do you configure it?
I currently am running 3 small instance EC2 nodes and I want to move
to 2 large EC2 instances.
What is the best way to migrate the data? I brought up a large EC2
instance already but if I shut down one of my small instances, then
half the documents disappear. Again, I'm not too clear how the
failover and sharding is working behind the scenes.
Here's another weird happenstance. On the node that I shutdown, all of
the index files disappeared. Poof, gone.
This happened once before too. I realized that I needed more disk
space so I moved the entire elasticsearch directory ... when I started
up again, all of the index files were gone.
Shards are allocated between nodes started, and I find it strange that
half
your docs disappeared when you shut down one node. They should not, since
you have replicas on the other node. In general, as long as you don't do
full cluster shutdown, you can bring more nodes into play and then shut
down
the other nodes. Shards will be allocated automatically between the nodes
(with the replicas).
Do you use unicast discovery in amazon? How do you configure it?
I currently am running 3 small instance EC2 nodes and I want to move
to 2 large EC2 instances.
What is the best way to migrate the data? I brought up a large EC2
instance already but if I shut down one of my small instances, then
half the documents disappear. Again, I'm not too clear how the
failover and sharding is working behind the scenes.
Here's another weird happenstance. On the node that I shutdown, all of
the index files disappeared. Poof, gone.
This happened once before too. I realized that I needed more disk
space so I moved the entire elasticsearch directory ... when I started
up again, all of the index files were gone.
Shards are allocated between nodes started, and I find it strange that
half
your docs disappeared when you shut down one node. They should not, since
you have replicas on the other node. In general, as long as you don't do
full cluster shutdown, you can bring more nodes into play and then shut
down
the other nodes. Shards will be allocated automatically between the nodes
(with the replicas).
Do you use unicast discovery in amazon? How do you configure it?
I currently am running 3 small instance EC2 nodes and I want to move
to 2 large EC2 instances.
What is the best way to migrate the data? I brought up a large EC2
instance already but if I shut down one of my small instances, then
half the documents disappear. Again, I'm not too clear how the
failover and sharding is working behind the scenes.
Here's another weird happenstance. On the node that I shutdown, all of
the index files disappeared. Poof, gone.
This happened once before too. I realized that I needed more disk
space so I moved the entire elasticsearch directory ... when I started
up again, all of the index files were gone.
Shards are allocated between nodes started, and I find it strange
that
half
your docs disappeared when you shut down one node. They should not,
since
you have replicas on the other node. In general, as long as you don't
do
full cluster shutdown, you can bring more nodes into play and then
shut
down
the other nodes. Shards will be allocated automatically between the
nodes
(with the replicas).
Do you use unicast discovery in amazon? How do you configure it?
I currently am running 3 small instance EC2 nodes and I want to
move
to 2 large EC2 instances.
What is the best way to migrate the data? I brought up a large EC2
instance already but if I shut down one of my small instances, then
half the documents disappear. Again, I'm not too clear how the
failover and sharding is working behind the scenes.
Here's another weird happenstance. On the node that I shutdown, all of
the index files disappeared. Poof, gone.
This happened once before too. I realized that I needed more disk
space so I moved the entire elasticsearch directory ... when I started
up again, all of the index files were gone.
Shards are allocated between nodes started, and I find it strange
that
half
your docs disappeared when you shut down one node. They should not,
since
you have replicas on the other node. In general, as long as you don't
do
full cluster shutdown, you can bring more nodes into play and then
shut
down
the other nodes. Shards will be allocated automatically between the
nodes
(with the replicas).
Do you use unicast discovery in amazon? How do you configure it?
I currently am running 3 small instance EC2 nodes and I want to
move
to 2 large EC2 instances.
What is the best way to migrate the data? I brought up a large EC2
instance already but if I shut down one of my small instances, then
half the documents disappear. Again, I'm not too clear how the
failover and sharding is working behind the scenes.
It sounds like you don't have any replicas. You may want to check the config
for your indexes. There are some REST API calls you can use to see how many
shards, replicas there are, status etc.
You should also check that the nodes are talking to each other successfully
just to be sure if you haven't done that already.
Regards,
Berkay Mollamustafaoglu
mberkay on yahoo, google and skype
Here's another weird happenstance. On the node that I shutdown, all
of
the index files disappeared. Poof, gone.
This happened once before too. I realized that I needed more disk
space so I moved the entire elasticsearch directory ... when I
started
up again, all of the index files were gone.
Shards are allocated between nodes started, and I find it strange
that
half
your docs disappeared when you shut down one node. They should
not,
since
you have replicas on the other node. In general, as long as you
don't
do
full cluster shutdown, you can bring more nodes into play and
then
shut
down
the other nodes. Shards will be allocated automatically between
the
nodes
(with the replicas).
Do you use unicast discovery in amazon? How do you configure it?
I currently am running 3 small instance EC2 nodes and I want to
move
to 2 large EC2 instances.
What is the best way to migrate the data? I brought up a large
EC2
instance already but if I shut down one of my small instances,
then
half the documents disappear. Again, I'm not too clear how the
failover and sharding is working behind the scenes.
I'm using the default settings. I'll check to see if the default has
replicas or not.
I'm also going to setup an S3 gateway, just in case.
The nodes are taking to each other. When I do a search on each node,
the results are the same for each.
Thanks for the help everybody, it's great when an open source project
has a supportive community.
On Jul 15, 7:03 pm, Berkay Mollamustafaoglu mber...@gmail.com wrote:
It sounds like you don't have any replicas. You may want to check the config
for your indexes. There are some REST API calls you can use to see how many
shards, replicas there are, status etc.
You should also check that the nodes are talking to each other successfully
just to be sure if you haven't done that already.
Regards,
Berkay Mollamustafaoglu
mberkay on yahoo, google and skype
Here's another weird happenstance. On the node that I shutdown, all
of
the index files disappeared. Poof, gone.
This happened once before too. I realized that I needed more disk
space so I moved the entire elasticsearch directory ... when I
started
up again, all of the index files were gone.
Shards are allocated between nodes started, and I find it strange
that
half
your docs disappeared when you shut down one node. They should
not,
since
you have replicas on the other node. In general, as long as you
don't
do
full cluster shutdown, you can bring more nodes into play and
then
shut
down
the other nodes. Shards will be allocated automatically between
the
nodes
(with the replicas).
Do you use unicast discovery in amazon? How do you configure it?
I currently am running 3 small instance EC2 nodes and I want to
move
to 2 large EC2 instances.
What is the best way to migrate the data? I brought up a large
EC2
instance already but if I shut down one of my small instances,
then
half the documents disappear. Again, I'm not too clear how the
failover and sharding is working behind the scenes.
Are you using 0.8? There was a similar problem in 0.8 that was fixed in
upcoming 0.9 (god, this version is long overdue, working hard on getting it
out). Note, current master (0.9) does not have a functioning cloud gateway
plugin.
I'm using the default settings. I'll check to see if the default has
replicas or not.
I'm also going to setup an S3 gateway, just in case.
The nodes are taking to each other. When I do a search on each node,
the results are the same for each.
Thanks for the help everybody, it's great when an open source project
has a supportive community.
On Jul 15, 7:03 pm, Berkay Mollamustafaoglu mber...@gmail.com wrote:
It sounds like you don't have any replicas. You may want to check the
config
for your indexes. There are some REST API calls you can use to see how
many
shards, replicas there are, status etc.
You should also check that the nodes are talking to each other
successfully
just to be sure if you haven't done that already.
Regards,
Berkay Mollamustafaoglu
mberkay on yahoo, google and skype
Here's another weird happenstance. On the node that I shutdown,
all
of
the index files disappeared. Poof, gone.
This happened once before too. I realized that I needed more
disk
space so I moved the entire elasticsearch directory ... when I
started
up again, all of the index files were gone.
Shards are allocated between nodes started, and I find it
strange
that
half
your docs disappeared when you shut down one node. They
should
not,
since
you have replicas on the other node. In general, as long as
you
don't
do
full cluster shutdown, you can bring more nodes into play and
then
shut
down
the other nodes. Shards will be allocated automatically
between
the
nodes
(with the replicas).
Do you use unicast discovery in amazon? How do you configure
it?
I currently am running 3 small instance EC2 nodes and I
want to
move
to 2 large EC2 instances.
What is the best way to migrate the data? I brought up a
large
EC2
instance already but if I shut down one of my small
instances,
then
half the documents disappear. Again, I'm not too clear how
the
failover and sharding is working behind the scenes.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.