Hi,
I have never used TRA, but a client of mine is considering it. A few questions.
A) Do you have links to talks (slides/video) on the feature? Or blog posts
going into more detail than the RefGuide?
B) For ingestion performance, sharding may make sense. But only for the current
collection. Have anyone tried merging "static" shards?
C) Is there a trick to have more relicas on recent collections than old ones?
D) Is there a way to manage what nodes that get selected for new collections,
or you need to rely on replica placement policies?
E) How do you guys ensure you get a good fill-rate on the nodes, and what
procedure do you use when adding more nodes in the cluster?
* I.e. do you simply add a few new nodes and let Solr automatically place
new collections onto those?
F) How many sub-collections/cores do you plan for on a single node?
* You could try to configure the "rotation interval" such that a node gets
filled by a single core, but that seems hard to predict
* Having a too rapid "rotation interval" will leave behind too many cores
per node, causing inefficiencies?
* Have you found a strategy to balance this? I'd likely try to plan for 10
cores per node, and monitor fill-rate such that I (manually) add more HW once a
threshold is reached.
G) Have anyone tried backup of a TRA? Does it even work, or do you need to run
the command for each single collection?
H) A typical requirement is to migrate all data from one cluster to a new
cluster on a newer version or with a new schema. Have you tried doing that with
a TRA?
* Would you need to migrate each sub collection at a time?
* Will TRA on the new cluster accept that someone "external" adds
collections, and how it is initialized/bootstrapped to fill the internal
collection registry?
That's what I could think of before trying the feature. I'm sure there would be
other questions after some trial and error :)
Jan
