-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
[BUG] [remote store] FileAlreadyExistsException causes Replication failed #9556
Comments
Looking into it |
More detail, @mch2 modified the code to catch the exception tlfeng@0849ff0, then I re-run the tests after deploying the modified OpenSearch to the cluster. Finally the cluster had "cluster-manager not discovered exception" instead of red index.
|
Describe the bug
Found a problem during running performance test against OpenSearch built from code in 2.x branch.
The index is red during indexing operation
The below is error messages from OpenSearch log on data nodes:
Once the
FileAlreadyExistsException
occurs, the error will keep showing forever until the index being red and caused permanent failure.To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
Plugins
Please list all plugins currently enabled.
Screenshots
If applicable, add screenshots to help explain your problem.
Host/Environment (please complete the following information):
OpenSearch version: 2.10.0,
build_date : 2023-08-17T01:55:16.349778010Z
Test scenario: 10 nodes, 40 shards, 1 replica, 2 GB shard
The command for deploying the cluster:
The command for generating the 1600gb workload data:
expand-data-corpus.py --corpus-size 1600 --output-file-suffix 1600gb
The command for triggering the benchmark test:
Additional context
There was an issue reporting a similar symptom #8905
The text was updated successfully, but these errors were encountered: