# Upgrading plugins - probably always want to restart the cluster? **URL:** \ **Category:** Elasticsearch\ **Created:** [January 28, 2013, 8:10pm UTC](https://discuss.elastic.co/t/upgrading-plugins-probably-always-want-to-restart-the-cluster/10531 "2013-01-28T20:10:37Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![ppearcy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ppearcy/32/980_2.png) [@ppearcy](https://discuss.elastic.co/u/ppearcy)\ **Post date:** [January 28, 2013, 8:10pm UTC](https://discuss.elastic.co/t/upgrading-plugins-probably-always-want-to-restart-the-cluster/10531/1 "2013-01-28T20:10:37Z")
Last week, I made some tweaks to the hunspell plugin. Specifically, removing all the affix rules that really aren't appropriate for stemming. Perhaps this was completely a bone-headed no-no on my part, but I overwrote the existing plugin jar file with the new one, with the expectation that the new plugin would get picked up when I restarted the cluster during some upcoming maintenance. I deleted an index which then triggered every node to crash a the same time. Doh! If you're curious, here is the core dump: > Did I commit a cardinal sin updating the plugin jar while the cluster was active or should this condition be handled better by elasticsearch? Thanks! Paul -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group, send email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)\ **Post date:** [January 28, 2013, 8:24pm UTC](https://discuss.elastic.co/t/upgrading-plugins-probably-always-want-to-restart-the-cluster/10531/2 "2013-01-28T20:24:04Z")
It's not Elasticsearch related. It's a JVM bug. Just do not update jars in the classpath while a JVM is active. See [http://bugs.sun.com/bugdatabase/view\_bug.do?bug\_id=4425695](http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4425695) Jörg Am 28.01.13 21:10, schrieb ppearcy: > Last week, I made some tweaks to the hunspell plugin. Specifically, > removing all the affix rules that really aren't appropriate for stemming. > > Perhaps this was completely a bone-headed no-no on my part, but I > overwrote the existing plugin jar file with the new one, with the > expectation that the new plugin would get picked up when I restarted > the cluster during some upcoming maintenance. > > I deleted an index which then triggered every node to crash a the same > time. Doh! If you're curious, here is the core dump: > [Elasticsearch 0.19.3 crash after updating hunspell jar and then deleting an index · GitHub](https://gist.github.com/4658564) > > Did I commit a cardinal sin updating the plugin jar while the cluster > was active or should this condition be handled better by elasticsearch? > > ## Thanks! Paul > > You received this message because you are subscribed to the Google > Groups "elasticsearch" group. > To unsubscribe from this group, send email to > [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 2:54am UTC](https://discuss.elastic.co/t/upgrading-plugins-probably-always-want-to-restart-the-cluster/10531/3 "2017-07-06T02:54:20Z")