-
Notifications
You must be signed in to change notification settings - Fork 24.8k
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
Default to one shard #30539
Default to one shard #30539
Commits on May 11, 2018
-
This commit changes the default out-of-the-box configuration for the number of shards from five to one. We think this will help address a common problem of oversharding. For users with time-based indices that need a different default, this can be managed with index templates. For users with non-time-based indices that find they need to re-shard with the shrink API in place they no longer need to resort only to reindexing. Since this has the impact of changing the default number of shards used in REST tests, we want to ensure that we still have coverage for issues that could arise from multiple shards. As such, we randomize (rarely) the default number of shards in REST tests to two. This is managed via a global index template. However, some tests check the templates that are in the cluster state during the test. Since this template is randomly there, we need a way for tests to skip adding the template used to set the number of shards to two. For this we add the default_shards feature skip. To avoid having to write our docs in a complicated way because sometimes they might be behind one shard, and sometimes they might be behind two shards we apply the default_shards feature skip to all docs tests. That is, these tests will always run with the default number of shards (one).
Configuration menu - View commit details
-
Copy full SHA for 0b8ea07 - Browse repository at this point
Copy the full SHA 0b8ea07View commit details -
This commit fixes a few issues in the REST client tests that arose from moving to one shard. Moving to one shard causes a reordering of calculations which impacts floating-point arithmetic. It can also impact scoring and thus the ranking of docs.
Configuration menu - View commit details
-
Copy full SHA for 3c16228 - Browse repository at this point
Copy the full SHA 3c16228View commit details -
Fix SQL test expecting five shards
This commit fixes a SQL test with security that was expecting five shards.
Configuration menu - View commit details
-
Copy full SHA for da5ddb3 - Browse repository at this point
Copy the full SHA da5ddb3View commit details -
Configuration menu - View commit details
-
Copy full SHA for 446e85b - Browse repository at this point
Copy the full SHA 446e85bView commit details -
Configuration menu - View commit details
-
Copy full SHA for 2e89d98 - Browse repository at this point
Copy the full SHA 2e89d98View commit details -
Configuration menu - View commit details
-
Copy full SHA for e9ec5f9 - Browse repository at this point
Copy the full SHA e9ec5f9View commit details -
Configuration menu - View commit details
-
Copy full SHA for 872f73f - Browse repository at this point
Copy the full SHA 872f73fView commit details -
Configuration menu - View commit details
-
Copy full SHA for 00c32ae - Browse repository at this point
Copy the full SHA 00c32aeView commit details
Commits on May 12, 2018
-
Configuration menu - View commit details
-
Copy full SHA for 85429b5 - Browse repository at this point
Copy the full SHA 85429b5View commit details -
Configuration menu - View commit details
-
Copy full SHA for 801f7f0 - Browse repository at this point
Copy the full SHA 801f7f0View commit details -
Configuration menu - View commit details
-
Copy full SHA for 68c138c - Browse repository at this point
Copy the full SHA 68c138cView commit details -
Configuration menu - View commit details
-
Copy full SHA for 09108a1 - Browse repository at this point
Copy the full SHA 09108a1View commit details
Commits on May 13, 2018
-
Fix multi-cluster search test with two shards
Let us just hard code the test to always use one shard, it is easier that way.
Configuration menu - View commit details
-
Copy full SHA for e5b0f49 - Browse repository at this point
Copy the full SHA e5b0f49View commit details -
Merge branch 'master' into one-shard-to-rule-them-all
* master: Deprecate not copy settings and explicitly disallow (elastic#30404) [ML] Improve state persistence log message Build: Add mavenPlugin cluster configuration method (elastic#30541) Re-enable FlushIT tests Bump Gradle heap to 2 GB (elastic#30535) SQL: Use request flavored methods in tests (elastic#30345)
Configuration menu - View commit details
-
Copy full SHA for a9c78f8 - Browse repository at this point
Copy the full SHA a9c78f8View commit details
Commits on May 14, 2018
-
Merge branch 'master' into one-shard-to-rule-them-all
* master: Adjust copy settings versions Mute ShrinkIndexIT suite SQL: SYS TABLES ordered according to *DBC specs (elastic#30530)
Configuration menu - View commit details
-
Copy full SHA for 21f87f2 - Browse repository at this point
Copy the full SHA 21f87f2View commit details -
Configuration menu - View commit details
-
Copy full SHA for 4852f34 - Browse repository at this point
Copy the full SHA 4852f34View commit details -
Merge remote-tracking branch 'elastic/master' into one-shard-to-rule-…
…them-all * elastic/master: Add missing dependencies on testClasses (elastic#30527) [TEST] Mute ML test that needs updating to following ml-cpp changes Document woes between auto-expand-replicas and allocation filtering (elastic#30531) Moved tokenizers to analysis common module (elastic#30538)
Configuration menu - View commit details
-
Copy full SHA for 6b30d4a - Browse repository at this point
Copy the full SHA 6b30d4aView commit details