You are viewing a plain text version of this content. The canonical link for it is here.

Posted to server-dev@james.apache.org by "Benoit Tellier (Jira)" <se...@james.apache.org> on 2019/10/10 03:46:00 UTC

[jira] [Created] (JAMES-2917) Rely on ElasticSearch routing key

Benoit Tellier created JAMES-2917:
-------------------------------------

             Summary: Rely on ElasticSearch routing key
                 Key: JAMES-2917
                 URL: https://issues.apache.org/jira/browse/JAMES-2917
             Project: James Server
          Issue Type: Improvement
          Components: elasticsearch
            Reporter: Benoit Tellier



Our queries are mostly bounded to a mailbox or an user. We can easily
limit the number of ElasticSearch nodes involved in a given query by 
grouping the underlying documents on the same node using a routingKey.

Without routing key, each shard needs to execute the query. The coordinator
needs also to be waiting for the slowest shard.

Using the routing key unlocks significant throughput enhancement (proportional 
to the number of shard) and also a possible high percentile latencies enhancement. This allows to be more lineary scalable.

However a data reindex is needed.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org