Apache
/
lucene
mirror of https://github.com/apache/lucene.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

LUCENE-12357: Update ref guide notes

This commit is contained in:
David Smiley 2018-10-15 23:38:09 -04:00
parent 73a413cd85
commit 306065fca8
1 changed files with 4 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
solr/solr-ref-guide/src/time-routed-aliases.adoc
View File

@ -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 Each time a new collection is added, the oldest collections in the TRA are examined for possible deletion, if that has
been configured. been configured.
All this happens synchronously, potentially adding seconds to the update request and indexing latency. 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. 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 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 * 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. 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 * CloudSolrClient could route documents to the correct collection based on a timestamp instead always picking the
latest. latest.
* Compatibility with CDCR.
== Limitations & Assumptions == Limitations & Assumptions
* Only *time* routed aliases are supported. If you instead have some other sequential number, you could fake it * Only *time* routed aliases are supported. If you instead have some other sequential number, you could fake it