Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 6 of 6 for Liveness (0.11 sec)

  1. docs/metrics/healthcheck/README.md

    # MinIO Healthcheck
    
    MinIO server exposes three un-authenticated, healthcheck endpoints liveness probe and a cluster probe at `/minio/health/live` and `/minio/health/cluster` respectively.
    
    ## Liveness probe
    
    This probe always responds with '200 OK'. Only fails if 'etcd' is configured and unreachable. When liveness probe fails, Kubernetes like platforms restart the container.
    
    ```
    livenessProbe:
      httpGet:
        path: /minio/health/live
        port: 9000
    Registered: Sun Sep 07 19:28:11 UTC 2025
    - Last Modified: Thu Jul 06 16:18:38 UTC 2023
    - 2.5K bytes
    - Viewed (0)
  2. docs/metrics/README.md

    ## Healthcheck Probe
    
    MinIO server has two healthcheck related un-authenticated endpoints, a liveness probe to indicate if server is responding, cluster probe to check if server can be taken down for maintenance.
    
    - Liveness probe available at `/minio/health/live`
    - Cluster probe available at `/minio/health/cluster`
    
    Registered: Sun Sep 07 19:28:11 UTC 2025
    - Last Modified: Thu Feb 29 18:35:20 UTC 2024
    - 1.9K bytes
    - Viewed (0)
  3. cmd/healthcheck-router.go

    	healthCheckClusterPath     = "/cluster"
    	healthCheckClusterReadPath = "/cluster/read"
    	healthCheckPathPrefix      = minioReservedBucketPath + healthCheckPath
    )
    
    // registerHealthCheckRouter - add handler functions for liveness and readiness routes.
    func registerHealthCheckRouter(router *mux.Router) {
    	// Healthcheck router
    	healthRouter := router.PathPrefix(healthCheckPathPrefix).Subrouter()
    
    	// Cluster check handler to verify cluster is active
    Registered: Sun Sep 07 19:28:11 UTC 2025
    - Last Modified: Mon Jan 23 11:12:47 UTC 2023
    - 2.3K bytes
    - Viewed (0)
  4. docs/orchestration/kubernetes/README.md

    ## Monitoring MinIO in Kubernetes
    
    MinIO server exposes un-authenticated liveness endpoints so Kubernetes can natively identify unhealthy MinIO containers. MinIO also exposes Prometheus compatible data on a different endpoint to enable Prometheus users to natively monitor their MinIO deployments.
    
    ## Explore Further
    Registered: Sun Sep 07 19:28:11 UTC 2025
    - Last Modified: Tue Aug 12 18:20:36 UTC 2025
    - 1.6K bytes
    - Viewed (0)
  5. cmd/healthcheck-handler.go

    			}
    			return
    		}
    	}
    	writeResponse(w, http.StatusOK, nil, mimeNone)
    }
    
    // LivenessCheckHandler checks whether MinIO is up. It differs from the
    // readiness handler since a failing liveness check causes pod restarts
    // in K8S environments. Therefore, it does not contact external systems.
    func LivenessCheckHandler(w http.ResponseWriter, r *http.Request) {
    	if objLayer := newObjectLayerFn(); objLayer == nil {
    Registered: Sun Sep 07 19:28:11 UTC 2025
    - Last Modified: Wed Jun 26 07:44:34 UTC 2024
    - 6.9K bytes
    - Viewed (0)
  6. cmd/http-tracer.go

    	op = strings.Replace(op, "ClusterCheckHandler", "health.Cluster", 1)
    	op = strings.Replace(op, "ClusterReadCheckHandler", "health.ClusterRead", 1)
    	op = strings.Replace(op, "LivenessCheckHandler", "health.Liveness", 1)
    	op = strings.Replace(op, "ReadinessCheckHandler", "health.Readiness", 1)
    	op = strings.Replace(op, "-fm", "", 1)
    	return op
    }
    
    // If trace is enabled, execute the request if it is traced by other handlers
    Registered: Sun Sep 07 19:28:11 UTC 2025
    - Last Modified: Tue Sep 24 17:13:00 UTC 2024
    - 6K bytes
    - Viewed (0)
Back to top