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

getCache() should not wait for the initial state transfer by default

    Details

    • Type: Enhancement
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 9.2.1.Final
    • Fix Version/s: None
    • Component/s: Configuration, Core
    • Labels:
      None

      Description

      DefaultCacheManager.getCache(name) normally blocks until the local node becomes a full member of the consistent hash and the rebalance has finished. This can cause problems when rebalancing is disabled, either explicitly by the administrator, or implicitly because the cache is in degraded mode.

      Blocking can be disabled with builder.clustering().stateTransfer().awaitInitialTransfer(false) (await-initial-transfer="false" in XML}}, but we should make the non-blocking behaviour the default. We should also deprecate the method and attribute to enable the blocking behaviour, and instead add a method to AdvancedCache to wait for the initial state transfer.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  dan.berindei Dan Berindei
                  Reporter:
                  dan.berindei Dan Berindei
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  2 Start watching this issue

                  Dates

                  • Created:
                    Updated: