From 7276ffdda86452692819f3295423baea8605abb9 Mon Sep 17 00:00:00 2001 From: Suraj Singh Date: Tue, 12 Dec 2023 13:07:48 -0800 Subject: [PATCH 1/4] Add documentation for known issue with use of custom codecs on version 2.7.0 Signed-off-by: Suraj Singh --- .../availability-and-recovery/segment-replication/index.md | 1 + 1 file changed, 1 insertion(+) diff --git a/_tuning-your-cluster/availability-and-recovery/segment-replication/index.md b/_tuning-your-cluster/availability-and-recovery/segment-replication/index.md index 37a4a5b8b6..8aa7c25905 100644 --- a/_tuning-your-cluster/availability-and-recovery/segment-replication/index.md +++ b/_tuning-your-cluster/availability-and-recovery/segment-replication/index.md @@ -76,6 +76,7 @@ When using segment replication, consider the following: 1. Integration with remote-backed storage as the source of replication is [currently not supported](https://github.com/opensearch-project/OpenSearch/issues/4448). 1. Read-after-write guarantees: The `wait_until` refresh policy is not compatible with segment replication. If you use the `wait_until` refresh policy while ingesting documents, you'll get a response only after the primary node has refreshed and made those documents searchable. Replica shards will respond only after having written to their local translog. We are exploring other mechanisms for providing read-after-write guarantees. For more information, see the corresponding [GitHub issue](https://github.com/opensearch-project/OpenSearch/issues/6046). 1. System indexes will continue to use document replication internally until read-after-write guarantees are available. In this case, document replication does not hinder the overall performance because there are few system indexes. +1. Custom codecs do not work on 2.7.0 OpenSearch versionq. For more information, see [Issue #7781](https://github.com/opensearch-project/OpenSearch/issues/7781) ## Benchmarks From 4b315e109560c73e5cb02a3f225db8b127525adc Mon Sep 17 00:00:00 2001 From: Suraj Singh Date: Tue, 12 Dec 2023 14:43:16 -0800 Subject: [PATCH 2/4] Update wordings Signed-off-by: Suraj Singh --- .../availability-and-recovery/segment-replication/index.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/_tuning-your-cluster/availability-and-recovery/segment-replication/index.md b/_tuning-your-cluster/availability-and-recovery/segment-replication/index.md index 8aa7c25905..f705656222 100644 --- a/_tuning-your-cluster/availability-and-recovery/segment-replication/index.md +++ b/_tuning-your-cluster/availability-and-recovery/segment-replication/index.md @@ -72,11 +72,12 @@ When using segment replication, consider the following: 1. Enabling segment replication for an existing index requires [reindexing](https://github.com/opensearch-project/OpenSearch/issues/3685). 1. Rolling upgrades are not currently supported. Full cluster restarts are required when upgrading indexes using segment replication. See [Issue 3881](https://github.com/opensearch-project/OpenSearch/issues/3881). 1. [Cross-cluster replication](https://github.com/opensearch-project/OpenSearch/issues/4090) does not currently use segment replication to copy between clusters. +<<<<<<< HEAD 1. Segment replication leads to increased network congestion on primary shards. See [Issue - Optimize network bandwidth on primary shards](https://github.com/opensearch-project/OpenSearch/issues/4245). 1. Integration with remote-backed storage as the source of replication is [currently not supported](https://github.com/opensearch-project/OpenSearch/issues/4448). 1. Read-after-write guarantees: The `wait_until` refresh policy is not compatible with segment replication. If you use the `wait_until` refresh policy while ingesting documents, you'll get a response only after the primary node has refreshed and made those documents searchable. Replica shards will respond only after having written to their local translog. We are exploring other mechanisms for providing read-after-write guarantees. For more information, see the corresponding [GitHub issue](https://github.com/opensearch-project/OpenSearch/issues/6046). 1. System indexes will continue to use document replication internally until read-after-write guarantees are available. In this case, document replication does not hinder the overall performance because there are few system indexes. -1. Custom codecs do not work on 2.7.0 OpenSearch versionq. For more information, see [Issue #7781](https://github.com/opensearch-project/OpenSearch/issues/7781) +1. Custom codecs do not work on 2.7.0 OpenSearch version for SEGMENT enabled indices. For more information, see [Issue #7781](https://github.com/opensearch-project/OpenSearch/issues/7781) ## Benchmarks From f045185175a552091858da350cceb8972f67c8fd Mon Sep 17 00:00:00 2001 From: Suraj Singh Date: Tue, 12 Dec 2023 14:47:03 -0800 Subject: [PATCH 3/4] Fix syntax error Signed-off-by: Suraj Singh --- .../availability-and-recovery/segment-replication/index.md | 1 - 1 file changed, 1 deletion(-) diff --git a/_tuning-your-cluster/availability-and-recovery/segment-replication/index.md b/_tuning-your-cluster/availability-and-recovery/segment-replication/index.md index f705656222..b3bc288208 100644 --- a/_tuning-your-cluster/availability-and-recovery/segment-replication/index.md +++ b/_tuning-your-cluster/availability-and-recovery/segment-replication/index.md @@ -72,7 +72,6 @@ When using segment replication, consider the following: 1. Enabling segment replication for an existing index requires [reindexing](https://github.com/opensearch-project/OpenSearch/issues/3685). 1. Rolling upgrades are not currently supported. Full cluster restarts are required when upgrading indexes using segment replication. See [Issue 3881](https://github.com/opensearch-project/OpenSearch/issues/3881). 1. [Cross-cluster replication](https://github.com/opensearch-project/OpenSearch/issues/4090) does not currently use segment replication to copy between clusters. -<<<<<<< HEAD 1. Segment replication leads to increased network congestion on primary shards. See [Issue - Optimize network bandwidth on primary shards](https://github.com/opensearch-project/OpenSearch/issues/4245). 1. Integration with remote-backed storage as the source of replication is [currently not supported](https://github.com/opensearch-project/OpenSearch/issues/4448). 1. Read-after-write guarantees: The `wait_until` refresh policy is not compatible with segment replication. If you use the `wait_until` refresh policy while ingesting documents, you'll get a response only after the primary node has refreshed and made those documents searchable. Replica shards will respond only after having written to their local translog. We are exploring other mechanisms for providing read-after-write guarantees. For more information, see the corresponding [GitHub issue](https://github.com/opensearch-project/OpenSearch/issues/6046). From 5977ebf11d9584649eb126477f17ce068f4bb3ed Mon Sep 17 00:00:00 2001 From: Naarcha-AWS <97990722+Naarcha-AWS@users.noreply.github.com> Date: Fri, 15 Dec 2023 08:10:47 -0600 Subject: [PATCH 4/4] Apply suggestions from code review Signed-off-by: Naarcha-AWS <97990722+Naarcha-AWS@users.noreply.github.com> --- .../availability-and-recovery/segment-replication/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_tuning-your-cluster/availability-and-recovery/segment-replication/index.md b/_tuning-your-cluster/availability-and-recovery/segment-replication/index.md index b3bc288208..c88d3dc309 100644 --- a/_tuning-your-cluster/availability-and-recovery/segment-replication/index.md +++ b/_tuning-your-cluster/availability-and-recovery/segment-replication/index.md @@ -76,7 +76,7 @@ When using segment replication, consider the following: 1. Integration with remote-backed storage as the source of replication is [currently not supported](https://github.com/opensearch-project/OpenSearch/issues/4448). 1. Read-after-write guarantees: The `wait_until` refresh policy is not compatible with segment replication. If you use the `wait_until` refresh policy while ingesting documents, you'll get a response only after the primary node has refreshed and made those documents searchable. Replica shards will respond only after having written to their local translog. We are exploring other mechanisms for providing read-after-write guarantees. For more information, see the corresponding [GitHub issue](https://github.com/opensearch-project/OpenSearch/issues/6046). 1. System indexes will continue to use document replication internally until read-after-write guarantees are available. In this case, document replication does not hinder the overall performance because there are few system indexes. -1. Custom codecs do not work on 2.7.0 OpenSearch version for SEGMENT enabled indices. For more information, see [Issue #7781](https://github.com/opensearch-project/OpenSearch/issues/7781) +1. Custom codecs do not work on 2.7.0 OpenSearch version for segment-enabled indices. For more information, see [Issue #7781](https://github.com/opensearch-project/OpenSearch/issues/7781) ## Benchmarks