stancl/tenancy-docs
1
0
Fork 0
mirror of https://github.com/stancl/tenancy-docs.git synced 2025-12-12 18:24:03 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

update information on queues

Browse source 
This documents the error resolution for users utilizing a different redis_client and the possibility that they may come across REDIS trying to create a connection when there isn't any connector for that connection
This commit is contained in:
Pius Gumo 2021-01-19 13:46:16 +02:00 • committed by GitHub
parent 3387736baa
commit d1ce93ad09
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

2
source/docs/v3/queues.blade.md
View file

@ -26,6 +26,8 @@ To force the database queue driver to use the central connection, open your `que
Make sure the connection used by the queue is not in `tenancy.redis.prefixed_connections`. Make sure the connection used by the queue is not in `tenancy.redis.prefixed_connections`.
>If you are making use of a different `REDIS_CLIENT ` other than `phpredis` (which is the default on most Laravel apps), you may run into an error indicating that Laravel `tried to set a connection on null` in the RedisManager class. Defaulting back to `phpredis` as the `REDIS_CLIENT` should fix this issue.
## Central queues {#central-queues} ## Central queues {#central-queues}
Jobs dispatched from the central context will remain central. However, it's recommended not to mix queue **connections** for central & tenant jobs due to potential leftover global state, e.g. central jobs thinking they're in the previous tenant's context. Jobs dispatched from the central context will remain central. However, it's recommended not to mix queue **connections** for central & tenant jobs due to potential leftover global state, e.g. central jobs thinking they're in the previous tenant's context.