googleforgames/open-match

Issue with packaged Redis

Closed this issue · 1 comments

Apologies if this isn't at all your fault. I don't know enough about k8s to know if this is to do with the way you're including Redis or more likely, something about my setup.

What happened:
The following error after the mmf creates a match:
2022/12/20 00:17:24 Failed to fetch matches for profile tower_defence, got rpc error: code = Unknown desc = error(s) in FetchMatches call. syncErr=[failed to handle match backfill: 942e9063-a56a-4f05-a779-99d9c856a29e: rpc error: code = Internal desc = failed to set the value for backfill, id: cegfu569icnjplort790: MISCONF Errors writing to the AOF file: No space left on device], mmfErr=[<nil>]
This can be traced back to Open Match's Redis cluster where the following errors are present:
cp: error writing '/opt/bitnami/redis/etc/redis.conf': No space left on device
/opt/bitnami/scripts/start-scripts/start-node.sh: line 97: echo: write error: No space left on device
/opt/bitnami/scripts/start-scripts/start-sentinel.sh: line 116: echo: write error: No space left on device
1:X 20 Dec 2022 00:57:01.800 # WARNING: Sentinel was not able to save the new configuration on disk!!!: No space left on device

How to reproduce it (as minimally and precisely as possible):
Unsure how my setup differs that causes this issue.

Anything else we need to know?:
The PVCs for each of the redis nodes have created and bound successfully.

Output of kubectl version:

Client Version: v1.25.2
Kustomize Version: v4.5.7
Server Version: v1.23.14

Install the default Evaluator

Cloud Provider/Platform (AKS, GKE, Minikube etc.): Minikube

Open Match Release Version: v1.26

Install Method(yaml/helm): Helm, exact command from Install the default Evaluator in the documentation

Appears this issue had something to do with my Minikube setup. I reinstalled the cluster (with more disk space available) and everything else the same. No idea if the reinstalling or more disk space for the cluster fixed it.