Search Options

Display Count
Sort
Preferred Language
Advanced Search

Results 1 - 8 of 8 for Liveness (0.1 seconds)

  1. 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
    Created: Sun Dec 28 19:28:13 GMT 2025
    - Last Modified: Tue Aug 12 18:20:36 GMT 2025
    - 1.6K bytes
    - Click Count (0)
  2. cmd/bucket-targets.go

    	Scheme          string
    	Online          bool
    	lastOnline      time.Time
    	lastHCAt        time.Time
    	offlineDuration time.Duration
    	latency         latencyStat
    }
    
    // isOffline returns current liveness result of remote target. Add endpoint to
    // healthCheck map if missing and default to online status
    func (sys *BucketTargetSys) isOffline(ep *url.URL) bool {
    	sys.hMutex.RLock()
    	defer sys.hMutex.RUnlock()
    Created: Sun Dec 28 19:28:13 GMT 2025
    - Last Modified: Sun Sep 28 20:59:21 GMT 2025
    - 20.9K bytes
    - Click Count (0)
  3. tensorflow/c/c_api_experimental.cc

        status->status = tensorflow::errors::NotFound(
            op_name, " does not have number_attr() defined.");
        return nullptr;
      }
    
      // The returned string is owned by OpRegistry, so liveness is not a concern.
      return input_arg.number_attr().c_str();
    }
    
    int TF_OpIsStateful(const char* op_type, TF_Status* status) {
      const tensorflow::OpRegistrationData* op_reg_data;
      status->status =
    Created: Tue Dec 30 12:39:10 GMT 2025
    - Last Modified: Sat Oct 04 05:55:32 GMT 2025
    - 29.4K bytes
    - Click Count (0)
  4. CHANGELOG/CHANGELOG-1.32.md

    - kubeadm: switched the kube-scheduler static Pod to use the endpoints `/livez` (for startup and liveness probes) and `/readyz` (for the readiness probe). Previously, `/healthz` was used for all probes, which is deprecated behavior in the scope of this component. ([#126945](https://github.com/kubernetes/kubernetes/pull/126945), [@liangyuanpeng](http...
    Created: Fri Dec 26 09:05:12 GMT 2025
    - Last Modified: Tue Dec 16 18:27:41 GMT 2025
    - 448.1K bytes
    - Click Count (0)
  5. CHANGELOG/CHANGELOG-1.34.md

    - Kubeadm: made the coredns deployment manifest use named ports consistently for the liveness and readiness probes. ([#131587](https://github.com/kubernetes/kubernetes/pull/131587), [@neolit123](https://github.com/neolit123)) [SIG Cluster Lifecycle]
    Created: Fri Dec 26 09:05:12 GMT 2025
    - Last Modified: Wed Dec 10 01:13:50 GMT 2025
    - 333.3K bytes
    - Click Count (2)
  6. CHANGELOG/CHANGELOG-1.31.md

    - Kubeadm: Switched to using the new etcd endpoints introduced in 3.5.11 - /livez (for liveness probe) and /readyz (for readyness and startup probe). With this change it is no longer possible to deploy a custom etcd version older than 3.5.11 with kubeadm 1.31. If so, please upgrade etcd to a supported version. ([#124465](https://github.com...
    Created: Fri Dec 26 09:05:12 GMT 2025
    - Last Modified: Wed Nov 12 11:33:21 GMT 2025
    - 451.9K bytes
    - Click Count (0)
  7. internal/grid/muxserver.go

    	// Response sender goroutine...
    	go func(outBlock <-chan struct{}) {
    		wg.Wait()
    		defer m.parent.deleteMux(true, m.ID)
    		m.sendResponses(ctx, send, c, &handlerErr, outBlock)
    	}(m.outBlock)
    
    	// Remote aliveness check if needed.
    	if msg.DeadlineMS == 0 || msg.DeadlineMS > uint32(4*c.clientPingInterval/time.Millisecond) {
    		go func() {
    			wg.Wait()
    			m.checkRemoteAlive()
    		}()
    	}
    	return &m
    }
    
    Created: Sun Dec 28 19:28:13 GMT 2025
    - Last Modified: Tue May 27 15:19:03 GMT 2025
    - 9.7K bytes
    - Click Count (0)
  8. CREDITS

         communicate, and translate a Work;
     ii. moral rights retained by the original author(s) and/or performer(s);
    iii. publicity and privacy rights pertaining to a person's image or
         likeness depicted in a Work;
     iv. rights protecting against unfair competition in regards to a Work,
         subject to the limitations in paragraph 4(a), below;
      v. rights protecting the extraction, dissemination, use and reuse of data
    Created: Sun Dec 28 19:28:13 GMT 2025
    - Last Modified: Thu Mar 13 05:29:51 GMT 2025
    - 1.8M bytes
    - Click Count (0)
Back to Top