Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

terminated by SIGKILL; not expected #188

Open
krPrashantSingh opened this issue Sep 3, 2021 · 1 comment
Open

terminated by SIGKILL; not expected #188

krPrashantSingh opened this issue Sep 3, 2021 · 1 comment

Comments

@krPrashantSingh
Copy link

I am trying to create rec. But not a single POD is getting to 'running' state
This is rec yaml file

apiVersion: app.redislabs.com/v1
kind: RedisEnterpriseCluster
metadata:
name: rec-svc
spec:

Add fields here

nodes: 3
nodeSelector:
role: highmemnp
redisEnterpriseNodeResources:
limits:
cpu: "1000m"
memory: 1Gi
requests:
cpu: "500m"
memory: 512Mi
persistentSpec:
enabled: true
volumeSize: "1Gi"


snapshot of the error from POD
image

@laurentdroin
Copy link
Contributor

Hi,

There is not enough information here to know for sure what is the cause of the issue but it's very unlikely that you can get a functional cluster with such low resource limits, especially the memory.
The minimum amount of memory per node in a development environment is 4 GB (see The minimum for a non-production environment is 4 GB (see https://docs.redis.com/latest/rs/administering/designing-production/hardware-requirements/).

I would suggest deleting that REC resource and creating a new one with 4 GB of memory per node.

If this doesn't help, the best way to get help is to generate a Support Package (see https://docs.redis.com/latest/platforms/kubernetes/tasks/run-log-collector-script/) and open a support ticket with Redis. We would be able to find out exactly what is causing the problem.

Cheers,

Laurent.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants