[
https://issues.apache.org/jira/browse/SOLR-11487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gus Heck updated SOLR-11487:
----------------------------
Attachment: SOLR_11487.patch
Patch providing List in Map java representation which was our lesser of 3 evils
choice for comma-string-in-map vs list-in-map vs duplication and moving version
back to alias. The last 2 comments you had are one liners but everything passes
and runs fine without them. I actually am seeing almost 30-40% pass rate with
many JVMS on the core tests, which is a lot better than it was a couple weeks
ago. The good thing about that is the suites after core have been run some too
without problems. I don't know that the sleep makes a difference, I'll leave it
up to you.
One thing I noticed is that the retry for getting updates from Zk if the
version is a hot loop, but it should never really loop more than once or twice
unless there's a bug and we're not getting the updated data, or causing a write
and incrementing the version before checking it again somehow... I had started
putting in a backoff, but then had the thought that that really opens up
vulnerability to a busy system where once it backs off it will never succeed...
see comment/code in ZkStateReader around L1495.
> Collection Alias metadata for time partitioned collections
> ----------------------------------------------------------
>
> Key: SOLR-11487
> URL: https://issues.apache.org/jira/browse/SOLR-11487
> Project: Solr
> Issue Type: Sub-task
> Security Level: Public(Default Security Level. Issues are Public)
> Components: SolrCloud
> Reporter: David Smiley
> Attachments: SOLR_11487.patch, SOLR_11487.patch, SOLR_11487.patch,
> SOLR_11487.patch, SOLR_11487.patch, SOLR_11487.patch, SOLR_11487.patch
>
>
> SOLR-11299 outlines an approach to using a collection Alias to refer to a
> series of collections of a time series. We'll need to store some metadata
> about these time series collections, such as which field of the document
> contains the timestamp to route on.
> The current {{/aliases.json}} is a Map with a key {{collection}} which is in
> turn a Map of alias name strings to a comma delimited list of the collections.
> _If we change the comma delimited list to be another Map to hold the existing
> list and more stuff, older CloudSolrClient (configured to talk to ZooKeeper)
> will break_. Although if it's configured with an HTTP Solr URL then it would
> not break. There's also some read/write hassle to worry about -- we may need
> to continue to read an aliases.json in the older format.
> Alternatively, we could add a new map entry to aliases.json, say,
> {{collection_metadata}} keyed by alias name?
> Perhaps another very different approach is to attach metadata to the
> configset in use?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
