-
Notifications
You must be signed in to change notification settings - Fork 274
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.
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
Opensearch: [Segment Replication] Add new Test manifest to test all plugin compatibility with Segment Replication enabled. #3345
Comments
Hi @Rishikesh1159, I believe we want to keep the actual integration testing separate from seg-Rep feature testing. additional-cluster-configs:
opensearch.experimental.feature.replication_type.enabled: true
cluster.indices.replication.strategy: "SEGMENT" This will add above values to opensearch.yml to each cluster that is deployed for testing. I assume this is what we want? |
Hi @gaiksaya, yes you are correct. Sorry for confusing description, the request here is to add one more test-manifest to add those values to opensearch.yml. Let me change the description of this issue to make it clear |
Thanks! So I tried adding the running with above configuration and looks like cluster is unable to start. Error
Manifest with segRep:---
schema-version: '1.0'
name: OpenSearch
ci:
image:
name: opensearchstaging/ci-runner:ci-runner-centos7-opensearch-build-v2
args: -e JAVA_HOME=/opt/java/openjdk-17
components:
- name: ml-commons
integ-test:
test-configs:
- with-security
- without-security
additional-cluster-configs:
opensearch.experimental.feature.replication_type.enabled: true
cluster.indices.replication.strategy: "SEGMENT" Steps to reproduce the issue:
Make sure you pas |
Thanks @gaiksaya for detailed info on steps to reproduce. Looks like my changes in PR (new cluster setting) are not present in build 7320 build. My changes merged to 2.x branch after this build. So, inorder to set this cluster setting we need a new successful build. Currently the latest successful build for 2.7 is still 7320 build, so we need to wait until new successful build of 2.7 branch happens |
Triggered a new build: https://build.ci.opensearch.org/job/distribution-build-opensearch/7325/ |
The build was successful and this build does contain the commit you mentioned. Details can be seen in distribution manifest: https://ci.opensearch.org/ci/dbc/distribution-build-opensearch/2.7.0/7325/linux/x64/tar/dist/opensearch/manifest.yml - name: OpenSearch
repository: https://github.com/opensearch-project/OpenSearch.git
ref: 2.x
commit_id: b33f7352f98971a6293a4f7e966f78745e9b2bb0 You can use above steps to reproduce with new build to test if cluster is able to start. Thanks! |
Thanks @gaiksaya. I used latest successful build to run the test-manifest with segrep enabled as you mentioned above. I ran the test using the command you suggested above:
the test passed successfully |
Triggered a test with segment replication enabled https://build.ci.opensearch.org/blue/organizations/jenkins/integ-test/detail/integ-test/3979/pipeline |
Is your feature request related to a problem? Please describe
Coming from: opensearch-project/OpenSearch#6602
Leading up to GA of segment replication in opensearch 2.7, we need to do a round of sanity testing with plugins.
To do this testing we need a new test-manifest exactly same as https://github.com/opensearch-project/opensearch-build/blob/main/manifests/2.7.0/opensearch-2.7.0-test.yml but with below values added to each plugin:
Describe the solution you'd like
To enable segment replication by default, we need to set feature flag and a cluster setting. Both of these must be passed/set from opensearch.yml
-> To enable segment replication feature flag, we have to pass:
opensearch.experimental.feature.replication_type.enabled: true
in opensearch.yml. (4959).-> To set cluster setting of replication type, we have to pass:
cluster.indices.replication.strategy: "SEGMENT"
in opensearch.yml. (6791).Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: