It's currently overly complex to configure the master/slave configuration in Infinispan Query as it was designed for Hibernate Search.

Especially different, in the case of Infinispan people should not have to deal with JMS, a secondary JGroups channel, nor static configuration for which node is the master.

Infinispan has custom commands which can replace the communication channel, and an implementation of an auto-election policy is trivial.