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

[Operator] Improve probe settings

XMLWordPrintable

      Current probes settings prevent DataGrid node being available earlier then after 10s and with 10s period check the readiness will always happen in times of 10s. (If the server starts in 11s its marked as ready in 20s by OpenShift).

      Given the nodes are deployed sequentially on OpenShift after previous nodes are ready, effect of this settings stacks up. (If user deploys 3 node cluster, where it takes 11s for node to come up, the whole cluster won't be available earlier then after 1 minute even it could theoretically start up in 33s)

      Current probe settings:

      readinessProbe: 
  httpGet: 
    path: rest/v2/cache-managers/default/health/status
    port: 11223
    scheme: HTTP
  initialDelaySeconds: 10
  timeoutSeconds: 80
  periodSeconds: 10
  successThreshold: 1
  failureThreshold: 5

      livenessProbe: 
  httpGet: 
    path: rest/v2/cache-managers/default/health/status
    port: 11223
    scheme: HTTP
   initialDelaySeconds: 10
   timeoutSeconds: 80
   periodSeconds: 10
   successThreshold: 1
   failureThreshold: 5

      startupProbe: 
  httpGet: 
    path: rest/v2/cache-managers/default/health/status
    port: 11223
    scheme: HTTP
   initialDelaySeconds: 10
   timeoutSeconds: 80
   periodSeconds: 10
   successThreshold: 1
   failureThreshold: 60

            remerson@redhat.com Ryan Emerson
            pdrobek@redhat.com Pavel Drobek
            Pavel Drobek Pavel Drobek
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: