GitHub user Nimishbansal-16 created a discussion: Async query Redis Connection 
issue

This is my redis configuration in superset.
from celery.schedules import crontab
class CeleryConfig(object):
    broker_url = "redis://:[email protected]:6379/1"
    imports = (
        "superset.sql_lab",
        "superset.tasks.scheduler",
        "superset.tasks.cache",
    )
    result_backend = 
"db+mysql://pr-superset:[email protected]:3306/superset"
    worker_prefetch_multiplier = 10
    task_acks_late = True
#    broker_connection_retry_on_startup = True
    task_annotations = {
        "sql_lab.get_sql_results": {
            "rate_limit": "100/s",
        },
    }
    task_default_queue = 'superset_queue'
    task_default_routing_key = 'superset.tasks'
    task_queues = (
        Queue('superset_queue', routing_key='superset.#'),
    )
    beat_schedule = {
            'cache-warmup-daily': {
                'task': 'cache-warmup',
                'schedule': crontab(minute=0, hour=4),  # @Daily at 4am
                'kwargs': {
                    'strategy_name': 'dashboard_tags',
                    'tags': ['daily_warmup'],
                },
            },
    }

CELERY_CONFIG = CeleryConfig



My superset version is: 5.0.0


Superset logs are - 
During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File 
"/home/ubuntu/superset_5.0.0_venv/lib/python3.11/site-packages/flask_appbuilder/api/__init__.py",
 line 111, in wraps
    return f(self, *args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^
  File 
"/home/ubuntu/superset_5.0.0_venv/lib/python3.11/site-packages/superset/views/base_api.py",
 line 120, in wraps
    duration, response = time_function(f, self, *args, **kwargs)
                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File 
"/home/ubuntu/superset_5.0.0_venv/lib/python3.11/site-packages/superset/utils/core.py",
 line 1369, in time_function
    response = func(*args, **kwargs)
               ^^^^^^^^^^^^^^^^^^^^^
  File 
"/home/ubuntu/superset_5.0.0_venv/lib/python3.11/site-packages/superset/async_events/api.py",
 line 96, in events
    events = async_query_manager.read_events(async_channel_id, last_event_id)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File 
"/home/ubuntu/superset_5.0.0_venv/lib/python3.11/site-packages/superset/async_events/async_query_manager.py",
 line 267, in read_events
    results = self._cache.xrange(stream_name, start_id, "+", 
self.MAX_EVENT_COUNT)
              
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File 
"/home/ubuntu/superset_5.0.0_venv/lib/python3.11/site-packages/superset/async_events/cache_backend.py",
 line 81, in xrange
    return self._cache.xrange(stream_name, start, end, count)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File 
"/home/ubuntu/superset_5.0.0_venv/lib/python3.11/site-packages/redis/commands/core.py",
 line 3891, in xrange
    return self.execute_command("XRANGE", name, *pieces)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File 
"/home/ubuntu/superset_5.0.0_venv/lib/python3.11/site-packages/redis/client.py",
 line 1266, in execute_command
    conn = self.connection or pool.get_connection(command_name, **options)
                              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File 
"/home/ubuntu/superset_5.0.0_venv/lib/python3.11/site-packages/redis/connection.py",
 line 1461, in get_connection
    connection.connect()
  File 
"/home/ubuntu/superset_5.0.0_venv/lib/python3.11/site-packages/redis/connection.py",
 line 713, in connect
    raise ConnectionError(self._error_message(e))
redis.exceptions.ConnectionError: Error 111 connecting to localhost:6379. 
Connection refused.


Due to this charts creation not happening.

GitHub link: https://github.com/apache/superset/discussions/35990

----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to: 
[email protected]


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

Reply via email to