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
Ingest Pipelines not working after removing plugin #27783
Comments
@gmoskovicz so is there a specific behavior that you prefer to see? One thing that comes to mind to me is that we continue to throw an exception in the logs, but also continue to registering later pipelines in the loop that would be able to be registered. Does that sound fair? So, pipelines that did rely on those plugins would still not be present, but the others would still work. |
Do we need to throw an intermittent exception? Perhaps just at startup (or when it fails) is enough? |
@talevy +1 to your plan. @gmoskovicz What do you mean by "intermittent exception"? Node startup is exactly what is being discussed. There is no synchronous request to return an error in here. |
Ah, ok. +1 on that then. I saw some intermittent logging related to this issue, but it might be just related to this issue but not caused by the same facts. It's just present when xpack is installed since it uses a pipeline for the Monitoring API. |
I know this is late to the game... but a similar problem popped up recently, and so that change should also fix this. reference PR: Since we cannot stop the node from starting up, the best we can do is inform the user that there is a problem. the PR I have pushed should make it clear to users that attempt to run pipelines, why they failed. Other pipelines that did not depend on the geoip processor should still be loaded now and work |
Elasticsearch version (
bin/elasticsearch --version
): 6.0Plugins installed: ingest-geoip
JVM version (
java -version
): AnyOS version (
uname -a
if on a Unix-like system): AnySteps to reproduce:
ingest-geoip
plugin in Elasticsearchingest-geoip
plugin in Elasticsearch[1]
[2]
Elasticsearch will return:
It seems to be that the problem is coming from the beginning when trying to apply the cluster state:
The text was updated successfully, but these errors were encountered: