Jason Cameron

updated configMap, forgot I changed it to 'test-linkerd-config' to avoid interrupting my work on Linkerd

I am having these same issues, and its VERY hard to reproduce. I am using a service account, so my kubeconfig is `token` based. In random namespaces, I encounter random...

``` ansible-playbook [core 2.11.6] config file = None python version = 3.8.10 (default, Jun 22 2022, 20:18:18) [GCC 9.4.0] jinja version = 2.10.1 libyaml = True ``` if the kubernetes.core...

Some additional notes: It appears that if we change the `commit-strategy` to `latest`, the offsets change as expected. However, we are using the smallrye-messaging version that `throttled` is the default...

@csabakollar I just ran into this issue - and though I agree with your assessment...at least you found something working. Thank you! Basically everything work as intended for me until...

one note: our data store is roughly 1.1TB. The setting https://neo4j.com/docs/operations-manual/4.4/configuration/configuration-settings/#config_causal_clustering.store_copy_max_retry_time_per_request is default, so set to 20m, so im wondering...is this error actually a timeout?

from the note above, it still doesn't explain the `online` backup i took and the errors that came from it. So I am still confused :-).

another note: I am looking at the incremental backup strategies currently. We are using `UNBOUNDED` but have a very high throughput environment, on top of the fact that we have...

all, the issue actually is with the fact that the `dbms.tx_log.rotation.retention_policy` setting (we set it to `1 hours`) was not set long enough for the causal cluster read_replica to join...

I am now having this experience with self-hosted runners in AWS with no apparent cause. Disk is fine, Mem is fine, CPU is fine - but just randomly a GitHub...