<div>Hi,<br><br>I'm reviving previous discussion.<br><br><blockquote style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;" class="gmail_quote">#3 Index copy<br>
this is what you are describing, copying the index using JGroups
instead of my file system approach. This might have merits esp as we
could diminish network traffic using multicast but it also require to
rethink the master / slave modus operandi.<br>
Today the master copy on a regular basis a clean index to a shared directory<br>
On a regular basis, the slave go and copy the clean index from the shared directory.<br>
In your approach, the master would send changes to the slaves and
slaves would have to apply them "right away" (on their passive version)<br></blockquote> <br></div><blockquote style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;" class="gmail_quote">
Lukasz,<br>
I have been discussing with Manik on #3 and we think that JBoss Cache /
Infinispan are probably a better fit than plain JGroups for that as all
the plumbing will be configured for you.<br>
When you reach this problem, let's revive this discussion.</blockquote><div><br>I was thinking about possible ideas about this problem, but could I get some directions and advices where to start. Does JBC/Infinispan job should be to store index (kind of shared directory) copied from master, and makes it available for slaves? Or maybe better idea is to write custom DirectoryProvider based on JBC/Infinispan with passing over current master/slave directory providers? <br>
<br>Cheers,<br>Lukasz<br><br><br><br></div>