Skip to content

Comment on Redis Sentinel design draft 1.1

Comments

I find this bit interesting:

Modify clients configurations when a slave is elected.

(I assume elected == promoted). This is an idea I haven't really seen in other servers/services before, and I'm curious how this will be implemented. I assume some sort of pub/sub subscription to each of the slaves so that your server is notified when one of them takes over? It sounds tricky, but really interesting. Document seems a bit scant on details for this part at the moment.

Regardless, really thrilled about this project.

[Edit: Ah, I missed this part:

client reconfiguration are performed running user-provided executables (for instance a shell script or a Python program) in a user setup specific way.]

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.