eran-levy opened a new issue #14322:
URL: https://github.com/apache/superset/issues/14322


   1. Cloned master github repo
   2. Run local docker-compose: docker-compose -f docker-compose-non-dev.yml up
   3. superset_cache redis container fails to start and infinitely restarted:
   `
   superset_cache          | 1:M 24 Apr 06:39:10.453 # WARNING: The TCP backlog 
setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set 
to the lower value of 128.
   superset_cache          | 1:M 24 Apr 06:39:10.453 # Server started, Redis 
version 3.2.12
   superset_cache          | 1:M 24 Apr 06:39:10.454 # 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.
   superset_cache          | 1:M 24 Apr 06:39:10.454 # Can't handle RDB format 
version 9
   superset_cache          | 1:M 24 Apr 06:39:10.455 # Fatal error loading the 
DB: Invalid argument. Exiting.
   `
   4. superset_worker fails to connect the superser_cache container: 
   `superset_worker         | [2021-04-24 06:40:09,492: ERROR/MainProcess] 
consumer: Cannot connect to redis://redis:6379/0: Error -2 connecting to 
redis:6379. Name or service not known..
   superset_worker         | Trying again in 16.00 seconds... (8/100)
   `
   Seems like it's using redis:3.2 - 
   `services:
     redis:
       image: redis:3.2
       container_name: superset_cache
   ...
   `
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to