Skip to main content
Announcements
Qlik Connect 2024! Seize endless possibilities! LEARN MORE
cancel
Showing results for 
Search instead for 
Did you mean: 
varganov
Contributor
Contributor

Redis is not working in QlikSense installed on Kubernetes

OS: CentOS 7

kubectl version
Client Version: version.Info{Major:"1", Minor:"15", GitVersion:"v1.15.6", GitCommit:"7015f71e75f670eb9e7ebd4b5749639d42e20079", GitTreeState:"clean", BuildDate:"2019-11-13T11:20:18Z", GoVersion:"go1.12.12", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"15", GitVersion:"v1.15.6", GitCommit:"7015f71e75f670eb9e7ebd4b5749639d42e20079", GitTreeState:"clean", BuildDate:"2019-11-13T11:11:50Z", GoVersion:"go1.12.12", Compiler:"gc", Platform:"linux/amd64"}

 

Install Qlik Sense without errors
helm install -n qliksense qlik/qliksense -f values.yaml --version 1.43.38

But some pods not started.


kubectl get pod |grep CrashLoopBackOff
qliksense-api-keys-7dcc999bc9-9pms6 0/1 CrashLoopBackOff 10 31m
qliksense-chronos-worker-7968788588-44hxb 0/1 CrashLoopBackOff 9 31m
qliksense-data-connector-qwc-cmd-67f95dd4d8-kl86q 0/1 CrashLoopBackOff 11 31m
qliksense-data-connector-qwc-rld-685dfcfd49-c5jfb 0/1 CrashLoopBackOff 11 31m
qliksense-qix-sessions-6485b5f45b-t2khx 0/1 CrashLoopBackOff 9 31m
qliksense-redis-slave-54b75f7599-2vwdn 0/1 CrashLoopBackOff 14 31m


kubectl get pod |grep Pending
qliksense-dcaas-redis-master-0 0/1 Pending 0 28m
qliksense-redis-master-0 0/1 Pending 0 28m
qliksense-redis-user-state-master-0 0/2 Pending 0 28m
qliksense-redis-user-state-slave-0 0/2 Pending 0 28m

 


kubectl get pv,pvc
NAME CAPACITY ACCESS MODES RECLAIM POLICY STATUS CLAIM STORAGECLASS REASON AGE
persistentvolume/pvc-07d546e2-9f2e-451b-81a7-97a83aa5d406 5Gi RWX Delete Bound default/qliksense-engine nfs-client 12m
persistentvolume/pvc-53442eeb-c948-4980-addd-beb562404e1b 5Gi RWX Delete Bound default/qliksense-resource-library nfs-client 12m
persistentvolume/pvc-6140ae20-381f-4a29-9710-a942c1875d57 5Gi RWX Delete Bound default/qliksense-sharing nfs-client 12m
persistentvolume/pvc-751b9059-f10f-4443-987c-f548c27bd1fc 5Gi RWX Delete Bound default/qliksense-temporary-contents nfs-client 12m
persistentvolume/pvc-985f3da6-d176-45d2-a4aa-f9bb5230a19c 5Gi RWX Delete Bound default/qliksense-qix-datafiles nfs-client 12m

NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE
persistentvolumeclaim/qliksense-engine Bound pvc-07d546e2-9f2e-451b-81a7-97a83aa5d406 5Gi RWX nfs-client 12m
persistentvolumeclaim/qliksense-qix-datafiles Bound pvc-985f3da6-d176-45d2-a4aa-f9bb5230a19c 5Gi RWX nfs-client 12m
persistentvolumeclaim/qliksense-resource-library Bound pvc-53442eeb-c948-4980-addd-beb562404e1b 5Gi RWX nfs-client 12m
persistentvolumeclaim/qliksense-sharing Bound pvc-6140ae20-381f-4a29-9710-a942c1875d57 5Gi RWX nfs-client 12m
persistentvolumeclaim/qliksense-temporary-contents Bound pvc-751b9059-f10f-4443-987c-f548c27bd1fc 5Gi RWX nfs-client 12m
persistentvolumeclaim/redis-data-qliksense-dcaas-redis-master-0 Pending 12m
persistentvolumeclaim/redis-data-qliksense-redis-master-0 Pending 12m
persistentvolumeclaim/redis-data-qliksense-redis-user-state-master-0 Pending 12m
persistentvolumeclaim/redis-data-qliksense-redis-user-state-slave-0 Pending

No logs from redis. Only from redis-slave:

12:25:28.14 INFO ==> ** Starting Redis **
1:C 04 Jun 12:25:28.152 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
1:C 04 Jun 12:25:28.152 # Redis version=4.0.14, bits=64, commit=00000000, modified=0, pid=1, just started
1:C 04 Jun 12:25:28.152 # Configuration loaded
1:M 04 Jun 12:25:28.154 * Running mode=standalone, port=6379.
1:M 04 Jun 12:25:28.154 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
1:M 04 Jun 12:25:28.154 # Server initialized
1:M 04 Jun 12:25:28.154 # WARNING you have Transparent Huge Pages (THP) support enabled in your kernel. This will create latency and memory usage issues with Redis. To fix this issue run the command 'echo never > /sys/kernel/mm/transparent_hugepage/enabled' as root, and add it to your /etc/rc.local in order to retain the setting after a reboot. Redis must be restarted after THP is disabled.
1:M 04 Jun 12:25:28.154 * Ready to accept connections
1:signal-handler (1591273555) Received SIGTERM scheduling shutdown...
1:M 04 Jun 12:25:55.070 # User requested shutdown...
1:M 04 Jun 12:25:55.070 # Redis is now ready to exit, bye bye...


But i tuned node system before install Qlik:
mcedit /etc/rc.local
echo never > /sys/kernel/mm/transparent_hugepage/enabled

mcedit /etc/sysctl.conf
net.core.somaxconn=15000

 

I'm trying to recreate kubers cluster on clean installed servers and get same errors

Labels (1)
  • SaaS

0 Replies