From e4290bc64f3bad599b2fa503445ce2c3a7a5099a Mon Sep 17 00:00:00 2001 From: Deepankar Kalita Date: Wed, 29 Jul 2026 16:09:08 +0530 Subject: [PATCH 1/2] REL-1333039: Add step to verify ESIndexCreationSettings shard/replica values after CLI setup Co-Authored-By: Claude Sonnet 4.6 --- elastic-stack-setup/elastic-stack-setup-03-audit.md | 13 +++++++++++-- 1 file changed, 11 insertions(+), 2 deletions(-) diff --git a/elastic-stack-setup/elastic-stack-setup-03-audit.md b/elastic-stack-setup/elastic-stack-setup-03-audit.md index adfb75f..b3a7068 100644 --- a/elastic-stack-setup/elastic-stack-setup-03-audit.md +++ b/elastic-stack-setup/elastic-stack-setup-03-audit.md @@ -183,11 +183,20 @@ 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: + + - **Single-node environments:** The defaults (`number_of_shards: "1"`, `number_of_replicas: "1"`) are appropriate. + - **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. New `audit_*` indices are created using these settings, so incorrect values will affect ingest and search performance until corrected. + + For guidance on recommended values for your cluster size, refer to the [Instance Setting Guide](https://help.relativity.com/Server2024/Content/System_Guides/Instance_Setting_Guide/Instance_setting_descriptions.htm#ESIndexCreationSettings). + > **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. From 637a11347f1447748295c1f8bb30273eabba28e9 Mon Sep 17 00:00:00 2001 From: Deepankar Kalita Date: Wed, 29 Jul 2026 17:01:46 +0530 Subject: [PATCH 2/2] REL-1333039: Address PR feedback - remove single-node note, audit index sentence, and instance setting guide link Co-Authored-By: Claude Sonnet 4.6 --- elastic-stack-setup/elastic-stack-setup-03-audit.md | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/elastic-stack-setup/elastic-stack-setup-03-audit.md b/elastic-stack-setup/elastic-stack-setup-03-audit.md index b3a7068..fb55388 100644 --- a/elastic-stack-setup/elastic-stack-setup-03-audit.md +++ b/elastic-stack-setup/elastic-stack-setup-03-audit.md @@ -187,10 +187,7 @@ Follow these steps to set up Data Grid Audit using the Relativity Server CLI. Al In Relativity, go to **Admin** → **Instance Settings** and locate `ESIndexCreationSettings`. Inspect the `number_of_shards` and `number_of_replicas` values in the JSON template: - - **Single-node environments:** The defaults (`number_of_shards: "1"`, `number_of_replicas: "1"`) are appropriate. - - **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. New `audit_*` indices are created using these settings, so incorrect values will affect ingest and search performance until corrected. - - For guidance on recommended values for your cluster size, refer to the [Instance Setting Guide](https://help.relativity.com/Server2024/Content/System_Guides/Instance_Setting_Guide/Instance_setting_descriptions.htm#ESIndexCreationSettings). + - **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.