Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Peer Recovery: remove maxUnsafeAutoIdTimestamp hand off #24243

Merged

Conversation

bleskes
Copy link
Contributor

@bleskes bleskes commented Apr 21, 2017

With #24149 , it is now stored in the Lucene commit and is implicitly transferred in the file phase of the recovery.

@bleskes bleskes added :Distributed Indexing/Recovery Anything around constructing a new shard, either from a local or a remote source. >enhancement v6.0.0-alpha1 labels Apr 21, 2017
@bleskes bleskes requested a review from s1monw April 21, 2017 12:17
Copy link
Contributor

@s1monw s1monw left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM I left one comment please adress it before you push

boolean assertionsEnabled = false;
assert assertionsEnabled = true;
// TODO: add this for shrinked indices.
if (assertionsEnabled && indexExists) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

please move this into a method private boolean assertSomething() and then do assert assertSomething();

@bleskes bleskes merged commit badb2be into elastic:master Apr 21, 2017
@bleskes bleskes deleted the recovery_remove_max_timestamp_transfer branch April 21, 2017 15:31
@bleskes
Copy link
Contributor Author

bleskes commented Apr 21, 2017

thx @s1monw

jasontedor added a commit to jasontedor/elasticsearch that referenced this pull request Apr 21, 2017
* master: (61 commits)
  Build: Move plugin cli and tests to distribution tool (elastic#24220)
  Peer Recovery: remove maxUnsafeAutoIdTimestamp hand off (elastic#24243)
  Adds version 5.3.2 and backwards compatibility indices for 5.3.1
  Add utility method to parse named XContent objects with typed prefix (elastic#24240)
  MultiBucketsAggregation.Bucket should not extend Writeable (elastic#24216)
  Don't expose cleaned-up tasks as pending in PrioritizedEsThreadPoolExecutor (elastic#24237)
  Adds declareNamedObjects methods to ConstructingObjectParser (elastic#24219)
  ESIntegTestCase.indexRandom should not introduce types. (elastic#24202)
  Tests: Extend InternalStatsTests (elastic#24212)
  IndicesQueryCache should delegate the scorerSupplier method. (elastic#24209)
  Speed up parsing of large `terms` queries. (elastic#24210)
  [TEST] make sure that the random query_string query generator defines a default_field or a list of fields
  token_count type : add an option to count tokens (fix elastic#23227) (elastic#24175)
  Query string default field (elastic#24214)
  Make Aggregations an abstract class rather than an interface (elastic#24184)
  [TEST] ensure expected sequence no and version are set when index/delete engine operation has a document failure
  Extract batch executor out of cluster service (elastic#24102)
  Add 5.3.1 to bwc versions
  Added "release-state" support to plugin docs
  Added examples to cross cluster search of using cluster settings
  ...
asettouf pushed a commit to asettouf/elasticsearch that referenced this pull request Apr 23, 2017
With elastic#24149 , it is now stored in the Lucene commit and is implicitly transferred in the file phase of the recovery.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Distributed Indexing/Recovery Anything around constructing a new shard, either from a local or a remote source. >enhancement v6.0.0-alpha1
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants