13:32:10 GMT <damnski> howdy, I am having a problem with with redis 3.2.4 replication syncing when a slave reboots, this time due to a hypervisor failure.  Running 3 hosts each with a redis instance and sentinel instance.
13:55:39 GMT <damnski> posting snippets of both master node and slave node errors.  maxmemory 2gb && maxmemory-policy allkeys-lru
13:55:59 GMT <damnski> http://skicentral.tv/redis_sync_replication_pastebin.txt
13:58:15 GMT <damnski> the master node01 ended up death spiraling with no response from the OS console - had to reset.  also node 2 became unSYNCed.  I can post full log if necessary.
13:59:17 GMT <damnski> Is this a known issue in this version?  I see version 4.0+ has a new replication engine.
20:51:26 GMT <nDuff> I'm trying to figure out how automation for redis-sentinel deployment should look. Am I correct to understand there should be one redis master and N>=2 slaves *before* sentinel is deployed/started (thus, that sentinel isn't intended to be used for initial master election)?
21:02:13 GMT <minus> nDuff: sentinel picks up the slaves attached to a master, so theoretically you just have to point all sentinels against one master and then attach slaves to it
21:07:19 GMT <nDuff> @minus, ...right -- if I'm trying to automate that, though, it means I need to have something other than sentinel responsible for setting up that initial master and attaching slaves to it.
21:10:42 GMT <nDuff> (in an ideal world, I'd be able to deploy N identically-configured nodes as a starting point; it sounds like that's not the case here).