Skip to content
Closed
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
fixup! [ADR] JMAP: Avoid ElasticSearch on critical reads
  • Loading branch information
chibenwa committed Nov 16, 2020
commit a95aa3dfefee5d54922cb34fd6d2bf74da321a18
9 changes: 6 additions & 3 deletions src/adr/0043-avoid-elasticsearch-on-critical-reads.md
Original file line number Diff line number Diff line change
Expand Up @@ -44,9 +44,12 @@ A migration task will be provided for new adopters.

Administrators would be offered a configuration option to turn this view on and off as needed.

If enabled administrators would no longer need to ensure high availability and good performances for ElasticSearch.
We thus expect a decrease in overall ElasticSearch load, allowing savings compared to actual deployments.
Furthermore, we expect better performances by resolving such queries against Cassandra.
If enabled, given clients following well defined Email/query requests, administrators would no longer need
to ensure high availability and good performances for ElasticSearch to ensure availability of basic usages
(mailbox content listing).

Given these pre-requisites, we thus expect a decrease in overall ElasticSearch load, allowing savings compared
to actual deployments. Furthermore, we expect better performances by resolving such queries against Cassandra.

The expected added load to Cassandra is low, as the search is a simple Cassandra read. As we only store messageId,
Cassandra dataset size will only grow of a few percents if enabled.
Expand Down