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

Support for Valkey #2245

Open
Zerotask opened this issue Feb 18, 2025 · 0 comments · May be fixed by #2246
Open

Support for Valkey #2245

Zerotask opened this issue Feb 18, 2025 · 0 comments · May be fixed by #2246

Comments

@Zerotask
Copy link

Valkey is an open source drop-in replacement for Redis.

Although the scheme redis:// is compatible, the package django-valkey recommends switching to valkey://.

If I change the BROKER_URL from BROKER_URL=redis://127.0.0.1:6379 to BROKER_URL=valkey://127.0.0.1:6379, both celery and celery-beat stops working, because they can't resolve transport:

  File "/***/lib/python3.13/site-packages/kombu/connection.py", line 201, in __init__
    if not get_transport_cls(transport).can_parse_url:
           ~~~~~~~~~~~~~~~~~^^^^^^^^^^^
  File "/***/lib/python3.13/site-packages/kombu/transport/__init__.py", line 91, in get_transport_cls
    _transport_cache[transport] = resolve_transport(transport)
                                  ~~~~~~~~~~~~~~~~~^^^^^^^^^^^
  File "/***/lib/python3.13/site-packages/kombu/transport/__init__.py", line 72, in resolve_transport
    raise KeyError(f'No such transport: {transport}')
KeyError: 'No such transport: valkey'
@Zerotask Zerotask linked a pull request Feb 18, 2025 that will close this issue
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

Successfully merging a pull request may close this issue.

1 participant