Eugene Klimov

@sunsingerus is it fixed in 0.23.3?

this is outdated keeper alert rules, for old clickhouse-keeper version which not provided prometheus endpoint i hope we will update these rules in the future

@sunsingerus did we look to this issue?

@Enmk cause most of queries on current metrics exporter use UNION ALL ... and make in parallel on clickhouse side but queries related to `system.parts` make a lot of "fstat...

clickhouse-keeper-0 have failed liveness probe and restart during loading snapshots try to increase `initialDelaySeconds: 180` in statefulset `spec.template.spec.containers.livenessProbe`

Could you show `clickhouse` or `clickhouse-pod` container log with error from `chi-{chi-name}-{cluster-name}-{shard}-{replica}-0` pod? try change CHI ```yaml spec: configuration: settings: disable_internal_dns_cache: 1 ```

skip_unaavailable_shards is unrelated, could you share `kubectl get chi --all-namespaces` ?

could you share `kubectl get chi -n infra-test grif-chi-ss -o yaml` without sensitive credentials?

i'm still wait CHI resource https://github.com/Altinity/clickhouse-operator/issues/1212#issuecomment-1660246872

> The problem is reproduced if you shutdown all the replicas at once and then include one by one Could you provide commands which exactly do this sequence? Is shared...