[Feature]: Sentinel

[drauschenbach]

Is your feature request related to a problem?

Is there a way to configure for Redis Sentinel?

Describe the solution you'd like

Expose the underlying Sentinel support.

Describe alternatives you've considered

No response

Use case

A HA setup of Redis involving a primary+mirror plus 3 sentinels.

Additional context

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

[geofmureithi]

Sure, I am willing to consider this, I am curious though what you have tried and what error you encountered.

[geofmureithi]

My initial thoughts is that it should work, as RedisStorage can accept any type that implements ConnentionLike.

[drauschenbach]

Thanks! Maybe I'm just missing an example. I'm not familiar with ConnectionLike. I'll do my best to figure it out this weekend and get back to you.

[geofmureithi]

Yeah it should be straight forward:

use futures::prelude::*;
use redis::{ Commands, RedisConnectionInfo };
use redis::sentinel::{ SentinelServerType, SentinelClient, SentinelNodeConnectionInfo };

let nodes = vec!["redis://127.0.0.1:6379/", "redis://127.0.0.1:6378/", "redis://127.0.0.1:6377/"];
let sentinel_node_connection_info = SentinelNodeConnectionInfo::default()
  .set_tls_mode(redis::TlsMode::Insecure);
let mut sentinel = SentinelClient::build(
    nodes,
    String::from("primary1"),
    Some(sentinel_node_connection_info),
    redis::sentinel::SentinelServerType::Master,
)
.unwrap();

let primary = sentinel.get_async_connection().await.unwrap();
let mut backend = RedisStorage::new_with_config(
        primary,
        RedisConfig::default()
            .set_namespace("redis_basic_worker")
            .set_buffer_size(100),
    );

Give the above setup a try and see how it goes.

[drauschenbach]

I'm getting close. Where do you provide the database number Apalis should use?

[drauschenbach]

OK I got it. Thanks!

    let nodes = vec![
        "redis://sentinel-0:26379",
        "redis://sentinel-1:26379",
        "redis://sentinel-2:26379",
    ];
    let sentinel_node_connection_info = SentinelNodeConnectionInfo {
        tls_mode: None,
        redis_connection_info: Some(RedisConnectionInfo {
            db: 14,
            ..Default::default()
        }),
    };
    let mut sentinel = SentinelClient::build(
        nodes,
        String::from("mymaster"),
        Some(sentinel_node_connection_info),
        redis::sentinel::SentinelServerType::Master,
    )?;
    let redis_primary = sentinel.get_async_connection().await.unwrap();

[geofmureithi]

It would be good to provide a small report of your findings :)

[drauschenbach]

I'm only past compilation issues at this point. My enqueue logic and worker seem to be using the same database at this point. But after I schedule a task, I have to restart my workers before they get unstuck and pick up new work. There's a lot of layers here, I'm going to have to peel them back one at a time. I might need to look at my Tokio Runtime configuration to check for thread starvation. Now is probably a good time for me to bring the UI online so I have some better visibility.

[geofmureithi]

Hmm, ok noted. I think there is some extra work here then. I would want to do the following:

1. Keep this issue open to track support for Sentinel
2. Commit to an example (which may not work based on your report) but will be good to provide feedback and investigate.

Regarding the UI, redis support is still ify but some basics should be working (I can only do so much, but this is now on top of my list as I am done with the core mysql implementation). As always feel free to report any issues experienced.