[
https://issues.apache.org/jira/browse/SOLR-16194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17536751#comment-17536751
]
Gus Heck commented on SOLR-16194:
---------------------------------
This issue can create a (recoverable, but potentially down time inducing) mess
with TRA's if the user tries to adjust TRA parameters on an existing TRA (which
should be fine for some parameters). I suspect this hasn't been noticed because
such updates are an infrequent and uncommon activity and in cases where the
time interval is not updated it probably causes a series of attempts to
recreate collections which (correctly) silently fail, but if the time interval
is changed and thus the created collections no longer overlap with the existing
ones and many useless collections can be created, and possibly previous
collections will be left out of the TRA. The result would look like data loss
initially, though the prior collections would still exist and the TRA could
still be manually re-assembled.
> Updating Time Routed Alias Parameters Loses Existing Collection List
> --------------------------------------------------------------------
>
> Key: SOLR-16194
> URL: https://issues.apache.org/jira/browse/SOLR-16194
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: SolrCloud
> Affects Versions: 8.11.1
> Reporter: Matt Kuiper
> Assignee: Gus Heck
> Priority: Major
>
> While updating a TRA with a new interval I noticed that the collection list
> stored in the alias.json is modified so that any previous created collections
> are dropped from the list and only the collection related to the TRA start
> date remains.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
