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
What is the bug?
The nightly benchmarks for vectorsearch have been failing for faiss engine indices in OS-2.14.0 with below error:
fatal error in thread [opensearch[ip-172-31-172-58.ec2.internal][generic][T#5]], exiting
java.lang.UnsatisfiedLinkError: /home/ec2-user/opensearch/plugins/opensearch-knn/lib/libopensearchknn_faiss.so: /lib64/libm.so.6: version `GLIBC_2.27' not found (required by /home/ec2-user/opensearch/plugins/opensearch-knn/lib/libopensearchknn_faiss.so)
The same nightlies have been running fine for lucene and nmslib engine types.
The OS process exits at create-target-index operation for faiss engine type.
The OpenSearch cluster is created on Amazon Linux 2 ec2-instances. The default GLIBC version installed on the host is 2.26.
How can one reproduce the bug?
Steps to reproduce the behavior:
Create an OS-2.14.0 cluster with k-NN plugin
Run vectorsearch workload benchmark using opensearch-benchmark
See error
What is the expected behavior?
There should be no failure and benchmark should complete successfully.
What is your host/environment?
OS: Amazon Linux 2
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.
The text was updated successfully, but these errors were encountered:
What is the bug?
The nightly benchmarks for vectorsearch have been failing for faiss engine indices in OS-2.14.0 with below error:
The same nightlies have been running fine for lucene and nmslib engine types.
The OS process exits at
create-target-index
operation for faiss engine type.The OpenSearch cluster is created on
Amazon Linux 2
ec2-instances. The default GLIBC version installed on the host is2.26
.How can one reproduce the bug?
Steps to reproduce the behavior:
What is the expected behavior?
There should be no failure and benchmark should complete successfully.
What is your host/environment?
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.
The text was updated successfully, but these errors were encountered: