You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@lucene.apache.org by ct...@apache.org on 2018/10/22 23:35:14 UTC

[29/50] [abbrv] lucene-solr:jira/solr-12746: 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/bbbb515f
Tree: http://git-wip-us.apache.org/repos/asf/lucene-solr/tree/bbbb515f
Diff: http://git-wip-us.apache.org/repos/asf/lucene-solr/diff/bbbb515f

Branch: refs/heads/jira/solr-12746
Commit: bbbb515fe7b4ad713fb459d1f6096f0ef024cf5f
Parents: ee876c1
Author: David Smiley <ds...@apache.org>
Authored: Mon Oct 15 23:38:09 2018 -0400
Committer: Cassandra Targett <ct...@apache.org>
Committed: Sun Oct 21 15:46:47 2018 -0500

----------------------------------------------------------------------
 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/bbbb515f/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