i might be having issues with the ortus redis exte...
# lucee
j
i might be having issues with the ortus redis extension. i wanted to take a look at the changelogs to see if there's anything interesting in the latest patch release, but i'm not finding a current changelog. (this seems old https://www.forgebox.io/view/5C558CC6-1E67-4776-96A60F9726D580F1/version/2.0.0-snapshot#changeLog) happen to know where i can find a current changelog? (attn: @bdw429s)
j
@jamiejackson What issues are you having? We are about to bump a new release in the next 24 hours. One of the fixes deals with connectivity issues to the cluster cache. We are also adding environment variable support for license info.
For the 2.0 version, though, here is the changelog:
Copy code
## [2.0.0] => 2022-AUG-05

### Fixed

* [LRE-35](<https://ortussolutions.atlassian.net/browse/LRE-35>) cache filters for getting entries was not working
* [LRE-32](<https://ortussolutions.atlassian.net/browse/LRE-32>) getting all values/entries was not passing a built key, so return struct was always null
* [LRE-23](<https://ortussolutions.atlassian.net/browse/LRE-23>) LicenseHelper not validating all editions of similar product skus

### Added

* [LRE-41](<https://ortussolutions.atlassian.net/browse/LRE-41>) Ability to choose which database to connect to in Redis, apart from 0 being the default
* [LRE-40](<https://ortussolutions.atlassian.net/browse/LRE-40>) Migration of docs to gitbook
* [LRE-39](<https://ortussolutions.atlassian.net/browse/LRE-39>) New redisSubscribe\(\) so you can subscribe with closures/lambdas or CFCs to listen to Redis messages
* [LRE-38](<https://ortussolutions.atlassian.net/browse/LRE-38>) New redisPublish\(\) UDF so you can publish messages into the Redis cluster
* [LRE-37](<https://ortussolutions.atlassian.net/browse/LRE-37>) New UDF redisGetClusterNodes\(\) to get a map of cluster node objects
* [LRE-36](<https://ortussolutions.atlassian.net/browse/LRE-36>) Redis Cluster protocol support \(RedisCluster, Sentinel, AWS, DigitalOcean\)
* [LRE-33](<https://ortussolutions.atlassian.net/browse/LRE-33>) Redis publish and subscribe features
* [LRE-31](<https://ortussolutions.atlassian.net/browse/LRE-31>) New native cfml function: redisGetCluster\(\) to get access to the native redis cluster manager
* [LRE-30](<https://ortussolutions.atlassian.net/browse/LRE-30>) Improve all exception handling to show exception messages
* [LRE-29](<https://ortussolutions.atlassian.net/browse/LRE-29>) Creation of a base class to share between cache implementations
* [LRE-28](<https://ortussolutions.atlassian.net/browse/LRE-28>) Add docker redis cluster support
* [LRE-27](<https://ortussolutions.atlassian.net/browse/LRE-27>) Update Jedis to 2.9.3
* [LRE-25](<https://ortussolutions.atlassian.net/browse/LRE-25>) Allow for a new setting to allow for case-sensitive mode instead of case-insensitive mode \(default\)
j
i'm not sure if the redis connections were the culprit or a victim but i was seeing slow connectivity to the redis cluster.
rather, single instance (my redis isn't clustered)
l
Also. All the docs include the release notes
FYI. Through experience the culprit of almost all distributed caches is network latency and network issues
j
New development: I hadn't pinned the version of the extension. for some folks in local development, it upgraded to v2.1.x (IIRC). this caused a hard application failure (wouldn't start up) -- something about the cache not being configured for sessions. we pinned the version so that the problem wouldn't happen on our servers.
Copy code
ENV LUCEE_EXTENSIONS ${LUCEE_EXTENSIONS},5C558CC6-1E67-4776-96A60F9726D580F1;name=Ortus Redis Cache;version=2.0.0.6428
there's also weird stuff going on with extension versions because installing 6428 actually yields 6427.
(lucee 5.3.10.97)
b
The build being off by one is a known issue. It doesn't hurt anything, we're just incrementing the build and publishig in the wrong order. I've pointed it out to @lmajano recently
j
@jamiejackson Redis Extension version 2.1.0 was released last week, which adds environment variable support as well as fixing some issues with the cluster cache. The build numbers should be fixed in that version.
j
Thanks for the info about the version numbers. Any thoughts on the app startup failures due to the session cache (upon our accidental upgrade to 2.1.x)? I imagine I'm going to need to get you more info when I have time next week.
j
How long ago was that? Give it a whirl again. We moved over to Github actions and the initial snapshots that were being published were being pushed incorrectly as release versions. It’s possible the extension didn’t download correctly. The one you want is
2.1.0+24
j
Two folks on my team ran into this on 3/22, @jclausen. We "fixed" it by pinning to the 2.0.0.x version that I mentioned.
j
When you get a chance, could you test it again with the version above? I fixed some bad versions up on Forgebox on the afternoon of 3/22