|Topic||A cluster slave node can directly cache published messages|
Usually if you publish a message to a cluster slave node, the message is directly forwarded and routed to the master node of this message type.
If clients connected to frodo (a slave node) subscribe to messages frodo subscribes it from heron, as heron is the master. Only messages coming from the master are approved. The slaves receives the update and delivers it to the client:
It is possible to suppress the update (2.1.1) as the slave can just as well dirty read the published message at step (2):
The main reason for this requirement is to minimize net traffic on
connections between cluster nodes with limited band width.
The dirty read attribute has to be set at all stratum levels to be active, here
cluster.node[heron.mycomp.com]=\ <clusternode id='heron.mycomp.com'>\ <master type='DomainToMaster' dirtyRead='true'>\ <key queryType='DOMAIN' domain='RUGBY_NEWS'/>\ </master>\ </clusternode>
See xmlBlaster/demo/javaclients/cluster for more examples.
NOTE: Configuration parameters are specified on command line (-someValue 17) or in the
xmlBlaster.properties file (someValue=17). See requirement "util.property" for details.
This page is generated from the requirement XML file xmlBlaster/doc/requirements/cluster.dirtyRead.xml
Back to overview