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

Continuous query events could be lost on backup node when primary leaves (atomic cache).

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 1.7
    • 1.8
    • cache
    • None

    Description

      Consider the following scenario:
      1) One node in topology;
      2) PARTITIONED cache with 1 backup;
      3) Continuous query is set on the cache;

      If another node joins the cluster, it will handle some updates. If it leaves the topology, the first node must flush it's own events from backup queue thus ensuring that no events are lost.

      But this doesn't happen because GridContinuousProcessor.addBackupNotification method perform lookup only on remote infos map, while handler is local and hence located in local infos map.

      Attachments

        Issue Links

          Activity

            People

              vozerov Vladimir Ozerov
              vozerov Vladimir Ozerov
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: