-
1. Re: Mod_Cluster 1.2.0 Final - possible 2 bugs ?
jfclere Feb 23, 2012 8:23 AM (in response to black_dev)1) transfered = data from POST you are testing with GET or HEAD, no?
2) DISABLE means that the requests without session-id won't go to the node so that looks OK.
-
2. Re: Mod_Cluster 1.2.0 Final - possible 2 bugs ?
black_dev Feb 23, 2012 9:50 AM (in response to black_dev)1) I use GET
like this ( PHP ) get content:
[..]
$ch = curl_init ("http://x.x.x.1/replication-test/");
curl_setopt ($ch, CURLOPT_COOKIEFILE, $ckfile);
curl_setopt ($ch, CURLOPT_RETURNTRANSFER, true);
$output = curl_exec ($ch);
[..]
2) Ok. But I have a Questions: How to force move clients from node1 to node2 to make node1 in maintenance mode.
I proposed make a button like: maintenance mode on/off for node or context to delicatly move users from this node/context.
Now if I have request with session-id mod cluster use all nodes, and I can't switch off dedicated node ( only simulate fault on this node)
-
3. Re: Mod_Cluster 1.2.0 Final - possible 2 bugs ?
jfclere Feb 23, 2012 10:41 AM (in response to black_dev)1 of 1 people found this helpful2) that is the concept of DISABLE you wait until all users have finished their sessions.
If you stop a node cleanly it will first send a DISABLE and wait before sending a STOP.