MongoDB cluster on Kubernetes - /opt/percona/ps-entry.sh: line 522: exec: numactl --interleave=all: not found

Hi, I have a kubernetes cluster which is running on Virtualbox and I am setting up a 3 node MongoDB replica set using Percona MongoDB Operator. Everything was working just fine with some very minor changes on the cr-minimal.yaml. I recently deleted the PerconaServerMongoDB and tried to recreate it and I am getting this error,

kubectl logs minimal-cluster-rs0-0
Defaulted container "mongod" out of: mongod, mongo-init (init)
+ exec 'numactl --interleave=all' mongod --bind_ip_all --auth --dbpath=/data/db --port=27017 --replSet=rs0 --storageEngine=wiredTiger --relaxPermChecks --clusterAuthMode=keyFile --keyFile=/etc/mongodb-secrets/mongodb-key --enableEncryption --encryptionKeyFile=/etc/mongodb-encryption/encryption-key --wiredTigerIndexPrefixCompression=true --tlsAllowInvalidCertificates
/opt/percona/ps-entry.sh: line 522: exec: numactl --interleave=all: not found

I am not sure where to look for the error.

My cluster config is

kubectl get nodes
NAME              STATUS   ROLES           AGE    VERSION
flatcar-worker1   Ready    control-plane   128d   v1.28.0
flatcar-worker2   Ready    <none>          128d   v1.28.0
flatcar-worker5   Ready    <none>          106d   v1.28.0

and the manifest I created it very simple

apiVersion: psmdb.percona.com/v1
kind: PerconaServerMongoDB
metadata:
  name: minimal-cluster
spec:
  crVersion: 1.16.0
  image: perconalab/percona-server-mongodb-operator:main-mongod6.0
  allowUnsafeConfigurations: true
  upgradeOptions:
    apply: disabled
    schedule: "0 2 * * *"
  # secrets:
  #   users: minimal-cluster
  secrets:
    users: my-cluster-name-secrets

  replsets:
  - name: rs0
    size: 3
    volumeSpec:
      persistentVolumeClaim:
        storageClassName: longhorn
        resources:
          requests:
            storage: 3Gi

  sharding:
    enabled: false

    configsvrReplSet:
      size: 1
      volumeSpec:
        persistentVolumeClaim:  
          storageClassName: longhorn
          resources:
            requests:
              storage: 3Gi

    mongos:
      size: 1

The replica set was just working fine and after deleting, during the recreation I am getting this error. Any pointers will be really helpful.

Thanks and Regards,
J

@athreyavc please do not use main branch. It is under development right now and from time to time we can see some problems with it. Please use PSMDBO v1.15.0.

@athreyavc main branch should work now.

1 Like

I did use 1.15.0 and it is working.