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

Internal counter cache should start lazy to prevent form issues if not used

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Clustering
    • Labels:
      None

      Description

      For counters an internal cache is used ___counter_configuration which is started eager.
      If counters are not used and there is a cluster split (only two nodes) the cache would be degraded and a new node (i.e. one pod which is started to replace the crashed node) is not able to join the cluster.
      In this case the livenessprobe will fail for OpenShift.
      There is no way to change the PartitionHandling for this internal caches.

      If the counters are not used the cache should be inactive to not consume resources or cause issues.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              pruivo Pedro Ruivo
              Reporter:
              wdfink Wolf-Dieter Fink
              Votes:
              2 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: