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

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

    Details

    • Affects:
      Compatibility/Configuration
    • Workaround Description:
      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.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  galder.zamarreno Galder ZamarreƱo
                  Reporter:
                  dan.berindei Dan Berindei
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  3 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: