Chao Wang

hmm, I don't think so, the shard state does not really matter in m3aggregator, is the cutover/cutoff time correct?

Yeah that seems to be a log in the coordinator code, the coordinator should probably do a `MarkAllShardsAvailable` then `Add`/`Remove`/`Replace` @robskillington The cutover/cutoff time is used to route traffic between...

hi, we are running into a similar issue with operator v0.18.4: during a scale up, when we run out of resources for new CH nodes, the operator stuck in a...

e.g. the operator is managing 3 CH clusters in a namespace: `cluster1`, `cluster2` and `cluster3`, when it stuck in scaling up `cluster1`, the `cluster2` config is removed in `cluster3`, so...

Nope, I meant 3 ClickHouse clusters in one k8s namespace operated by one operator

``` kubectl get chi --all-namespaces NAMESPACE NAME CLUSTERS HOSTS STATUS AGE xxx my-use-case-v1 3 ?? Completed 9d ``` in that namespace I have the following clusters: ``` spec: configuration: clusters:...

``` kubectl get deployment -l app=clickhouse-operator --all-namespaces NAMESPACE NAME READY UP-TO-DATE AVAILABLE AGE xxx clickhouse-operator 1/1 1 1 79d ```

@Slach yes separate clusters are all deployed on separate pods, each node should have the same `chop-generated-remote_servers.xml` on all cluster during scale-up. the nodes can see all the clusters, we...

For item 1, could we do it by using a different env for zone Bar and Baz? because otherwise we basically need another layer between zone and namespace, then for...

Re item 1, I'd prefer not to use namespace that way, The original plan for namespace is to support a registry per namespace, basically allowing user to define the type...