Uploaded image for project: 'Red Hat Data Grid'
  1. Red Hat Data Grid
  2. JDG-2025

State transfer should preserve the creation timestamp of entries

XMLWordPrintable

    • +
    • Hide

      1. start JDG server 1.
      2. put 1000 entries with lifespan (10 seconds) via hotrod client (ExpireTest.java).
      3. start JDG server 2 after 5 seconds from the step 2.
      4. monitor the cache size every seconds, about a half entries remains in a cache after 10 seconds.

      And the creation time of relabanced entries's was renewed after rebalance.
      (JDG 7.2.1 is same behavior.)

      Show
      1. start JDG server 1. 2. put 1000 entries with lifespan (10 seconds) via hotrod client (ExpireTest.java). 3. start JDG server 2 after 5 seconds from the step 2. 4. monitor the cache size every seconds, about a half entries remains in a cache after 10 seconds. And the creation time of relabanced entries's was renewed after rebalance. (JDG 7.2.1 is same behavior.)
    • JDG Sprint #22, JDG Sprint #23

      State transfer inserts values with the current time as the creation time. Since the entries store the expected lifespan and not the expected expiration time, entries on the receiving node could expire much later than intended.

      The argument probably doesn't apply to the timestamp of the last usage. Since state transfer process could be interpreted as a reader, it should be fine to extend the update the time of the last usage both on the sending node and on the receiving node.

        1. ExpireTest.java
          3 kB
        2. reproducer_hotrod.zip
          3 kB

              dberinde@redhat.com Dan Berindei (Inactive)
              rhn-support-wfink Wolf Fink
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: