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

Get from backup in Dht cache can be optimized

    XMLWordPrintableJSON

Details

    • Task
    • Status: Closed
    • Blocker
    • Resolution: Done
    • None
    • 1.6
    • None

    Description

      Reproducible example: https://gist.github.com/aboudnik/3419fdc3872cc3051a1d

      See attached screenshot for sampling info.

      Issues found:

      1. entry is created with putIfObsoleteOrAbsent() even if store and swap are disabled
      2. no need to create DhtGetFuture on primary when there is no ongoing rebalancing

      Make sure the performance is fixed for ATOMIC and TRANSACTIONAL REPLICATED & PARTITIONED caches.

      Attachments

        1. test.csv
          0.9 kB
          Denis A. Magda
        2. Screenshot 2015-10-29 18.04.07.png
          406 kB
          Yakov Zhdanov
        3. Main.java
          5 kB
          Denis A. Magda

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. IGNITE-2526 get() from a REPLICATED cache for a non-existing key on a non-primary node causes a get() to the primary node

          • Major - Major loss of function.
          • Closed

          Activity

            People

              sboikov Semen Boikov
              yzhdanov Yakov Zhdanov
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: