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

Accessing a non-distributed cache from a RemoteCacheManager can break topology updates

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 7.0.0.Alpha5
    • 5.1.1.FINAL
    • Remote Protocols
    • None
    • Compatibility/Configuration
    • Hide

      Make sure all your caches are distributed. If you don't use the default cache, make sure it's not accessed under the covers by a ping request by disabling infinispan.client.hotrod.ping_on_startup.

      Show
      Make sure all your caches are distributed. If you don't use the default cache, make sure it's not accessed under the covers by a ping request by disabling infinispan.client.hotrod.ping_on_startup.

    Description

      RemoteCacheManager uses a single consistent hash to map requests to different servers, but caches on the server may have different CHs (or even no CH if the cache is not in distributed mode).

      If the first request goes to a on-distributed cache, the client will never request an updated CH and so it will use a round robin strategy for routing request to all the caches. Obviously this is not optimal for distributed caches.

      Each distributed cache can also have different members since 5.1, so it would be best if we kept a separate CH per cache on the client.

      Attachments

        Issue Links

          is incorporated by

          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-1090 Hot Rod protocol improvements for version 2

          • 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.
          • Resolved
          is related to

          Bug - A problem that impairs or prevents the functions of the product. ISPN-3701 In HotRod client topologyId is shared for all caches

          • 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.
          • Resolved

          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-3530 The HotRod client should support a separate CH for each cache

          • 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
              dberinde@redhat.com Dan Berindei (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: