Carp sync issue with load balancing

  • I opened a ticket for a kind of unique problem that only exists when you have a web server that is going in and out of the cluster.  Ticket is  bug 1262.  This could be as simple as not calling the sync function from check_reload_status when it is being triggered by a node in a cluster, instead of a user change.

    Just want to make sure this does not get over looked.


  • Looks like some people have read my post, but no response, also the ticket has not been touched….

    Here is the link to the ticket  Will someone acknowledge this?

Log in to reply