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

Incorrect "Completed partition exchange" message triggered by client node (dis)connect.

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Resolved
    • Major
    • Resolution: Not A Problem
    • 2.8.1
    • None
    • general
    • None

    Description

      Now topology change with client cluster node triggers near message, this is erroneous due to no partition exchange have place here. All we need to log here - is only topology change message.

      Completed partition exchange [localNode=e0062158-e1d1-4139-aca3-332ddc919b00, exchange=GridDhtPartitionsExchangeFuture [topVer=AffinityTopologyVersion [topVer=97, minorTopVer=0], evt=NODE_LEFT, evtNode=TcpDiscoveryNode [id=e91e44dd-fb7e-415a-a980-3d6c597f46e8, consistentId=e91e44dd-fb7e-415a-a980-3d6c597f46e8, addrs=ArrayList [1.2.6.44], sockAddrs=HashSet [grid2094/1.2.3.4:0], discPort=0, order=94, intOrder=59, lastExchangeTime=1590669922545, loc=false, ver=2.5.8#20190912-sha1:67c23274, isClient=true],
      

      Attachments

        Activity

          People

            Unassigned Unassigned
            zstan Evgeny Stanilovsky
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: