Uploaded image for project: 'Ignite'
  1. Ignite
  2. IGNITE-5860

Client disconnects if server it is connected to goes unresponsive

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 1.7
    • 2.4
    • None
    • None

    Description

      Scenario is the following:

      1. Start at least two server nodes.
      2. Start a client node.
      3. Detect server node client is connected to in discovery SPI.
      4. Suspend that server (^Z in terminal or 'kill -SIGSTOP <PID>').
      5. It's expected that client will drop connection with this server and connect to another one.
      6. However, a client gets dropped from topology and disconnects.

      A client should reconnect cluster before the timeout and without EVT_CLIENT_NODE_RECONNECTED event.

      In ClientImpl.Reconnector in joinTopology method it gets all addresses from discoverySpi and addresses of the server that was suspended on top of this list.

      Proposed solution:
      Move addresses of the suspended server to the end of the list for the join.

      Attachments

        1. testAlivesClient.patch
          3 kB
          Ilya Kasnacheev

        Activity

          People

            dmekhanikov Denis Mekhanikov
            ezhuravl Evgenii Zhuravlev
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: