Roy, from what I understand, you want plugins that are somehow coordinated and do not require to get installed on every node.
A similar situation is possible in the HTTP area. Some ES nodes may provide HTTP, some not, by disabling HTTP. The deploy of a set of coordinated plugins is possible by adding a coordination service within a "uber plugin" architecture where a group of node dynamically serve custom requests within a cluster. The idea is to deploy an uber plugin once to several nodes, not all. From then on, they accept REST commands for distributed job executing on the nodes that can serve the job type. Each node can examine the cluster nodes and decide where to forward the job to. Nodes that have no plugin installed - or having the plugin disabled - are not affected. With a trick, the uber plugin nodes can receive additional jars live, for serving different job types. This can be useful for monitoring services, but also for scalable rivers. All the ES admin have to do is to select the appropriate nodes for the uber plugin. I started his work can called it gatherer plugin, see https://github.com/jprante/elasticsearch-gatherer Jörg -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAKdsXoHOJgZ_mao8myiESwOex6oy%3Dm53rUn32e%2Bha83b2u2Fbw%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
