Uploaded image for project: 'Infinispan'
  1. Infinispan
  2. ISPN-4720

Values data reverts in Compatibilty mode in Infinispan 8.0.0Beta3

    XMLWordPrintable

Details

    Description

      1) The owners of the keys are Node1 and Node4
      0911 10:56:56,552 TRACE [org.infinispan.interceptors.distribution.TxDistributionInterceptor] [remote-thread-0] (TxDistributionInterceptor.java:362) - Not doing a remote get for key 1029 since entry is mapped to current node (blrsrv42-19390), or is in L1. Owners are [blrsrv29-4565, blrsrv42-19390]

      2. The request for update came to Node2 a non-owner.
      0911 10:56:56,388 TRACE [org.infinispan.statetransfer.StateTransferInterceptor] [HotRodServerWorker-2] (StateTransferInterceptor.java:203) - handleNonTxWriteCommand for command ReplaceCommand{key=1029, oldValue=TestData

      {id=1029, field1=XXXXXX}

      , newValue=TestData

      {id=1029, field1=cyyy}

      , metadata=EmbeddedMetadata{version=NumericVersion{version=844433520066561}}, flags=[OPERATION_HOTROD], successful=true, valueMatcher=MATCH_EXPECTED}

      3. The updates are happening in Node1 and overwritten again with old data present in OOB Thread. Because of which the Node1, reverts back to the old data.

      4. While doing a get from Node 1 we again receive the old value

      Attachments

        1. BaseDistributionInterceptor.java
          27 kB
          Prashant Thakur
        2. distributed_cache_configuration.xml
          3 kB
          Prashant Thakur
        4. tc2.out
          2.41 MB
          Prashant Thakur
        5. tc3.out
          2.52 MB
          Prashant Thakur
        6. tc4.out
          2.22 MB
          Prashant Thakur
        7. TxDistributionInterceptor.java
          19 kB
          Prashant Thakur

        Issue Links

          is incorporated by

          Bug - A problem that impairs or prevents the functions of the product. ISPN-5477 Compatibility with L1 can lead to wrong return type

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is related to

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) ISPN-3797 DataContainer should interact atomically with Persistence

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              rh-ee-galder Galder Zamarreño
              prashant.thakur_jira Prashant Thakur (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: