Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Last revision Both sides next revision
current:advancedlayouts [2015/01/24 22:49]
sj
current:advancedlayouts [2015/01/24 22:50]
sj
Line 15: Line 15:
 === #2: Master - slave SQL servers, no quarantine === === #2: Master - slave SQL servers, no quarantine ===
  
-In this scenario each clapf nodes have their own slave sql servers. The important change from the previous setup is that you can't just write the clapf database since a slave sql server should be used as read-only. Thus we disable updating the token timestamp values (update_tokens=0). Note that the counters should be put to a memcached / redis server, and then to the master, instead of directly the local slave. The advantage of this setup is that the local slave sql servers can be highly optimised to support.+In this scenario each clapf nodes have their own slave sql servers. The important change from the previous setup is that you can't just write the clapf database since a slave sql server should be used as read-only. Thus we disable updating the token timestamp values (update_tokens=0). Note that the counters should be put to a memcached / redis server, and then to the master, instead of directly ​writing to the local slave. The advantage of this setup is that the local slave sql servers can be highly optimised to support.
  
 Also note that you need different spam@, and ham@ addresses for training using an extra clapf node which updates the master sql server with training requests. Also note that you need different spam@, and ham@ addresses for training using an extra clapf node which updates the master sql server with training requests.