3 Replies Latest reply on Feb 23, 2012 10:41 AM by jfclere

    Mod_Cluster 1.2.0 Final - possible 2 bugs ?

    black_dev

      I think this is a bugs:

       

      1)

      In status page not work Transffered counter, always i have 0.

       

      Balancer: mycluster,LBGroup: ,Flushpackets: Off,Flushwait: 10000,Ping: 10000000,Smax: 1,Ttl: 60000000,Status: OK,Elected: 7,Read: 1561,Transferred: 0,Connected: 0,Load: 50

       

      2) When I Enable/disable content this not any work/impact on client. Conttext is allways accessed with no ending sessions.

       

      CASE:

      Context is Enable.

      I start session and start use a context.

      1 use

      2 use...

      [..]

      n use

      - I disable a context and i can use context in session started on first step of case. IF I stop sessions, and start new session, context is unavaliable...

       

      CASE 2:

      Context is Disable.

      I start session and try use context.

      1 try - error

      2 try - error

      [...]

      n try - error

      - I eneble context

      n+1 try - error.

       


      This is ok ?


      Virtual Host 1:

      Contexts:

      /, Status: ENABLED Request: 0 Disable /replication-test, Status: ENABLED Request: 0 Disable 

       

       

      Jboss on other machine than httpd and ajp connection to jboss is used.

        • 1. Re: Mod_Cluster 1.2.0 Final - possible 2 bugs ?
          jfclere

          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

            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

              2) 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.

              1 of 1 people found this helpful