Skip to content

REL-1333039: Add step to verify ESIndexCreationSettings shard/replica #70

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.

Sign up for GitHub

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

Open
deepankarrelativity002 wants to merge 2 commits into
base: main
Choose a base branch
from
Open

REL-1333039: Add step to verify ESIndexCreationSettings shard/replica #70

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
e4290bc
REL-1333039: Add step to verify ESIndexCreationSettings shard/replica…
deepankarrelativity002 Jul 29, 2026
637a113
REL-1333039: Address PR feedback - remove single-node note, audit ind…
deepankarrelativity002 Jul 29, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 8 additions & 2 deletions elastic-stack-setup/elastic-stack-setup-03-audit.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -183,11 +183,17 @@ Follow these steps to set up Data Grid Audit using the Relativity Server CLI. Al

If the setup completes successfully, Datagrid is now configured for the environment.

4. **Verify `ESIndexCreationSettings` shard and replica values** — Before restarting services, check that the `ESIndexCreationSettings` instance setting reflects the correct shard and replica configuration for your cluster.

In Relativity, go to **Admin** → **Instance Settings** and locate `ESIndexCreationSettings`. Inspect the `number_of_shards` and `number_of_replicas` values in the JSON template:

- **Multi-node environments:** Confirm these values match your cluster's intended configuration. If they appear to have been reset to `1` and you had previously customized them, restore the correct values before restarting services.

> **Warning:** Before restarting services, check whether the `NewDataGridMigratorToggleOverwrite` instance setting exists in your Relativity instance. If it is present, it **must** be set to `True` before running any ARM jobs — otherwise ARM jobs will fail during the Audit Migration stage and may time out and discard all migration progress. If the setting is not present, no action is required.

4. Restart the following Relativity services on **all machines** in the Relativity instance: `kCura Edds Agent Manager`, `kCura Edds Web Processing Manager`, and `kCura Service Host Manager`.
5. Restart the following Relativity services on **all machines** in the Relativity instance: `kCura Edds Agent Manager`, `kCura Edds Web Processing Manager`, and `kCura Service Host Manager`.

5. Verify the Audit setup — navigate to the Audit tab in the Relativity environment and confirm all of the following:
6. Verify the Audit setup — navigate to the Audit tab in the Relativity environment and confirm all of the following:
- Recent audit events are visible and populating (new user actions appear within a few minutes).
- No error banners or "Elasticsearch connection failed" messages are displayed.
- Audit search returns results without errors.