title: Redis keyspace notifications subscriptions in distributed environment using ServiceStack
body: <p>We have some Redis keys with a given TTL that we would like to subscribe to and take action upon once the TTL expires (a la job scheduler).</p>
  
  <p>This works well in a single-host environment, and when you subscribe in ServiceStack, using its Redis client, to <code>'__keyspace@0__:expired'</code>, that service will pick it and take action. That's fantastic...</p>
  
  <p>... until you have a high-availability topology set up, with more than one API instance in that cluster. Then every single host appears to be picking up on that message and potentially doing things with it.</p>
  
  <p>I know keyspace notifications don't work exactly the same as traditional pub/sub or messaging-layer events, but is there a way to perform some kind of acknowledgement on these kinds of events, so that, at the end of the day, only one host will carry on with the task?</p>
  
  <p>Otherwise, is there a way to delay a message publishing?</p>
  
  <p>Thanks!</p>