inbuxa cluster doctor probes the endpoints a clustered inbuxa server
depends on -- the PostgreSQL store, the NATS coordinator, etcd, Patroni
and the S3 blob store -- and reports which answer. It checks only the
endpoints named on the command line, each with that service's own probe
(a NATS greeting, etcd's /health, Patroni's /primary at 200 for the
leader), so it fits any deployment and touches nothing on the node.
It's the reachability preflight a node wants before it is pointed at a
cluster, and the groundwork for guided cluster membership.
`inbuxa cluster doctor` probes the endpoints a clustered inbuxa server
depends on -- the PostgreSQL store, the NATS coordinator, etcd, Patroni
and the S3 blob store -- and reports which answer. It checks only the
endpoints named on the command line, each with that service's own probe
(a NATS greeting, etcd's /health, Patroni's /primary at 200 for the
leader), so it fits any deployment and touches nothing on the node.
It's the reachability preflight a node wants before it is pointed at a
cluster, and the groundwork for guided cluster membership.
`inbuxa cluster doctor` probes the endpoints a clustered inbuxa server
depends on -- the PostgreSQL store, the NATS coordinator, etcd, Patroni
and the S3 blob store -- and reports which answer. It checks only the
endpoints named on the command line, each with that service's own probe
(a NATS greeting, etcd's /health, Patroni's /primary at 200 for the
leader), so it fits any deployment and touches nothing on the node.
It's the reachability preflight a node wants before it is pointed at a
cluster, and the groundwork for guided cluster membership.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
inbuxa cluster doctorprobes the endpoints a clustered inbuxa serverdepends on -- the PostgreSQL store, the NATS coordinator, etcd, Patroni
and the S3 blob store -- and reports which answer. It checks only the
endpoints named on the command line, each with that service's own probe
(a NATS greeting, etcd's /health, Patroni's /primary at 200 for the
leader), so it fits any deployment and touches nothing on the node.
It's the reachability preflight a node wants before it is pointed at a
cluster, and the groundwork for guided cluster membership.
4269ecd697to109f1bc780