KEYS redis command not working?

[sandyplace]

KEYS redis command not working?

[MojtabaTajik]

Do you have any extra info to reproduce the issue? I can't reproduce it.

[sandyplace]

I figured it out, I was trying to reduce the memory footprint as I noticed it was taking up 10gb in my local machine dev environment using docker/k8s. For some reason the startup parameters I was using was returning no errors at startup. I was able to index my data into GarnetServer just fine but the keys command was behaving as above. I was passing the following configuration to try to create a smaller footprint for local testing:

apiVersion: apps/v1
kind: StatefulSet
metadata:
  name: redis
spec:
  serviceName: redis
  replicas: 1
  selector:
    matchLabels:
      app: redis
  template:
    metadata:
      labels:
        app: redis
    spec:
      containers:
        - name: redis
          image: ghcr.io/microsoft/garnet
          imagePullPolicy: IfNotPresent
          ports:
            - containerPort: 6379
              name: client
          command: [
              "/app/GarnetServer",
              "--index",
              "1073742849",
              "--checkpointdir",
              "/data",
              "--aof",
              "--port",
              "6379",
            ]
          resources:
            requests:
              memory: "3Gi"
              cpu: "1000m"
            limits:
              memory: "3Gi"
              cpu: "4000m"
          env:
            - name: POD_IP
              valueFrom:
                fieldRef:
                  fieldPath: status.podIP
          volumeMounts:
            - name: redis-data
              mountPath: /data
              readOnly: false
  volumeClaimTemplates:
    - metadata:
        name: redis-data
      spec:
        storageClassName: ssd
        accessModes:
          - ReadWriteOnce
        resources:
          requests:
            storage: 1Gi
---
apiVersion: v1
kind: Service
metadata:
  name: redis-svc
spec:
  type: LoadBalancer
  ports:
    - name: redis-port
      port: 6379
      protocol: TCP # default; can also specify UDP
  selector:
    app: redis

[vazois]

Are you still facing the issue above or is it resolved?

[vazois]

It looks like the issue was result of configuration issue. Closing the issue until otherwise.

[cduluCNB]

This seems to be the related to #143, this memory usage is by design and configurable.