From e817c95a78c0b6e8811c6c190b77a509cc68d210 Mon Sep 17 00:00:00 2001 From: David Lee Date: Mon, 15 Jan 2018 18:49:19 +0000 Subject: [PATCH] Fixed typo; corrected note to 'certain databases' --- docs/source/design/hadr/decisions/drb-meeting-20171116.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/source/design/hadr/decisions/drb-meeting-20171116.md b/docs/source/design/hadr/decisions/drb-meeting-20171116.md index 9e6b1a9137..155a7f9e51 100644 --- a/docs/source/design/hadr/decisions/drb-meeting-20171116.md +++ b/docs/source/design/hadr/decisions/drb-meeting-20171116.md @@ -36,11 +36,11 @@ MN highlighted limitations in testability: Azure had confirmed support for geo r The design was noted to be dependent on a lot on external dependencies for replication, with R3's testing capability limited to Azure. Agent banks may want to use SAN across dark fiber sites, redundant switches etc. not available to R3. -MN noted that databases are not yet officially supportedin Corda. +MN noted that certain databases are not yet officially supported in Corda. ### [Near-term-target](./near-term-target.md), [Medium-term target](./medium-term-target.md) -Outlining the hot-cold design, MN Highlighted importance of ensuring only one node is active at one time. MN argued for having a tested hot-cold solution as a ‘backstop’. MN confirmed the work involved was to develop DB/SAN exclusion checkers and test appropriately. +Outlining the hot-cold design, MN highlighted importance of ensuring only one node is active at one time. MN argued for having a tested hot-cold solution as a ‘backstop’. MN confirmed the work involved was to develop DB/SAN exclusion checkers and test appropriately. JC queried whether unknowns exist for hot-cold. MN described limitations of Azure file replication.