Any further thoughts on this?
I'd like to proceed with the PR for SOLR-16962 [1], which I've updated
with a fix to address now-once-again-relevant SOLR-6537 [2] (at
whatever point SOLR-16962 made it impossible to configure an external
tlog, SOLR-6537 (cleanup/deletion of external tlog) became
> useful to separate the location to use some fast local SSDs vs slower but
> larger storage for the main index
Exactly.
And yes, the duplicity of nomenclature is a large part of what I'm
suggesting to deal with here ... it's very confusing. But having
recently been pretty deep in this part of
FWIW I've never heard of anyone customizing that. I suppose it might be
useful to separate the location to use some fast local SSDs vs slower but
larger storage for the main index?
I've noticed an annoying duplicity in nomenclature here -- is it the Update
Log or the Transaction Log? And
Thanks Ilan, this seems good. In addition to addressing practical
concerns, this could also be an opportunity to clarify the semantics
around updateLog/tlog configuration:
In looking closely at this code, my understanding is that the
`${solr.ulog.dir:}`
setting in solrconfig.xml currently defines
Re backcompat issue: might be an option to fix that config but use a
different name for it then, so that any currently existing (and ignored)
config continues to be ignored.
Ilan
On Thu, Sep 7, 2023, 6:14 PM Michael Gibney
wrote:
> I'd like to call some extra attention to SOLR-16962 [1]. I'm
I'd like to call some extra attention to SOLR-16962 [1]. I'm fairly
certain that it's been years since it has actually worked to specify
tlog dir in solrconfig.xml `` element. I've opened a PR
that fixes this, but it involves making some decisions about edge-case
handling, for which I'd appreciate
