You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running the vectorsearch OpenSearch benchmark workload on a constrained system (3GB memory, single node), repeated index/search workloads will occasionally cause node drops.
Other times, I am seeing the following error: IndexAllocation-Reference error [ERROR] search_phase_execution_exception ({'error': {'root_cause': [{'type': 'illegal_state_exception', 'reason': "IndexAllocation-Reference is already closed can't increment refCount current count [0]"}], 'type': 'search_phase_execution_exception', 'reason': 'all shards failed', 'phase': 'query', 'grouped': True, 'failed_shards': [{'shard': 0, 'index': 'target_index', 'node': 'jgqwrThQTvuDDPQfxXZo_g', 'status': 500}) without a node drop. The workload succeeds with a small error rate.
How can one reproduce the bug?
Steps to reproduce the behavior: Docker-compose.yml (based on the sample docker-compose.yml given in the OpenSearch docs, but with restricted memory):
services:
opensearch-node1: # This is also the hostname of the container within the Docker network (i.e. https://opensearch-node1/)
image: opensearchproject/opensearch:2.18.0 # Specifying the latest available image - modify if you want a specific version
container_name: opensearch-node1
environment:
- cluster.name=opensearch-cluster
- node.name=opensearch-node1
- discovery.type=single-node
- bootstrap.memory_lock=true # along with the memlock settings below, disables swapping
- "OPENSEARCH_JAVA_OPTS=-Xms512m -Xmx512m" # minimum and maximum Java heap size, recommend setting both to 50% of system RAM
- OPENSEARCH_INITIAL_ADMIN_PASSWORD=${OPENSEARCH_INITIAL_ADMIN_PASSWORD}
deploy:
resources:
limits:
memory: 3.0GB
ulimits:
memlock:
soft: -1 # Set memlock to unlimited (no soft or hard limit)
hard: -1
nofile:
soft: 65536 # Maximum number of open files for the opensearch user - set to at least 65536
hard: 65536
volumes:
- opensearch-data1:/usr/share/opensearch/data # Creates volume called opensearch-data1 and mounts it to the container
ports:
- 9200:9200 # REST API
- 9600:9600 # Performance Analyzer
networks:
- opensearch-net # All of the containers will join the same Docker bridge network
opensearch-dashboards:
image: opensearchproject/opensearch-dashboards:2.18.0 # Make sure the version of opensearch-dashboards matches the version of opensearch installed on other nodes
container_name: opensearch-dashboards
deploy:
resources:
limits:
memory: 500MB
ports:
- 5601:5601 # Map host port 5601 to container port 5601
expose:
- "5601" # Expose port 5601 for web access to OpenSearch Dashboards
environment:
OPENSEARCH_HOSTS: '["https://opensearch-node1:9200"]' # Define the OpenSearch nodes that OpenSearch Dashboards will query
networks:
- opensearch-net
volumes:
opensearch-data1:
networks:
opensearch-net:
Params (faiss-sift-128-l2.json from the sample params with search_clients, id_field_name, and docvalue_fields added or updated):
navneet1v
changed the title
[BUG] "IndexAllocation-Reference closed" error on search workload
[Duplicate] "IndexAllocation-Reference closed" error on search workload
Dec 24, 2024
What is the bug?
When running the vectorsearch OpenSearch benchmark workload on a constrained system (3GB memory, single node), repeated index/search workloads will occasionally cause node drops.
Other times, I am seeing the following error:
IndexAllocation-Reference error [ERROR] search_phase_execution_exception ({'error': {'root_cause': [{'type': 'illegal_state_exception', 'reason': "IndexAllocation-Reference is already closed can't increment refCount current count [0]"}], 'type': 'search_phase_execution_exception', 'reason': 'all shards failed', 'phase': 'query', 'grouped': True, 'failed_shards': [{'shard': 0, 'index': 'target_index', 'node': 'jgqwrThQTvuDDPQfxXZo_g', 'status': 500})
without a node drop. The workload succeeds with a small error rate.How can one reproduce the bug?
Steps to reproduce the behavior:
Docker-compose.yml (based on the sample docker-compose.yml given in the OpenSearch docs, but with restricted memory):
Params (faiss-sift-128-l2.json from the sample params with
search_clients
,id_field_name
, anddocvalue_fields
added or updated):Commands:
What is the expected behavior?
Queries will complete without error, or the node will drop
What is your host/environment?
Do you have any additional context?
The text was updated successfully, but these errors were encountered: