Denis Boulas
Denis Boulas
**Describe the bug** ```Error: yaml: control characters are not allowed``` e.g. `\x01` `\x02` Version of yq: 4.9.3 Operating system: linux Installed via: binary release Seems related: https://stackoverflow.com/questions/33717799/go-yaml-control-characters-are-not-allowed-error
Hi Brandon! In some cases it would be useful to have some per-event logging for extended stats calculation, analysis and incident/problem management. Surely it may bring performance bottlenecks, but with...
It's necessary to restart other nodes after coordinator restart too to return cluster to "NORMAL" state. If pilosa nodes advertise themselves with plain IP address it looks as follows: ```...
- Cluster set of 3 nodes - replication factor 3 - cluster is empty (no indexes created) - reproducible in 99% of attempts. Let me know what else you need...
Pilosa doesn't try to re-initiate connection to replaced node. There is a brainsplit in `/status` lists for this node (it lists old IP). I think it should check for information...
As far as I've understood `/status` handler on every node returns cluster state and map from its point of view. It also has just 3 statuses (from what I've seen...
Hello! I'm seeing that last release was a year ago, there is bunch of PRs and issues opened w/o much activity... Is this project being developed or abandoned already?
This aimed to remove leftovers of the fix from https://github.com/kubernetes/kops/pull/9917
Today I've got very strange issue (not a first time actually) when all middlemanagers stopped to consume data from Kinesis stream for a long period (>40 minutes). The only message...
Right now we do support different realms as long as they use different authenticators. However its not possible to manage more than 1 realm within the same authenticator (for e.g....