Skip to content
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] Nightly benchmark for vectorsearch workload (faiss engine) failing with GLIBC version error #1646

Closed
rishabh6788 opened this issue Apr 23, 2024 · 3 comments
Labels
bug Something isn't working

Comments

@rishabh6788
Copy link

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:

  1. Create an OS-2.14.0 cluster with k-NN plugin
  2. Run vectorsearch workload benchmark using opensearch-benchmark
  3. 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.

@rishabh6788 rishabh6788 added bug Something isn't working untriaged labels Apr 23, 2024
@jmazanec15
Copy link
Member

Related to opensearch-project/opensearch-build#4379 (comment). cc: @peterzhuamazon

With the change to Almalinux, AL2 will be deprecated for support because it has glibc 2.26 (https://repost.aws/questions/QUrXOioL46RcCnFGyELJWKLw/glibc-2-27-on-amazon-linux-2)

@jmazanec15
Copy link
Member

So @rishabh6788 , post 2.14, AL2 will not be supported. Please confirm @peterzhuamazon

@jmazanec15
Copy link
Member

Closing - this is discussed in opensearch-project/opensearch-build#4379 (comment).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants