[horde] Issue when trying to use admin interface in recent update

[Ralf Lang]

Hi Nels,

MGET only works if all keys are available from one node. In your setup this
might not be the case. I have released a fixed version of the library which
will fall back to GET if MGET fails AND LOGS.
The new library also provides a method to suppress MGET when the admin
knows it won't work but currently there is no horde config option to
support this yet.

On Mon, May 11, 2026 at 10:20 PM Nels Lindquist <nlindq at maei.ca> wrote:

> On 2026-05-11 10:50 AM, Ralf Lang wrote:
> >
> > I have been investigating this issue.
> >
> > Q: Is this a real redis or a redis-like product such as KeyDB?
> > Q: Single redis or a cluster?
>
> It's real redis, in a 2-node sentinel replication/failover
> configuration. There are two additional sentinel-only nodes for quorum;
> the Horde hashtable configuration includes all four hosts, each using
> the sentinel port 26379.
>
> > The old code fell back from MGET to GET if the server / config didn't
> > support MGET but our new library is a bit more picky. I will provide a
> > way to support your scenario but I'd like to learn more about it.
>
> It's currently Redis 5, installed directly from the distro (AlmaLinux 8)
> repository. Looks like MGET has been supported since version 1.0.0 so
> that shouldn't be an issue. Is the new library handling the Sentinel
> discovery differently?
>
> --
> Nels Lindquist
> nlindq at maei.ca
>