diff --git a/.github/workflows/main.yml b/.github/workflows/main.yml index 77cbf6a4b..2935927da 100644 --- a/.github/workflows/main.yml +++ b/.github/workflows/main.yml @@ -44,6 +44,5 @@ jobs: - name: Deploy docs run: | mike deploy 7.0 -b publish -p - mike set-default 7.0 -b publish -p - mike retitle 7.0 "7.0.2-1 (LATEST)" -b publish -p + mike retitle 7.0 "7.0.2-1" -b publish -p diff --git a/docs/aws-iam.md b/docs/aws-iam.md index e256b5b1d..8de621608 100644 --- a/docs/aws-iam.md +++ b/docs/aws-iam.md @@ -31,7 +31,7 @@ For either type of AWS IAM authentication, the flow is the following: 4. The AWS STS service validates whether the signature is correct and answers with the user / role ARN that created the signature 5. Percona Server for MongoDB looks for the same username as the received ARN in the `$external` database and grants privileges to access Percona Server for MongoDB as defined for the respective user. -Starting with version [6.0.8-6](release_notes/6.0.8-6.md), you can [configure the AWS STS endpoint](aws-iam-setup.md#configure-aws-sts-endpoint) by specifying the `setParameter.awsStsHost` in the configuration file. This allows you to send requests to the AWS resources of your choice to meet security requirements of your organization and ensure successful authentication. +Starting with version [6.0.8-6](https://docs.percona.com/percona-server-for-mongodb/6.0/release_notes/6.0.8-6.md), you can [configure the AWS STS endpoint](aws-iam-setup.md#configure-aws-sts-endpoint) by specifying the `setParameter.awsStsHost` in the configuration file. This allows you to send requests to the AWS resources of your choice to meet security requirements of your organization and ensure successful authentication. !!! admonition "See also" diff --git a/docs/install/source-fips.md b/docs/install/source-fips.md deleted file mode 100644 index c0c9a4586..000000000 --- a/docs/install/source-fips.md +++ /dev/null @@ -1,316 +0,0 @@ -# Build from source code - -You can build Percona Server for MongoDB from the source code either manually or using the build script. - -## Manual build - -To build Percona Server for MongoDB manually, you need the following: - -- A modern C++ compiler capable of compiling C++17 like GCC 8.2 or newer -- Amazon AWS Software Development Kit for C++ library -- Python 3.7.x and Pip modules. -- The set of dependencies for your operating system. The following table lists dependencies for Ubuntu 22.04 and Red Hat Enterprise 9 and compatible derivatives: - - - | Linux Distribution | Dependencies - | --------------------------------|--------------------------- - | Debian/Ubuntu | gcc g++ cmake curl libssl-dev libldap2-dev libkrb5-dev libcurl4-openssl-dev libsasl2-dev liblz4-dev libbz2-dev libsnappy-dev zlib1g-dev libzlcore-dev liblzma-dev e2fslibs-dev| - | RedHat Enterprise Linux/CentOS 9| gcc gcc-c++ cmake curl openssl-devel openldap-devel krb5-devel libcurl-devel cyrus-sasl-devel bzip2-devel zlib-devel lz4-devel xz-devel e2fsprogs-devel| - -- About 13 GB of disk space for the core binaries (`mongod`, `mongos`, and `mongo`) and about 600 GB for the install-all target. - -### Build steps - -#### Install Python and Python modules - -1. Make sure the `python3`, `python3-dev`, `python3-pip` Python packages are installed on your machine. Otherwise, install them using the package manager of your operating system. - -2. Clone Percona Server for MongoDB repository - - ```{.bash data-prompt="$"} - $ git clone https://github.com/percona/percona-server-mongodb.git - ``` - -3. Switch to the Percona Server for MongoDB branch that you are building - and install Python3 modules - - ```{.bash data-prompt="$"} - $ cd percona-server-mongodb && git checkout v6.0 - $ python3 -m pip install --user -r etc/pip/dev-requirements.txt - ``` - -4. Define Percona Server for MongoDB version (6.0.6 for the time of - writing this document) - - ```{.bash data-prompt="$"} - $ echo '{"version": "6.0.6"}' > version.json - ``` - -#### Install operating system dependencies - -=== "Debian/Ubuntu" - - The following command installs the dependencies for Ubuntu 22.04: - - ```{.bash data-prompt="$"} - $ sudo apt install -y gcc g++ cmake curl libssl-dev libldap2-dev libkrb5-dev libcurl4-openssl-dev libsasl2-dev liblz4-dev libbz2-dev libsnappy-dev zlib1g-dev libzlcore-dev liblzma-dev e2fslibs-dev - ``` - -=== "RHEL / CentOS" - - The following command installs the dependencies for CentOS 9: - - ```{.bash data-prompt="$"} - $ sudo yum -y install gcc gcc-c++ cmake curl openssl-devel openldap-devel krb5-devel libcurl-devel cyrus-sasl-devel bzip2-devel zlib-devel lz4-devel xz-devel e2fsprogs-devel - ``` - -#### Build AWS Software Development Kit for C++ library - -1. Clone the AWS Software Development Kit for C++ repository - - ```{.bash data-prompt="$"} - $ git clone --recurse-submodules https://github.com/aws/aws-sdk-cpp.git - ``` - -2. Create a directory to store the AWS library - - ```{.bash data-prompt="$"} - $ mkdir -p /tmp/lib/aws - ``` - -3. Declare an environment variable ``AWS_LIBS`` for this directory - ```{.bash data-prompt="$"} - $ export AWS_LIBS=/tmp/lib/aws - ``` - -4. Percona Server for MongoDB is built with AWS SDK CPP 1.9.379 - version. Switch to this version - - ```{.bash data-prompt="$"} - $ cd aws-sdk-cpp && git checkout 1.9.379 - ``` - -5. It is recommended to keep build files outside the SDK directory. - Create a build directory and navigate to it - - ```{.bash data-prompt="$"} - $ mkdir build && cd build - ``` - -6. Generate build files using ``cmake`` - - ```{.bash data-prompt="$"} - $ cmake .. -DCMAKE_BUILD_TYPE=Release '-DBUILD_ONLY=s3;transfer' -DBUILD_SHARED_LIBS=OFF -DMINIMIZE_SIZE=ON -DCMAKE_INSTALL_PREFIX="${AWS_LIBS}" - ``` - -7. Install the SDK - - ```{.bash data-prompt="$"} - $ make install - ``` - -#### Build Percona Server for MongoDB - -1. Change directory to ``percona-server-mongodb`` - - ```{.bash data-prompt="$"} - $ cd percona-server-mongodb - ``` - -2. Build Percona Server for MongoDB from ``buildscripts/scons.py`` - - === "Without FIPS mode" - - ```{.bash data-prompt="$"} - $ buildscripts/scons.py --disable-warnings-as-errors --release --ssl --opt=on -j$(nproc --all) --use-sasl-client --wiredtiger --audit --inmemory --hotbackup CPPPATH="${AWS_LIBS}/include" LIBPATH="${AWS_LIBS}/lib ${AWS_LIBS}/lib64" install-mongod install-mongos - ``` - - === "With FIPS mode" - - ```{.bash data-prompt="$"} - $ buildscripts/scons.py --disable-warnings-as-errors --release --ssl --opt=on -j$(nproc --all) --use-sasl-client --wiredtiger --audit --inmemory --hotbackup --enable-fipsmode CPPPATH="${AWS_LIBS}/include" LIBPATH="${AWS_LIBS}/lib ${AWS_LIBS}/lib64" install-mongod install-mongos - ``` - - This command builds core components of the database. Other available targets for the - ``scons`` command are: - - - `install-mongod` - - `install-mongos` - - `install-servers` (includes mongod and mongos) - - `install-core` (includes mongod and mongos) - - `install-devcore` (includes mongod, mongos, and jstestshell (formerly mongo shell)) - - `install-all` - -The built binaries are in the ``percona-server-mongodb`` directory. - -## Use the build script - -To automate the build process, Percona provides the build script. With this script you can either build binary tarballs or DEB/RPM packages to install Percona Server for MongoDB from. - -### Prerequisites - -To use the build script you need the following: - -* Docker up and running on your machine -* About 200GB of disk space - -### Prepare the build environment - -1. Create the folder where all build actions take place. For the steps below we use the `/tmp/psmdb/test` folder. -2. Navigate to the build folder and download the build script. Replace the `` placeholder with the required version of Percona Server for MongoDB: - - ```{.bash data-prompt="$"} - $ wget https://raw.githubusercontent.com/percona/percona-server-mongodb/psmdb-/percona-packaging/scripts/psmdb_builder.sh -O psmdb_builder.sh - ``` - -### Build steps - -Use the following instructions depending on what you wish to build: - -=== "Build tarballs" - - The following command builds tarballs of Percona Server for MongoDB 6.0.6-5 on Red Hat Enterprise Linux 9. Change the Docker image and the values for `--branch`, `--psm_ver`, `--psm_release` flags to build tarballs of a different version and on a different operating system. - - ```{.bash data-prompt="$"} - $ docker run -ti -u root -v /tmp/psmdb:/tmp/psmdb rhel:9 sh -c ' - set -o xtrace - cd /tmp/psmdb - bash -x ./psmdb_builder.sh --builddir=/tmp/psmdb/test --install_deps=1 - bash -x ./psmdb_builder.sh --builddir=/tmp/psmdb/test --repo=https://github.com/percona/percona-server-mongodb.git \ - --branch=release-6.0.6-5 --psm_ver=6.0.6 --psm_release=5 --mongo_tools_tag=100.7.0 --jemalloc_tag=psmdb-3.2.11-3.1 --get_sources=1 - ' - ``` - - The command does the following: - - * runs Docker daemon as the root user using the RHEL 9 image - * mounts the build directory into the container - * establishes the shell session inside the container - * inside the container, navigates to the build directory and runs the build script to install dependencies - * runs the build script again to build the tarball for the PSMDB version 6.0.6-5 - - Check that tarballs are built: - - ```{.bash data-prompt="$"} - $ ls -la /tmp/psmdb/test/source_tarball/ - ``` - - Sample output: - - ```{.text .no-copy} - total 88292 - -rw-r--r--. 1 root root 90398894 Jul 1 10:58 percona-server-mongodb-6.0.6-5.tar.gz - ``` - -=== "Build packages" - - 1. Build source packages - - === "DEB" - - ```{.bash data-prompt="$"} - $ docker run -ti -u root -v /tmp/psmdb:/tmp/psmdb ubuntu:jammy sh -c ' - set -o xtrace - cd /tmp/psmdb - bash -x ./psmdb_builder.sh --builddir=/tmp/psmdb/test --install_deps=1 - bash -x ./psmdb_builder.sh --builddir=/tmp/psmdb/test --repo=https://github.com/percona/percona-server-mongodb.git \ - --branch=release-6.0.6-5 --psm_ver=6.0.6--psm_release=5 --mongo_tools_tag=100.7.0 --jemalloc_tag=psmdb-3.2.11-3.1 --build_src_deb=1 - ' - ``` - - Check that source packages are created - - ```{.bash data-prompt="$"} - $ ls -la /tmp/psmdb/test/source_deb/ - ``` - - Sample output: - - ```{.text .no-copy} - rw-r--r--. 1 root root 90398894 Jul 1 11:45 percona-server-mongodb_6.0.6.orig.tar.gz - ``` - - === "RPM" - - ```{.bash data-prompt="$"} - $ docker run -ti -u root -v /tmp/psmdb:/tmp/psmdb ubuntu:jammy sh -c ' - set -o xtrace - cd /tmp/psmdb - bash -x ./psmdb_builder.sh --builddir=/tmp/psmdb/test --install_deps=1 - bash -x ./psmdb_builder.sh --builddir=/tmp/psmdb/test --repo=https://github.com/percona/percona-server-mongodb.git \ - --branch=release-6.0.6-5 --psm_ver=6.0.6--psm_release=5 --mongo_tools_tag=100.7.0 --jemalloc_tag=psmdb-3.2.11-3.1 --build_src_rpm=1 - ' - ``` - - Check that source packages are created - - ```{.bash data-prompt="$"} - $ ls -la /tmp/psmdb/test/srpm/ - ``` - - Sample output: - - ```{.text .no-copy} - rw-r--r--. 1 root root 90398894 Jul 1 11:45 percona-server-mongodb-6.0.6-5.generic.src.rpm - ``` - - 2. Build Percona Server for MongoDB packages - - === "DEB" - - ```{.bash data-prompt="$"} - $ docker run -ti -u root -v /tmp/psmdb:/tmp/psmdb ubuntu:jammy sh -c ' - set -o xtrace - cd /tmp/psmdb - bash -x ./psmdb_builder.sh --builddir=/tmp/psmdb/test --install_deps=1 - bash -x ./psmdb_builder.sh --builddir=/tmp/psmdb/test --repo=https://github.com/percona/percona-server-mongodb.git \ - --branch=release-6.0.6-5 --psm_ver=6.0.6 --psm_release=5 --mongo_tools_tag=100.7.0 --jemalloc_tag=psmdb-3.2.11-3.1 --build_deb=1 - ' - ``` - - Check that source packages are created - - ```{.bash data-prompt="$"} - $ ls -la /tmp/psmdb/test/deb/ - ``` - - Sample output: - - ```{.text .no-copy} - rw-r--r--. 1 root root 90398894 Jul 1 13:16 percona-server-mongodb-dbg_6.0.6-5.jammy_amd64.deb - rw-r--r--. 1 root root 90398894 Jul 1 13:16 percona-server-mongodb-mongos_6.0.6-5.jammy_amd64.deb - rw-r--r--. 1 root root 90398894 Jul 1 13:16 percona-server-mongodb-server_6.0.6-5.jammy_amd64.deb - rw-r--r--. 1 root root 90398894 Jul 1 13:16 percona-server-mongodb-tools_6.0.6-5.jammy_amd64.deb - rw-r--r--. 1 root root 90398894 Jul 1 13:16 percona-server-mongodb_6.0.6-5.jammy_amd64.deb - ``` - - === "RPM" - - ```{.bash data-prompt="$"} - $ docker run -ti -u root -v /tmp/psmdb:/tmp/psmdb ubuntu:jammy sh -c ' - set -o xtrace - cd /tmp/psmdb - bash -x ./psmdb_builder.sh --builddir=/tmp/psmdb/test --install_deps=1 - bash -x ./psmdb_builder.sh --builddir=/tmp/psmdb/test --repo=https://github.com/percona/percona-server-mongodb.git \ - --branch=release-6.0.6-5 --psm_ver=6.0.6 --psm_release=5 --mongo_tools_tag=100.7.0 --jemalloc_tag=psmdb-3.2.11-3.1 --build_rpm=1 - ' - ``` - - Check that source packages are created - - ```{.bash data-prompt="$"} - $ ls -la /tmp/psmdb/test/srpm/ - ``` - - Sample output: - - ```{.text .no-copy} - rw-r--r--. 1 root root 90398894 Jul 1 13:16 percona-server-mongodb-6.0.6-5.el8.x86_64.rpm - rw-r--r--. 1 root root 90398894 Jul 1 13:16 percona-server-mongodb-debugsource-6.0.6-5.el8.x86_64.rpm - rw-r--r--. 1 root root 90398894 Jul 1 13:16 percona-server-mongodb-mongos-6.0.6-5.el8.x86_64.rpm - rw-r--r--. 1 root root 90398894 Jul 1 13:16 percona-server-mongodb-mongos-debuginfo-6.0.6-5.el8.x86_64.rpm - rw-r--r--. 1 root root 90398894 Jul 1 13:16 percona-server-mongodb-server-6.0.6-5.el8.x86_64.rpm - rw-r--r--. 1 root root 90398894 Jul 1 13:16 percona-server-mongodb-server-debuginfo-6.0.6-5.el8.x86_64.rpm - rw-r--r--. 1 root root 90398894 Jul 1 13:16 percona-server-mongodb-tools-6.0.6-5.el8.x86_64.rpm - rw-r--r--. 1 root root 90398894 Jul 1 13:16 percona-server-mongodb-tools-debuginfo-6.0.6-5.el8.x86_64.rpm - ``` diff --git a/docs/release_notes/7.0.2-1.md b/docs/release_notes/7.0.2-1.md new file mode 100644 index 000000000..daa081fd3 --- /dev/null +++ b/docs/release_notes/7.0.2-1.md @@ -0,0 +1,49 @@ +# Percona Server for MongoDB 7.0.2-1 (Release Candidate) (2023-10-05) + +[Installation](../install/index.md){.md-button} + +We are pleased to announce the release candidate of the new major version of Percona Server for MongoDB 7.0.2-1 – the drop in replacement for MongoDB Community Edition. Percona Server for MongoDB supports MongoDB community protocols and drivers and enhances it with the [enterprise-grade features for free](../comparison.md), enabling you to effectively meet the requirements of your organization in terms of high-availability, reliability and data security. + +## Upgrade considerations + +Starting with version 7.0, Percona Server for MongoDB enables journaling by default. Both the `storage.journal.enabled` configuration option and the corresponding `--journal`, `--no-journal` command-line options are now ignored. You receive the corresponding warning during the server start after the upgrade. To get rid of this warning, change your configuration to remove the journaling options. See the [upgrade guide](../install/upgrade-from-60.md) for exact procedure. + +## Release Highlights + +MongoDB 7.0 introduces a lot of major changes. We recommend testing it on staging environments before using it in production. The features and improvements in MongoDB 7.0 are focused on the following main areas: + +### Streamlined development process + +* Using the new system variable [$USER_ROLES](https://www.mongodb.com/docs/v7.0/reference/aggregation-variables/#mongodb-variable-variable.USER_ROLES) you can build a single dynamic view instead of multiple static views to control access to data depending on the user’s roles and permissions. +* [Compound wildcard indexes](https://www.mongodb.com/docs/v7.0/core/indexes/index-types/index-wildcard/index-wildcard-compound/#std-label-wildcard-index-compound) enable you to filter documents that have common but not identical attributes. You can build a compound wildcard index on an always-present field as well as on one or more arbitrary fields thus reducing the number of indexes on a collection. This also simplifies coding of your application to work with such collections. +* You can now [selectively delete one or more documents within time series collections](https://www.mongodb.com/docs/v7.0/core/timeseries/timeseries-limitations/#deletes). Partial TTL indexes enable you to age out your data in a more controlled way. +* The new [`$percentile`](https://www.mongodb.com/docs/v7.0/reference/operator/aggregation/percentile/#mongodb-group-grp.-percentile), [`$median`](https://www.mongodb.com/docs/v7.0/reference/operator/aggregation/median/#mongodb-group-grp.-median) and bitwise aggregation operators improve processing and operation with the stats data. +* The fsync is now added for `mongos` to be used more in sharded clusters and for making backups. + +### Optimized performance + +* Added support for processing large documents for event-driven solutions: you can now split the [change streams events](https://www.mongodb.com/docs/v7.0/changeStreams/#std-label-changeStreams) that exceed 16MB into fragments and then put them together to process as a whole. +* New commands [`analyzeShardKey`](https://www.mongodb.com/docs/v7.0/reference/command/analyzeShardKey/#mongodb-dbcommand-dbcmd.analyzeShardKey) and [`configureQueryAnalyzer`](https://www.mongodb.com/docs/v7.0/reference/command/configureQueryAnalyzer/#mongodb-dbcommand-dbcmd.configureQueryAnalyzer) for sharded collections help you evaluate the shard key in terms of best read and write distribution. +* The [AutoMerger](https://www.mongodb.com/docs/v7.0/core/automerger-concept/#std-label-automerger-concept) now merges contiguous chunks that reside on the same shard. This reduces the sharding table, avoids unnecessary chunk migrations and improves overall performance. The AutoMerger is enabled by default. +* The `findOne`, `updateOne` and `deleteOne` command behavior is now aligned for both sharded and unsharded collections. This allows you to run these commands without having to target a specific shard. This comes handy when you need to update documents on multiple shards and you don’t know exactly on what shard the data resides. + +### Security + +* Improve security and safety of your sensitive data with [queryable encryption](https://www.mongodb.com/docs/v7.0/core/queryable-encryption/#std-label-qe-manual-feature-qe). This mechanism enables you to encrypt/decrpyt the data on the client side, store it as encrypted on the database and run queries against the encrypted data. This way your data remains encrypted and secure throughout its whole lifecycle. The community edition supports explicit encryption only. +* SSL 3.0 is the default standard ensuring you to use the latest security standards + +Other improvements include the following: + +* [SERVER-71627](https://jira.mongodb.org/browse/SERVER-71627) - Improved performance of updating the routing table and prevented blocking client requests during refresh for clusters with 1 million of chunks +* [SERVER-77183](https://jira.mongodb.org/browse/SERVER-77183) - Fixed incorrect results when $project is followed by $group and the group doesn't require full document +* [SERVER-74954](https://jira.mongodb.org/browse/SERVER-74954) - Fixed the issue with the incorrect output for the query where the $or operator rewrites the $elemMatch extra condition. +* [SERVER-79771](https://jira.mongodb.org/browse/SERVER-79771) - Made Resharding Operation Resilient to NetworkInterfaceExceededTimeLimit +* [SERVER-79982](https://jira.mongodb.org/browse/SERVER-79982) - Fixed the issue with possibel server crash and data inconsistency when returning the results of the `find` command by timestamp monitor to take global lock when cleaning up batched catalog writers +* [SERVER-80488](https://jira.mongodb.org/browse/SERVER-80488) - Avoided traversing routing table in balancer split chunk policy +* [SERVER-78150](https://jira.mongodb.org/browse/SERVER-78150) - Implemented the mongos `fsyncUnlock` command +* [SERVER-79025](https://jira.mongodb.org/browse/SERVER-79025) - Added the ability for mongos to unlock the locked shards using its fsync Unlock functionality. + +## Packaging changes + +Percona Server for MongoDB 7.0.2-1 is available on Debian 12 (bookworm) in addition to other [supported platforms](https://www.percona.com/services/policies/percona-software-platform-lifecycle#mongodb). + diff --git a/docs/release_notes/index.md b/docs/release_notes/index.md index eaee71caa..09dcac3d3 100644 --- a/docs/release_notes/index.md +++ b/docs/release_notes/index.md @@ -1,3 +1,5 @@ + # Percona Server for MongoDB 7.0 release notes + * [Percona Server for MongoDB 7.0.2-1 (2023-10-05)](7.0.2-1.md) \ No newline at end of file diff --git a/docs/vault.md b/docs/vault.md index 812d5f067..bf6aee0fe 100644 --- a/docs/vault.md +++ b/docs/vault.md @@ -17,7 +17,7 @@ with versioning enabled. | vaultServerName | security.vault.serverName | string | The IP address of the Vault server| | vaultPort | security.vault.port | int | The port on the Vault server| | vaultTokenFile | security.vault.tokenFile | string | The path to the vault token file. The token file is used by MongoDB to access HashiCorp Vault. The vault token file consists of the raw vault token and does not include any additional strings or parameters.

Example of a vault token file:

`s.uTrHtzsZnEE7KyHeA797CkWA`| -| vaultSecret | security.vault.secret | string | The path to the Vault secret. The Vault secret path format must be ```/data/```

where:
- ```` is the path to the Key/Value Secrets Engine v2;
- ``data`` is the mandatory path prefix required by Version 2 API;
- ```` is the path to the specific secret.

Example: `secret_v2/data/psmdb-test/rs1-27017`

Starting with version [6.0.5-4](release_notes/6.0.5-4.md), a distinct Vault secret path for every replica set member is no longer mandatory. In earlier versions, it is recommended to use different secret paths for every database node in the entire deployment to avoid issues during the master key rotation.| +| vaultSecret | security.vault.secret | string | The path to the Vault secret. The Vault secret path format must be ```/data/```

where:
- ```` is the path to the Key/Value Secrets Engine v2;
- ``data`` is the mandatory path prefix required by Version 2 API;
- ```` is the path to the specific secret.

Example: `secret_v2/data/psmdb-test/rs1-27017`

Starting with version [6.0.5-4](https://docs.percona.com/percona-server-for-mongodb/6.0/release_notes/6.0.5-4.md), a distinct Vault secret path for every replica set member is no longer mandatory. In earlier versions, it is recommended to use different secret paths for every database node in the entire deployment to avoid issues during the master key rotation.| | vaultSecretVersion | security.vault.
secretVersion | unsigned long | (Optional) The version of the Vault secret to use | | vaultRotateMasterKey | security.vault.
rotateMasterKey| switch | When enabled, rotates the master key and exits | | vaultServerCAFile | security.vault.
serverCAFile | string | The path to the TLS certificate file | @@ -90,7 +90,7 @@ Rotating the master key process also re-encrypts the keystore using the new mast ### Key rotation in replica sets -Starting with version [6.0.5-4](release_notes/6.0.5-4.md), you can store the master key at the same path on every replica set member in your entire deployment. Vault assigns different versions to the master keys stored at the same path. The path and the version serve as the unique identifier of a master key. The `mongod` server stores that identifier and uses it to retrieve the correct master key from the Vault server during the restart. +Starting with version [6.0.5-4](https://docs.percona.com/percona-server-for-mongodb/6.0/release_notes/6.0.5-4.md), you can store the master key at the same path on every replica set member in your entire deployment. Vault assigns different versions to the master keys stored at the same path. The path and the version serve as the unique identifier of a master key. The `mongod` server stores that identifier and uses it to retrieve the correct master key from the Vault server during the restart. The key rotation steps are the following: diff --git a/mkdocs.yml b/mkdocs.yml index 8b802f8aa..2fb5dab8e 100644 --- a/mkdocs.yml +++ b/mkdocs.yml @@ -25,3 +25,4 @@ extra: note: >- Thank you for your feedback! Help us improve by following this feedback form. + diff --git a/variables.yml b/variables.yml index 4994c4e4a..b815a96fb 100644 --- a/variables.yml +++ b/variables.yml @@ -2,4 +2,5 @@ # See also mkdocs.yml plugins.with-pdf.cover_subtitle and output_path release: '7.0.2-1' -version: '7.0' +version: '7.0' +