Skip to content
#

cluster

Here are 2,000 public repositories matching this topic...

medyagh
medyagh commented Apr 28, 2022

What Happened?

if you have 3 clusters and you make one of them active
all minikube commands will run against that cluster,

$ minikube profile p1
✅  minikube profile was successfully set to p1
15:16:37 medya
$ minikube status
p1
type: Control Plane
host: Running
kubelet: Running
apiserver: Running
kubeconfig: Configured

this should be reflected in the minikube profile l

kind/feature priority/important-soon good first issue
xiaopingcs
xiaopingcs commented May 13, 2022

Bug Description
taosBenchmark subscribe crash

To Reproduce
Steps to reproduce the behavior:

  1. Build taosd, taosBenchmark in latest develop branch
  2. go to 'TDengine/src/kit/taos-tools/example'
  3. execute taosBenchmark -f insert_csv.json
  4. execute taosBenchmark -f subscribe.json

Expected Behavior
taosBenchmark -f subscribe.json should not crash

Screenshots
N/A

bug good first issue
nadenf
nadenf commented Nov 11, 2021

Problem

I would like to be able to have different names for my node to help with discovery in tools like k9s.

If I (a) create the cluster and then (b) create the nodes I can achieve this.

But if I need to create the cluster and nodes at the same time i.e. via -agents flag then this is not possible.
And some use cases e.g. per-node volumes are only possible using this approach

enhancement good first issue priority/low
AnisTigrini
AnisTigrini commented Apr 7, 2022

Hi There, noticed there is an environment variable to inject "etcd_host" but there are none in the repo for usernames and password. Could create a PR for that to add them to the operator configmap ?
Could enable etcd3 as well since there are no env variables for v3 (supported by Patroni).
Let me know what you guys think.

actionhero
mfvargo
mfvargo commented Jan 22, 2021

We had an issue where an api user was using the incorrect parameters on an API call. Having this feature would have made the API fail instead of proceeding. The bug would been found earlier.

I can see where this would be a hassle on many cases, But it would be nice for new projects.

I suppose it could be a global config item that could be overridden at the individual action level:

For

good first issue enhancement help wanted
kafka-monitor

Xinfra Monitor monitors the availability of Kafka clusters by producing synthetic workloads using end-to-end pipelines to obtain derived vital statistics - E2E latency, service produce/consume availability, offsets commit availability & latency, message loss rate and more.

  • Updated May 13, 2022
  • Java
ksync

Improve this page

Add a description, image, and links to the cluster topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the cluster topic, visit your repo's landing page and select "manage topics."

Learn more