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

Document MVCC continuous queries

    XMLWordPrintableJSON

    Details

    • Type: Task
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.7
    • Component/s: documentation
    • Labels:
      None
    • Ignite Flags:
      Docs Required

      Description

      Key differences with continuous queries for non-MVCC caches:
      1) When event is received, subsequent read of the same key may still return previous value for some time (i.e. no guarantee of happens-before between event and subsequent read)
      2) Keys for notification are kept in memory. If transaction is too large, OOME could happen. In order to avoid that, we skip notification of too large transactions.

      Roman Kondakov, could you please elaborate on how is this implemented?

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Artem Budnikov Artem Budnikov
                Reporter:
                vozerov Vladimir Ozerov
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: