Uploaded image for project: 'mod_cluster'
  1. mod_cluster
  2. MODCLUSTER-217

request hang with a node is stop in EC2

    Details

    • Steps to Reproduce:
      Hide

      Ask Bela
      start a cluster on EC2 with at least 2 nodes use a sessionid application, kill the node with the JVMRoute corresponding to sessionid... The request will hang for a while until it is failed over to the other node.

      Show
      Ask Bela start a cluster on EC2 with at least 2 nodes use a sessionid application, kill the node with the JVMRoute corresponding to sessionid... The request will hang for a while until it is failed over to the other node.
    • Workaround Description:
      Hide

      Use nodeTimeout

      Show
      Use nodeTimeout
    • Estimated Difficulty:
      Low

      Description

      Once stopping the EC2 the socket is closed so the cping doesn't wait for ping but connectiontimeout which default to nodeTimeout and/or server timeout.
      That affects only the first request (per process) once the node has been cleaned.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                mbabacek Michal Karm Babacek
                Reporter:
                jfclere Jean-Frederic Clere
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: