> This is caused by the service ticket being written to one node of the MySQL > cluster, > but then the other CAS node happens to get to do the service ticket > validation, > and it happens to use the other DB node, the ticket isn't found, because > database > replication hasn't been fast enough to bring the ticket over.
I assume you're using traditional master-slave replication where no amount of tweaks will _guarantee_ replication on a timescale that would work in all cases. I believe you MUST use multi-master MySQL replication in order to make this work properly. Bill Thompson mentioned recently that he'd worked on such a setup and it worked admirably, so perhaps he can weigh in here with more information. M -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
