Currently it only works on JMS client side.

Shouldn't we make an option to make consumptions transactional as well? i.e. if the master takes a batch of Works A, then can not manage to flush that successfully to the IndexWriter, and fails, the next master node should still get A in his TODO list?

see https://github.com/hibernate/hibernate-search/pull/858