# org.elasticsearch.ElasticsearchParseException: No processor type exists with name "my plugin name"

**URL:** <https://discuss.elastic.co/t/org-elasticsearch-elasticsearchparseexception-no-processor-type-exists-with-name-my-plugin-name/71990>\
**Category:** Elasticsearch\
**Created:** [January 18, 2017, 11:50am UTC](https://discuss.elastic.co/t/org-elasticsearch-elasticsearchparseexception-no-processor-type-exists-with-name-my-plugin-name/71990 "2017-01-18T11:50:20Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![deerawan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/deerawan/32/14676_2.png) [@deerawan](https://discuss.elastic.co/u/deerawan)\
**Post date:** [January 18, 2017, 11:50am UTC](https://discuss.elastic.co/t/org-elasticsearch-elasticsearchparseexception-no-processor-type-exists-with-name-my-plugin-name/71990/1 "2017-01-18T11:50:20Z")

</div>

**Elasticsearch version** : 5.0.0

**Plugins installed** : my custom processor plugin

**JVM version** : 1.8.0\_111

**OS version** : OSX El Capitan

**Description of the problem including expected versus actual behavior:**

1. I created my custom processor plugin with name "tax\_date"
2. I installed it using elasticsearch-plugin install command
3. I removed the plugin using elasticsearch-remove command
4. I kept getting error said that org.elasticsearch.ElasticsearchParseException: No processor type exists with name tax\_date
5. Restart elasticsearch doesn't solve this issue.

**Steps to reproduce:**  
same as above. I have ensured that my plugin was not there in "loaded plugin" list.

**Provide logs (if relevant):**

 ![](https://us1.discourse-cdn.com/elastic/original/2X/a/a38254cdfbe36147d154e3bd3fc5451237cc13a9.png)

```auto
[2017-01-18T18:10:14,607][INFO][o.e.n.Node] [WYiAAg0] started
[2017-01-18T18:10:15,368][WARN][o.e.c.s.ClusterService] [WYiAAg0] failed to notify ClusterStateListener
org.elasticsearch.ElasticsearchParseException: No processor type exists with name [tax_date]
	at org.elasticsearch.ingest.ConfigurationUtils.readProcessor(ConfigurationUtils.java:312) ~[elasticsearch-5.0.0.jar:5.0.0]
	at org.elasticsearch.ingest.ConfigurationUtils.readProcessorConfigs(ConfigurationUtils.java:251) ~[elasticsearch-5.0.0.jar:5.0.0]
	at org.elasticsearch.ingest.Pipeline$Factory.create(Pipeline.java:122) ~[elasticsearch-5.0.0.jar:5.0.0]
	at org.elasticsearch.ingest.PipelineStore.innerUpdatePipelines(PipelineStore.java:79) ~[elasticsearch-5.0.0.jar:5.0.0]
	at org.elasticsearch.ingest.PipelineStore.clusterChanged(PipelineStore.java:66) ~[elasticsearch-5.0.0.jar:5.0.0]
	at org.elasticsearch.cluster.service.ClusterService.runTasksForExecutor(ClusterService.java:708) [elasticsearch-5.0.0.jar:5.0.0]
	at org.elasticsearch.cluster.service.ClusterService$UpdateTask.run(ClusterService.java:894) [elasticsearch-5.0.0.jar:5.0.0]
	at org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingRunnable.run(ThreadContext.java:444) [elasticsearch-5.0.0.jar:5.0.0]
	at org.elasticsearch.common.util.concurrent.PrioritizedEsThreadPoolExecutor$TieBreakingPrioritizedRunnable.runAndClean(PrioritizedEsThreadPoolExecutor.java:237) [elasticsearch-5.0.0.jar:5.0.0]
	at org.elasticsearch.common.util.concurrent.PrioritizedEsThreadPoolExecutor$TieBreakingPrioritizedRunnable.run(PrioritizedEsThreadPoolExecutor.java:200) [elasticsearch-5.0.0.jar:5.0.0]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [?:1.8.0_111]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [?:1.8.0_111]
	at java.lang.Thread.run(Thread.java:745) [?:1.8.0_111]

```

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [January 18, 2017, 1:49pm UTC](https://discuss.elastic.co/t/org-elasticsearch-elasticsearchparseexception-no-processor-type-exists-with-name-my-plugin-name/71990/2 "2017-01-18T13:49:08Z")

</div>

But did you remove existing ingest pipelines which are declaring this processor?

If you don't have any important data you can always restart from scratch and stop elasticsearch and remove its data dir. Note that it will erase all data, all licenses if you have any...

---

<div class="post-metadata">

**Author:** ![deerawan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/deerawan/32/14676_2.png) [@deerawan](https://discuss.elastic.co/u/deerawan)\
**Post date:** [January 19, 2017, 6:38am UTC](https://discuss.elastic.co/t/org-elasticsearch-elasticsearchparseexception-no-processor-type-exists-with-name-my-plugin-name/71990/3 "2017-01-19T06:38:30Z")

</div>

Hi @dadoonet

Wonderful suggestion! I didn't notice that pipeline will still exist even though you stop and start the elasticsearch.

So the cause is because I uninstalled the processor plugin but I forgot to remove the pipeline which use the plugin.

I solved this by executing DELETE \_ingest/pipeline/my-plugin-name

Thank you @dadoonet 🙂

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [February 16, 2017, 6:38am UTC](https://discuss.elastic.co/t/org-elasticsearch-elasticsearchparseexception-no-processor-type-exists-with-name-my-plugin-name/71990/4 "2017-02-16T06:38:34Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.