opensearch-project / opensearch-project/security-analytics
[BUG] Failed to deploy OS with 2.19.0 version
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 111
- Forks
- 111
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 13
Description
What is the bug?
When I run the command helm upgrade opensearch opensearch/opensearch -f helm-openearch.yaml to try to upgrade the cluster version of future playground to 2.19.0, the following error will be reported.
java.lang.IllegalStateException: unable to upgrade the mappings for the index [[.opensearch-sap-correlation-history-2024.11.18-000003/EXiTKNkcRhW-JsnLSYYd-g]]
Likely root cause: MapperParsingException[No handler for type [sa_vector] declared on field [corr_vector]]
at org.opensearch.index.mapper.ObjectMapper$TypeParser.parseProperties(ObjectMapper.java:572)
at org.opensearch.index.mapper.ObjectMapper$TypeParser.parseObjectOrDocumentTypeProperties(ObjectMapper.java:339)
at org.opensearch.index.mapper.RootObjectMapper$TypeParser.parse(RootObjectMapper.java:190)
at org.opensearch.index.mapper.DocumentMapperParser.parse(DocumentMapperParser.java:146)
at org.opensearch.index.mapper.DocumentMapperParser.parse(DocumentMapperParser.java:135)
at org.opensearch.index.mapper.MapperService.internalMerge(MapperService.java:477)
at org.opensearch.index.mapper.MapperService.internalMerge(MapperService.java:465)
at org.opensearch.index.mapper.MapperService.merge(MapperService.java:451)
at org.opensearch.cluster.metadata.MetadataIndexUpgradeService.checkMappingsCompatibility(MetadataIndexUpgradeService.java:248)
at org.opensearch.cluster.metadata.MetadataIndexUpgradeService.upgradeIndexMetadata(MetadataIndexUpgradeService.java:121)
at org.opensearch.gateway.GatewayMetaState.upgradeMetadata(GatewayMetaState.java:340)
at org.opensearch.gateway.GatewayMetaState.upgradeMetadataForNode(GatewayMetaState.java:322)
at org.opensearch.gateway.GatewayMetaState.start(GatewayMetaState.java:196)
at org.opensearch.node.Node.start(Node.java:1680)
at org.opensearch.bootstrap.Bootstrap.start(Bootstrap.java:339)
at org.opensearch.bootstrap.Bootstrap.init(Bootstrap.java:413)
at org.opensearch.bootstrap.OpenSearch.init(OpenSearch.java:181)
at org.opensearch.bootstrap.OpenSearch.execute(OpenSearch.java:172)
at org.opensearch.cli.EnvironmentAwareCommand.execute(EnvironmentAwareCommand.java:104)
at org.opensearch.cli.Command.mainWithoutErrorHandling(Command.java:138)
at org.opensearch.cli.Command.main(Command.java:101)
at org.opensearch.bootstrap.OpenSearch.main(OpenSearch.java:138)
at org.opensearch.bootstrap.OpenSearch.main(OpenSearch.java:104)
For complete error details, refer to the log at /usr/share/opensearch/logs/opensearch-cluster.log
helm-openearch.yaml
image:
repository: "opensearchstaging/opensearch"
# override image tag, which is .Chart.AppVersion by default
tag: "2.19.0"
pullPolicy: "Always"
How can one reproduce the bug?
Steps to reproduce the behavior:
- Go to '...'
- Click on '....'
- Scroll down to '....'
- See error
What is the expected behavior?
A clear and concise description of what you expected to happen.
What is your host/environment?
- OS: [2.19.0]
- Version [e.g. 22]
- Plugins
Do you have any screenshots?
If applicable, add screenshots to help explain your problem.
Do you have any additional context?
Add any other context about the problem.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with helm-openearch.yaml and the Helm upgrade command using the 2.19.0 image tag. Inspect /usr/share/opensearch/logs/opensearch-cluster.log and the reported .opensearch-sap-correlation-history-2024.11.18-000003 mapping, focusing on the sa_vector type and corr_vector field. Done means the cluster upgrades without the mapping compatibility failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, java
- Domain
- backend, databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100