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

[bitnami/elasticsearch] No processor type exists with name [inference] #72437

Open
alimoezzi opened this issue Sep 14, 2024 · 10 comments
Open

[bitnami/elasticsearch] No processor type exists with name [inference] #72437

alimoezzi opened this issue Sep 14, 2024 · 10 comments
Assignees
Labels
elasticsearch on-hold Issues or Pull Requests with this label will never be considered stale tech-issues The user has a technical issue about an application

Comments

@alimoezzi
Copy link

alimoezzi commented Sep 14, 2024

Name and Version

bitnami/elasticsearch:8.15.0

What architecture are you using?

amd64

What steps will reproduce the bug?

Inference processor although it's available in kibana but upon creating an ingest pipeline with inference processor results in the following error:

No processor type exists with name [inference] 

image

This processor works with no problem with docker.elastic.co/elasticsearch/elasticsearch:8.15.0

What is the expected behavior?

Bitnami build should include this processor as the official image also contains it both in kibana and elasticsearch.

What do you see instead?

Kibana includes the option but upon saving this error is raised:

No processor type exists with name [inference]

Additional information

Checked 8.15.1 and issue still persists.

@alimoezzi alimoezzi added the tech-issues The user has a technical issue about an application label Sep 14, 2024
@github-actions github-actions bot added the triage Triage is needed label Sep 14, 2024
@github-actions github-actions bot removed the triage Triage is needed label Sep 16, 2024
@github-actions github-actions bot assigned andresbono and unassigned javsalgar Sep 16, 2024
@andresbono
Copy link
Contributor

Hi @alimoezzi, thank you for opening this issue. Can you describe and share how are you running the elasticsearch stack? Are you using the Helm Chart? Do you run the containers directly? Please, give us some more details so we can try to reproduce the issue on our side.

@alimoezzi
Copy link
Author

I have tested both containers and helm chart and none of them works.

@alimoezzi
Copy link
Author

To reproduce the issue, you need to create a pipeline with inference Processor. Also, this processor is missing in the cluster info.

@alimoezzi
Copy link
Author

I think it is related to disabled ML by default in both container and helm chart.
I tried to enable it but then the cluster doesn't turn on. In this case I think for sure Bitnami build is the cause as official build works with no problem.

@carrodher carrodher assigned gongomgra and unassigned andresbono Oct 1, 2024
@gongomgra
Copy link
Contributor

Hi @alimoezzi,

Sorry for the delay on getting back to you. Can you provide us with more information on how to reproduce the issue and how to enable the ML features so we can test it on our side? According to the official docs linked below you have to download and install your own ML model into the stack first and then create the inference type processor using the installed model.

https://www.elastic.co/guide/en/elasticsearch/reference/current/ingest-pipeline-search-inference.html

Did you find any error following those steps? I have found the "Inference" processor type under the "Stack Management" > "Ingest pipelines" > "Create pipeline" > "Add a processor" menu

Screenshot 2024-10-11 at 17 07 29

@alimoezzi
Copy link
Author

alimoezzi commented Oct 11, 2024

I have found the "Inference" processor type under the "Stack Management" > "Ingest pipelines" > "Create pipeline" > "Add a processor" menu

Exactly, at this stage continue by clicking 'Add Processor' and then create the pipeline! Then you will get the same error.

@alimoezzi
Copy link
Author

This feature is not enabled by adding a model. Instead by enabling feature flag elasticsearch_conf_set xpack.ml.enabled "true" as it has been disable by Bitnami by default without any notice.

@gongomgra
Copy link
Contributor

@alimoezzi thanks for the detailed information. I have found a related configuration in our initialization logic

# Latest Elasticseach releases install x-pack-ml by default. Since we have faced some issues with this library on certain platforms,

According to it, we found some issues while enabling it by default in some scenarios, but you can customize the setting on your side via an initialization script

https://github.com/bitnami/containers/tree/main/bitnami/elasticsearch#initializing-a-new-instance

@alimoezzi
Copy link
Author

The bigger problem is bitnami build has corrupted xpack-ml. Please enable the option and you see the instance throws error.

@gongomgra
Copy link
Contributor

@alimoezzi thanks for your message. I have created an internal task to further investigate this issue. We will keep you posted.

@gongomgra gongomgra added on-hold Issues or Pull Requests with this label will never be considered stale and removed in-progress labels Oct 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
elasticsearch on-hold Issues or Pull Requests with this label will never be considered stale tech-issues The user has a technical issue about an application
Projects
None yet
Development

No branches or pull requests

4 participants