ortus redis extension: is there anything special i...
# lucee
j
ortus redis extension: is there anything special i have to do in the configuration to migrate from self-hosted redis to elasticache redis? (both unauthenticated; both single-node)
i'm not having luck just changing the host. before i go digging i want to make sure there's not something special i need to do in the settings first. (attn: @lmajano)
fyi, i can interact with elasticache redis via an instance of redis commander running locally but not from lucee (also running locally).
b
I don't think so. @lmajano (he is traveling out of the country ATM) and @jclausen can you confirm?
j
No, it’s been tested with Elasticache cluster and single. It should be good to go.
👍 1
I’ll be adding Redis Sentinel support in the next release - which will probably be next week, but Elasticache just uses Redis Cluster
FYI make sure
useSSL
is
true
for Elasticache. Otherwise you have to jump through a bunch of hoops to disable it in the Elasticache config
j
would that still be a potential problem even if i can access the instance via redis commander with no special configuration besides host and port?
j
I’m not sure. It’s possible that Redis commander tries the SSL handshake first.
j
just got out of a meeting and i'm about to try this. by the way, with elasticache, should i be using the cluster connection or non cluster connection type?
the lucee admin gui is weird for the ssl config in the cache config: • for cluster,
false
is the only option. • for non-cluster,
----
and
false
are the only options. @jclausen, when you were talking about the
isSSL
setting, you were talking about client-side, correct, not server-side Elasticache?
i went with "Encryption in transit: Disabled" on the aws side because i read that it was complicated to connect to if turned on (but maybe that's not true).
j
Oh. So that you disabled SSL then. So you would set that to false. You want to use the cluster cache driver if you have more than one Redis instance
j
How do you set the extension connection info to true if I ever went that route? I don't see a
true
option in the cache config for the extension. Also, I guess I'm still out of luck because I've been set to
false
all along.
it's DNS. maybe cached JVM DNS. looking into it.
yup,
createObject("java", "java.security.Security").setProperty("networkaddress.cache.ttl", "1");
got me sorted. i'll follow up if i have any remaining questions.
This question stands, though:
How do you set the extension connection info to useSSL=true if I want to try that route? I don't see a
true
option in the cache config GUI for the extension.
j
Oh. I see from your screenshots above, that the
true
is not appearing in the select. It looks like the lucee config for that select is correct, but I’ll track it down and push up a patch.
Copy code
"rediscluster": {
            "class":"ortus.extension.cache.redis.RedisClusterCache",
            "custom":{
                "hosts":"${REDIS_CLUSTER_HOSTS:127.0.0.1}",
                "keyprefix":"lucee-cluster",
                "username" : "${REDIS_CLUSTER_USERNAME}",
                "password" : "${REDIS_CLUSTER_PASSWORD}",
                "port":"${REDIS_CLUSTER_PORT:7000}",
		"useSSL" :"${REDIS_CLUSTER_USE_SSL:false}"
            },
            "readOnly":"false",
            "storage":"true"
        }
    },
🙏 1