-
This is similar to #1390 (but for a different system).
Node `wrk-0` of the observability cluster (`obs.nerc.mghpcc.org`), service tag `CZMS0Q2`, is experiencing memory errors on `DIMM_B1`:
```
…
-
At the beginning of `disrupt_truncate` nemesis the test ks/table are prepared with the c-s command:
```
< t:2024-09-14 12:46:50,787 f:stress_thread.py l:325 c:sdcm.stress_thread p:INFO > cassand…
-
**Description**
Kyma clusters should support multiple machine types simultaneously. For example GPU and ARM nodes, network, memory and CPU optimized nodes, etc.
Acceptance criteria:
- [ ] [KIM su…
-
Hello,
Can we add opensearch-security/config.yml to the docker compose file to declare appropriate LDAP changes that will persist across updates ?
A certificate can also be defined for ldapcace…
-
**Is your doc request related to a problem? Please describe or add the related issue ID.**
I have just been confronted with the problem of how to name the installation modes in Harvester. For example…
-
### Describe the bug
When two nodes are registered very closely to eachother, it can happen that the ZKHelixAdmin.addInstance() method is called at about the same time on the two nodes. The one tha…
-
-
### Description
**What problem are you trying to solve?**
Karpenter provides nodepools with a `disruption` spec to control how a nodepool can be disrupted by Karpenter to satisfy nodes.
As a clu…
-
Per elastic/elasticsearch@7d3ae5442537560de5578894699e0b08a9848fcb, the node name for master eligible nodes that are in the initial cluster discovery must match exactly the node name of the instance. …
dcode updated
5 years ago
-
Out of the box, Fabric8 builds do not work on multi-node cluster due to default, insecure, configuration of `fabric8-docker-registry`.
I installed fabric8 on two-node cluster using gofabric8 on Azu…