You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@lucene.apache.org by da...@apache.org on 2018/10/16 22:53:55 UTC
[40/50] [abbrv] lucene-solr:jira/http2: LUCENE-12357: Update ref
guide notes
LUCENE-12357: Update ref guide notes
Project: http://git-wip-us.apache.org/repos/asf/lucene-solr/repo
Commit: http://git-wip-us.apache.org/repos/asf/lucene-solr/commit/306065fc
Tree: http://git-wip-us.apache.org/repos/asf/lucene-solr/tree/306065fc
Diff: http://git-wip-us.apache.org/repos/asf/lucene-solr/diff/306065fc
Branch: refs/heads/jira/http2
Commit: 306065fca8a4b540f197aca5d53e46f2700c25bc
Parents: 73a413c
Author: David Smiley <ds...@apache.org>
Authored: Mon Oct 15 23:38:09 2018 -0400
Committer: David Smiley <ds...@apache.org>
Committed: Mon Oct 15 23:38:09 2018 -0400
----------------------------------------------------------------------
solr/solr-ref-guide/src/time-routed-aliases.adoc | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/lucene-solr/blob/306065fc/solr/solr-ref-guide/src/time-routed-aliases.adoc
----------------------------------------------------------------------
diff --git a/solr/solr-ref-guide/src/time-routed-aliases.adoc b/solr/solr-ref-guide/src/time-routed-aliases.adoc
index 2e4160e..a97d051 100644
--- a/solr/solr-ref-guide/src/time-routed-aliases.adoc
+++ b/solr/solr-ref-guide/src/time-routed-aliases.adoc
@@ -60,6 +60,8 @@ TRUP first reads TRA configuration from the alias properties when it is initiali
Each time a new collection is added, the oldest collections in the TRA are examined for possible deletion, if that has
been configured.
All this happens synchronously, potentially adding seconds to the update request and indexing latency.
+If `router.preemptiveCreateMath` is configured and if the document arrives within this window then it will occur
+asynchronously.
Any other type of update like a commit or delete is routed by TRUP to all collections.
Generally speaking, this is not a performance concern. When Solr receives a delete or commit wherein nothing is deleted
@@ -78,12 +80,11 @@ Some _potential_ areas for improvement that _are not implemented yet_ are:
* Ways to automatically optimize (or reduce the resources of) older collections that aren't expected to receive more
updates, and might have less search demand.
-* New collections ought to be created preemptively, as an option, to avoid delaying a document that does not yet have
- a collection to go to.
-
* CloudSolrClient could route documents to the correct collection based on a timestamp instead always picking the
latest.
+* Compatibility with CDCR.
+
== Limitations & Assumptions
* Only *time* routed aliases are supported. If you instead have some other sequential number, you could fake it