From 315ef919bdc1332ceca519f13fb4e32c9a67d67d Mon Sep 17 00:00:00 2001 From: Thien-Thi Nguyen Date: Tue, 5 Jan 2021 16:33:39 -0500 Subject: fix typo: s/update/updated/ --- design-documents/011-auditor-db-sync.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'design-documents') diff --git a/design-documents/011-auditor-db-sync.rst b/design-documents/011-auditor-db-sync.rst index bf8f9a52..505f7b49 100644 --- a/design-documents/011-auditor-db-sync.rst +++ b/design-documents/011-auditor-db-sync.rst @@ -78,7 +78,7 @@ Proposed Solution tables from other data *if* we need to recover from backup. * On schema migration, halt exchange, once auditor DB has synchronized, update all DB schema (the "ingress" DB schema - may be update automatically when the exchange DB schema is + may be updated automatically when the exchange DB schema is migrated, but the "trusted" DB of the auditor must most likely be manually migrated), then finally resume "ingress" to "trusted" helper-based DB synchronization and restart the exchange. -- cgit v1.2.3 From 275de898eeff924b0658adbbc3cd51cadcd749d6 Mon Sep 17 00:00:00 2001 From: Thien-Thi Nguyen Date: Tue, 5 Jan 2021 16:36:05 -0500 Subject: fix typo: s/ingres/ingress/ --- design-documents/011-auditor-db-sync.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'design-documents') diff --git a/design-documents/011-auditor-db-sync.rst b/design-documents/011-auditor-db-sync.rst index 505f7b49..f4befdfa 100644 --- a/design-documents/011-auditor-db-sync.rst +++ b/design-documents/011-auditor-db-sync.rst @@ -131,7 +131,7 @@ Drawbacks is the answer, to be investigated what performs better. * A malicious exchange could theoretically send expensive transactions to the auditor via the replication mechanism (possibly ones that - it did not even execute locally itself) to DoS the "ingres" + it did not even execute locally itself) to DoS the "ingress" database. This would be noticed primarily by load monitoring or even the auditor lagging unusually far behind the exchange's transaction history. We believe this is acceptable, -- cgit v1.2.3