-
-
Notifications
You must be signed in to change notification settings - Fork 4k
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
Issue with Redis while Upgrading or Installing Sentry #2530
Comments
Thanks for the report. Looking into supporting this in rb. |
On a second thought: not sure how that made sense before. Pretty sure we never used the blocking connection pool. @mattrobenolt do you know what the timeout there is supposed to be for? I can only see this used for the blocking pool as waiting time until connection is available and we are not using that (and did not before unless i am missing a change). |
@mitsuhiko This was the |
@mitsuhiko Not sure what needs to be done here, if anything? |
@mattrobenolt probably we should document that this is now called |
@mattrobenolt actually kinda shitty. In rb this is configured with the pool options which you currently cannot set from sentry :( |
This issue will tackle supporting it under a new key: #2671 |
This replaces `SENTRY_REDIS_OPTIONS` and per-backend configuration with named Redis clusters, configured from the value of the `redis.clusters` key in `sentry.options`. The preferred method of configuring Redis-based backends is by providing a *cluster name*, rather than the cluster configuration parameters. This deprecates: - `SENTRY_REDIS_OPTIONS` in favor of the `redis.clusters` option. - Passing `hosts` to any backend in favor of `cluster`. - `sentry.utils.make_rb_cluster` in favor of retrieving clusters defined in configuration via the clsuter manager. This also updates all tests to retrieve Redis clusters via the cluster manager, instead of via cluster configuration or direct construction via `rb.Cluster` or `StrictRedis`. This also consolidates all test cluster setup and teardown to the test wrapper methods. Resolves GH-2530 and references GH-2693.
Hello there,
While trying to upgrade to the most recent version of sentry , and following the documentation present at
this link i get the following error:
I tracked down the problem to this part of the configuration file
What solved it for me was removing the timeout options. If this is the only solution maybe the documentation should be updated.
If anyone knows about another way of solving this share it. :)
I just wanted to share this.
The text was updated successfully, but these errors were encountered: