-
Notifications
You must be signed in to change notification settings - Fork 61
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
Integ test: forcemerge and snapshot on leader during bootstrap #76
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me, have a minor comment.
//flush the index | ||
clusterClient.indices().flush(FlushRequest(indexName), RequestOptions.DEFAULT) | ||
} | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Add new line.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tests look good. Suggested an alternate in case we want to increase probability of hitting our test clause.
How long do these take approximately?
try { | ||
followerClient.startReplication(StartReplicationRequest("source", leaderIndexName, followerIndexName), | ||
TimeValue.timeValueSeconds(10), | ||
false) | ||
//Given the size of index, the replication should be in RESTORING phase at this point | ||
leaderClient.indices().forcemerge(ForceMergeRequest(leaderIndexName), RequestOptions.DEFAULT) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would replication chunk size give us better probability of assurance? We can set that to a small number and be assured it worked, and we can probably increase it too to later complete the test faster.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How long do these take approximately?
It takes approx 30 sec for this test: around 10 sec to fill index with data and around 10 sec to verify the document count at follower side.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The suggested setting plugins.replication.index.recovery.chunk_size
takes min value as 1MB. So it is not possible to set a small chunk size like 1B. With 1MB chunk size, we still need to index large amount of data.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Signed-off-by: Sooraj Sinha <[email protected]>
fb55e8a
Description
Add integ tests
Check List
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.