When adding a new node to a cluster, is there a way to prevent it from having
to copy all the data from the other nodes?
We tried to copy the data on disk from an existing node (one that had all the
data for the given indices), but it still copied everything. Is there a way to
make it update what is new only?
It doesn't copy everything, only what it needs to balance the shards.
On 20 November 2014 17:20, Yves Dorfsman yves@zioup.com wrote:
When adding a new node to a cluster, is there a way to prevent it from
having
to copy all the data from the other nodes?
We tried to copy the data on disk from an existing node (one that had all
the
data for the given indices), but it still copied everything. Is there a
way to
make it update what is new only?
So if a shard has been updated since the data copy, will it copy the entire
shard, or just update it?
On Wednesday, 19 November 2014 23:34:01 UTC-7, Mark Walkom wrote:
It doesn't copy everything, only what it needs to balance the shards.
On 20 November 2014 17:20, Yves Dorfsman <yv...@zioup.com <javascript:>>
wrote:
When adding a new node to a cluster, is there a way to prevent it from
having
to copy all the data from the other nodes?
We tried to copy the data on disk from an existing node (one that had all
the
data for the given indices), but it still copied everything. Is there a
way to
make it update what is new only?
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.