Does Redis allow caching of the javax.sql.DataSource object? I read Redis does not allow all types of objects to be cached.
Related
I want to read directly from a replica inside a Redis cluster but I am getting redirected even if the key actually exist inside the Redis node.
Checked READONLY command docs. However, that is seemed to be ignored in case of Redis Cluster.
How should I configure the Redis cluster so that I can directly read from a replica node for the reads issue against its hash slots? I am OK to read stale data in this case.
The READONLY command (as well as the READWRITE command that counteracts it) are applicable per connection in a clustered environment.
While READWRITE is the default behavior, in order to change that you'll need to call READONLY in the context of the connection that you're using.
I have a Redis database (no cluster, no replica).
How can i configure it to be read only? (so client can not modify it)
I do not want to set up a replication or cluster.
Thanks in advance
There is no such configuration for Redis master. Only replicas can be configured as read-only. If you have control over the Redis client library used by your clients, you can change it to expose only read methods to the clients.
About Persistent Storage, Should I turn on Persistent true on Client node if i only use atomic cache?
<property name="persistenceEnabled" value="true">
I have several ignite client with RESTful of ignite turn on, to query remote several ignite servers, i know it's sure to keep the data safe when node corrupt, i need turn on persistent on server node, should i also turn on this
on my client node or i don't need turn it on as all my cache is atomic, thanks.
By default, client nodes do not store data. So, this parameter does not make much sense.
[1] https://apacheignite.readme.io/docs/clients-vs-servers
I have a Redis instance with some persistent keys and a lot of keys that have expired. Then I execute the bgsave command to get an rdb file. As a result the file contains all keys - persistent and not persistent.
When I restart Redis all the non-persistent keys turned into persistent keys.
How can I avoid this?
I want all non-persistent keys stay non-persistent.
I am working on converting an existing single tenant application to a multitenant one. Distributed caching is new to me. We have an existing primitive local cache system using the .NET cache that generates cloned objects from existing cached ones. I have been looking at utilizing Redis.
Can Redis cache and invalidate locally in addition to over the wire thus replacing all benefit of the local primitive cache? Or would it potentially be an ideal approach to have a tiered approach utilizing Redis distributed cache if the local one doesn't have the objects we need? I believe the latter would imply requiring expiration notifications to happen against the local caches when data is updated otherwise servers may have out of date inconsistent data
It seems like a set of local caches with expiration notifications would also qualify as a distributed cache, so I am a bit confused here on how Redis might be configured and if it would be distributed accross the servers serving the requests or live in it's own cluster.
When I say local I am implying not having to go over the wire for data.