Is Redis required?
See original GitHub issueHi, I am trying to explore the option of not using Redis with Exceptionless. Is that a possibility or is Redis a requirement?
I think I read somewhere in the documentation that it is optional so I deleted the below environment variables. Is this the wrong approach?
EX_ConnectionStrings__Queue: provider=redis
EX_ConnectionStrings__Redis: server=redis,abortConnect=false
Currently, the Exceptionless logs are saying this:
[16:19:43 ERR] Health check Cache completed after 0.7787ms with status Unhealthy and 'Cache Not Working.'
Issue Analytics
- State:
- Created 2 years ago
- Comments:11 (6 by maintainers)
Top Results From Across the Web
Redis: in-memory data store. How it works and why you ...
Redis offers a fast, in-memory data store to power live streaming use cases. Redis can be used to store metadata about users' profiles...
Read more >Redis: What It Is, What It Does, and Why You Should Care
This makes Redis well-suited for applications that require fast access to large amounts of data, such as real-time analytics, online gaming, and ...
Read more >Redis FAQ
Yes, a common design pattern involves taking very write-heavy small data in Redis (and data you need the Redis data structures to model...
Read more >Is Redis really necessary? · argoproj argo-cd
Running Argo CD without Redis is not supported, as it is an integral part of the architecture. You can opt to use your...
Read more >Hardware requirements | Redis Documentation Center
Nodes per cluster, You can install on one node but many features require at least two nodes. 1 node ; RAM per node,...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
In that case I’m not too worried going without the additional complexity of Redis. We’ll enable disk queuing on the client side and requeue the server side queue folder if anything goes wrong. We’ll also set up a monitor for the server side queue folder to make sure that nothing hangs around for too long. Does that sound reasonable?
Thanks for reaching out to us. It’s not required but highly recommended as not using it will limit you to run everything in a single process and any non processed queued data will be lost upon app restart. Sounds like there could be some kind of issue with the cache health check when using in memory cache client. Where is this log message coming from?