[jira] [Commented] (JAMES-2917) Rely on ElasticSearch routing key
[ https://issues.apache.org/jira/browse/JAMES-2917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17035865#comment-17035865 ] René Cordier commented on JAMES-2917: - https://github.com/linagora/james-project/pull/3101 add avoiding specifying an unbounded count of routing keys > 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 >Priority: Major > Labels: perfomance > Fix For: 3.5.0 > > > 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-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-2917) Rely on ElasticSearch routing key
[ https://issues.apache.org/jira/browse/JAMES-2917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16953321#comment-16953321 ] Benoit Tellier commented on JAMES-2917: --- https://github.com/linagora/james-project/pull/2757 is a proposal for this > 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 >Priority: Major > Labels: perfomance > > 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-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-2917) Rely on ElasticSearch routing key
[ https://issues.apache.org/jira/browse/JAMES-2917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16953320#comment-16953320 ] Benoit Tellier commented on JAMES-2917: --- https://github.com/linagora/james-project/pull/2757 is a proposal for this > 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 >Priority: Major > Labels: perfomance > > 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-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-2917) Rely on ElasticSearch routing key
[ https://issues.apache.org/jira/browse/JAMES-2917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16948179#comment-16948179 ] Benoit Tellier commented on JAMES-2917: --- https://github.com/linagora/james-project/pull/2757 proposes this. > 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 >Priority: Major > Labels: perfomance > > 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-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
