Sequence Numbers for Replica Recovery


(Chris Rimondi) #1

In a blog post last
month, http://www.elasticsearch.org/blog/resiliency-elasticsearch/, Shay
pointed out that with Lucene 4.8 Elasticsearch will start using sequence
numbers for operations on priimary shards. This will speed up recovery so
only data that has changed need be copied on recovery. It is unclear to me
reading the 1.2 release notes whether that has been implemented or if so
where it is on the roadmap. Any more information on this?

Thanks,

Chris

--
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 elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/6f8dfcd9-7258-4f1b-a33a-efe72358daa3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


(Ivan Brusic) #2

My understanding is that Lucene now provides checksums, but that sequence
numbers is a functionality built into Elasticsearch.

I do not think that functionality has been released with 1.2, but I could
be wrong. The item below it, zen discovery, is definitely not part of 1.2

--
Ivan

On Tue, May 27, 2014 at 7:36 AM, Chris Rimondi chris.rimondi@gmail.comwrote:

In a blog post last month,
http://www.elasticsearch.org/blog/resiliency-elasticsearch/, Shay pointed
out that with Lucene 4.8 Elasticsearch will start using sequence numbers
for operations on priimary shards. This will speed up recovery so only data
that has changed need be copied on recovery. It is unclear to me reading
the 1.2 release notes whether that has been implemented or if so where it
is on the roadmap. Any more information on this?

Thanks,

Chris

--
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 elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/6f8dfcd9-7258-4f1b-a33a-efe72358daa3%40googlegroups.comhttps://groups.google.com/d/msgid/elasticsearch/6f8dfcd9-7258-4f1b-a33a-efe72358daa3%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

--
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 elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CALY%3DcQC4S1Z1gp-ECBtMLkgtdUEyAK9noVFxvFNH0_SGooqRZQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


(Jörg Prante) #3

I'm not sure if this is related but there is work on designing sequence
numbers that are decentralized time based UUIDs. If they were assigned to
Lucene segments, shards could declare what segments they already have, when
a recovery process runs. Feature is planned for 1.3

Jörg

On Wed, May 28, 2014 at 7:01 AM, Ivan Brusic ivan@brusic.com wrote:

My understanding is that Lucene now provides checksums, but that sequence
numbers is a functionality built into Elasticsearch.

I do not think that functionality has been released with 1.2, but I could
be wrong. The item below it, zen discovery, is definitely not part of 1.2

--
Ivan

On Tue, May 27, 2014 at 7:36 AM, Chris Rimondi chris.rimondi@gmail.comwrote:

In a blog post last month,
http://www.elasticsearch.org/blog/resiliency-elasticsearch/, Shay
pointed out that with Lucene 4.8 Elasticsearch will start using sequence
numbers for operations on priimary shards. This will speed up recovery so
only data that has changed need be copied on recovery. It is unclear to me
reading the 1.2 release notes whether that has been implemented or if so
where it is on the roadmap. Any more information on this?

Thanks,

Chris

--
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 elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/6f8dfcd9-7258-4f1b-a33a-efe72358daa3%40googlegroups.comhttps://groups.google.com/d/msgid/elasticsearch/6f8dfcd9-7258-4f1b-a33a-efe72358daa3%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

--
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 elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/CALY%3DcQC4S1Z1gp-ECBtMLkgtdUEyAK9noVFxvFNH0_SGooqRZQ%40mail.gmail.comhttps://groups.google.com/d/msgid/elasticsearch/CALY%3DcQC4S1Z1gp-ECBtMLkgtdUEyAK9noVFxvFNH0_SGooqRZQ%40mail.gmail.com?utm_medium=email&utm_source=footer
.

For more options, visit https://groups.google.com/d/optout.

--
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 elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAKdsXoEsm3cTs4dqREKVCv-KT246m1U%2BSbo_aQhoVfbUEV8CBw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


(system) #4