Refactor indices aliases

.ci/jobs.t/elastic+elasticsearch+pull-request+example-plugins.yml

@@ -0,0 +1,34 @@
+---
+- job:
+    name: "elastic+elasticsearch+pull-request+example-plugins"
+    display-name: "elastic / elasticsearch - pull request example-plugins"
+    description: "Testing of Elasticsearch pull requests - example-plugins"
+    workspace: "/dev/shm/elastic+elasticsearch+pull-request+example-plugins"
+    scm:
+      - git:
+          refspec: "+refs/pull/${ghprbPullId}/*:refs/remotes/origin/pr/${ghprbPullId}/*"
+          branches:
+            - "${ghprbActualCommit}"
+    triggers:
+      - github-pull-request:
+          org-list:
+            - elastic
+          allow-whitelist-orgs-as-admins: true
+          trigger-phrase: '.*run\W+elasticsearch-ci/example-plugins.*'
+          github-hooks: true
+          status-context: elasticsearch-ci/example-plugins
+          cancel-builds-on-update: true
+          white-list-labels:
+            - ':Delivery/Build'
+    builders:
+      - inject:
+          properties-file: '.ci/java-versions.properties'
+          properties-content: |
+            JAVA_HOME=$HOME/.java/$ES_BUILD_JAVA
+            JAVA8_HOME=$HOME/.java/java8
+            JAVA11_HOME=$HOME/.java/java11
+            RUNTIME_JAVA_HOME=$HOME/.java/$ES_RUNTIME_JAVA
+      - shell: |
+          #!/usr/local/bin/runbld --redirect-stderr
+          cd plugins/examples
+          $WORKSPACE/.ci/scripts/run-gradle.sh -Dorg.gradle.jvmargs=-Xmx8g build --include-build $WORKSPACE

TESTING.asciidoc

@@ -3,28 +3,37 @@
 
 [partintro]
 
-Elasticsearch uses jUnit for testing, it also uses randomness in the
-tests, that can be set using a seed, the following is a cheatsheet of
-options for running the tests for ES.
+Elasticsearch uses JUnit for testing. It also generated random inputs into
+tests, either using a random seed, or one that is set via a system
+property. The following is a cheatsheet of options for running the
+Elasticsearch tests.
 
 == Creating packages
 
-To create a distribution without running the tests, simply run the
-following:
+To build a distribution for your local OS and print its output location upon completion, run:
 
 -----------------------------
-./gradlew assemble
+./gradlew localDistro
 -----------------------------
 
-To create a platform-specific build including the x-pack modules, use the
-following depending on your operating system:
+To create a platform-specific build, use the following depending on your
+operating system:
 
 -----------------------------
 ./gradlew :distribution:archives:linux-tar:assemble
-./gradlew :distribution:archives:darwin-tar:assemble
+./gradlew :distribution:archives:darwin(-aarch64)-tar:assemble
 ./gradlew :distribution:archives:windows-zip:assemble
 -----------------------------
 
+You can build a Docker image with:
+
+-----------------------------
+./gradlew build(Aarch64)DockerImage
+-----------------------------
+
+Note: you almost certainly don't want to run `./gradlew assemble` as this
+will attempt build every single Elasticsearch distribtion.
+
 === Running Elasticsearch from a checkout
 
 In order to run Elasticsearch from source without building a package, you can

build-tools/src/main/java/org/elasticsearch/gradle/plugin/PluginBuildPlugin.java

@@ -144,6 +144,7 @@ private static void configureDependencies(final Project project) {
         var dependencies = project.getDependencies();
         dependencies.add("compileOnly", "org.elasticsearch:elasticsearch:" + VersionProperties.getElasticsearch());
         dependencies.add("testImplementation", "org.elasticsearch.test:framework:" + VersionProperties.getElasticsearch());
+        dependencies.add("testImplementation", "org.apache.logging.log4j:log4j-core:" + VersionProperties.getVersions().get("log4j"));
 
         // we "upgrade" these optional deps to provided for plugins, since they will run
         // with a full elasticsearch server that includes optional deps

docs/Versions.asciidoc

@@ -68,3 +68,7 @@ ifeval::["{source_branch}"=="7.x"]
 :apm-server-ref-v:     {apm-server-ref-m}
 :apm-overview-ref-v:   {apm-overview-ref-m}
 endif::[]
+
+// Max recommended snapshots in a snapshot repo.
+// Used in the snapshot/restore docs.
+:max-snapshot-count: 200

docs/plugins/repository-s3.asciidoc

@@ -215,9 +215,9 @@ include a port. For example, the endpoint may be `172.17.0.2` or
 `172.17.0.2:9000`. You may also need to set `s3.client.CLIENT_NAME.protocol` to
 `http` if the endpoint does not support HTTPS.
 
-https://minio.io[Minio] is an example of a storage system that provides an
+https://minio.io[MinIO] is an example of a storage system that provides an
 S3-compatible API. The `repository-s3` plugin allows {es} to work with
-Minio-backed repositories as well as repositories stored on AWS S3. Other
+MinIO-backed repositories as well as repositories stored on AWS S3. Other
 S3-compatible storage systems may also work with {es}, but these are not
 covered by the {es} test suite.
 

docs/reference/high-availability.asciidoc

@@ -21,12 +21,10 @@ to achieve high availability despite failures.
   to serve searches from nearby clients.
 
 * The last line of defence against data loss is to take
-  <<backup-cluster,regular snapshots>> of your cluster so that you can restore
-  a completely fresh copy of it elsewhere if needed.
+  <<snapshots-take-snapshot,regular snapshots>> of your cluster so that you can
+  restore a completely fresh copy of it elsewhere if needed.
 --
 
 include::high-availability/cluster-design.asciidoc[]
 
-include::high-availability/backup-cluster.asciidoc[]
-
 include::ccr/index.asciidoc[]