From 2af4ee0928d66b2d3f100d3b145c1b445f962072 Mon Sep 17 00:00:00 2001 From: James Phillips Date: Tue, 16 Aug 2016 15:48:22 -0700 Subject: [PATCH] Update outage.html.markdown --- website/source/docs/guides/outage.html.markdown | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/website/source/docs/guides/outage.html.markdown b/website/source/docs/guides/outage.html.markdown index 98ba0a067e..b6453c0b14 100644 --- a/website/source/docs/guides/outage.html.markdown +++ b/website/source/docs/guides/outage.html.markdown @@ -61,10 +61,10 @@ first start after upgrading. Be sure to leave `raft/peers.info` in place for pro operation.

-Note that using `raft/peers.json` for recovery can cause uncommitted Raft log -entries to be committed, so this should only be used after an outage where no +Using `raft/peers.json` for recovery can cause uncommitted Raft log entries to be +implicitly committed, so this should only be used after an outage where no other option is available to recover a lost server. Make sure you don't have -any automated processes that will put the peers in place on a periodic basis, +any automated processes that will put the peers file in place on a periodic basis, for example.