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

Eland should be Serverless aware when throwing incompatible ES version errors #696

Closed
ppf2 opened this issue May 31, 2024 · 0 comments · Fixed by #698
Closed

Eland should be Serverless aware when throwing incompatible ES version errors #696

ppf2 opened this issue May 31, 2024 · 0 comments · Fixed by #698

Comments

@ppf2
Copy link
Member

ppf2 commented May 31, 2024

Currently, eland checks the ES version whek checking compatible.

2024-05-31 12:44:50,385 INFO : Establishing connection to Elasticsearch
2024-05-31 12:44:50,808 INFO : Connected to cluster named '<Serverless Project ID>' (version: 8.11.0)
2024-05-31 12:44:50,808 ERROR : Eland uses PyTorch version 2.1.2 which is incompatible with Elasticsearch versions prior to 8.13. Please upgrade Elasticsearch to at least version 8.13

On Serverless, this is problematic because Serverless does not have the notion of version but it will always return an arbitrary 8.11.0 version number (e.g. in GET /) for backwards compatibility reasons (it does not mean that automatic upgrades on Serverless is not working). So eland will need to be updated to check against build_flavor instead of version.number. Otherwise, Serverless ES projects will always fail with model loading:

"build_flavor": "serverless"
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant