Uploaded image for project: 'Solr'
  1. Solr
  2. SOLR-11299 Time partitioned collections (umbrella issue)
  3. SOLR-12521

TRA: evaluate autoDeleteAge independently of when collections are created

    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Open
    • Major
    • Resolution: Unresolved
    • None
    • None
    • SolrCloud
    • None

    Description

      Today, aging out the oldest collection due to exceeding autoDeleteAge occurs immediately before new collections in the Time Routed Alias are created. It's performed by MaintainRoutedAliasCmd. While this is fine, it would be better if this were evaluated at additional circumstances – basically whenever we get new documents. This would make the TRA more responsive to dynamic changes in this metadata and it would allow more effective use of finer granularity of autoDeleteAge than the interval size. Furthermore, once we create new TRA collections preemptively (SOLR-12357), we'll probably want this even more since otherwise the oldest collection will tend to stick around longer. SOLR-12357 could probably share some logic here since both will involve preemptive action (action that does not delay routing the current document) by the TimeRoutedAliasUpdateProcessor, and both need to deal with not overloading the overseer with effectively redundant requests.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              dsmiley David Smiley
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:

                Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 20m
                  20m