[
https://issues.apache.org/jira/browse/SOLR-7820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14642992#comment-14642992
]
Timothy Potter commented on SOLR-7820:
--------------------------------------
[~andyetitmoves] thanks for the thoughtful feedback here. [~varunthacker] let's
try to get SOLR-6606 committed soon!
I agree that having a larger threshold would have helped my specific situation,
although I've heard having too large of a threshold has its own set of issues.
I'll research the CdcrUpdateLog and revisit the concerns around larger
thresholds. But this definitely seems like a good area to have better
instructions / guidance around esp. for addressing brief outages with very
large indexes.
bq. would be a good enhancement to calculate ahead of time how much space is
needed for recovery and cleanly abort instead of trying and running out of
space.
I'll change the title of this ticket to address that enhancement.
> IndexFetcher should delete the current index directory before downloading the
> new index when isFullCopyNeeded==true
> -------------------------------------------------------------------------------------------------------------------
>
> Key: SOLR-7820
> URL: https://issues.apache.org/jira/browse/SOLR-7820
> Project: Solr
> Issue Type: Improvement
> Components: replication (java)
> Reporter: Timothy Potter
>
> When a replica is trying to recover and it's IndexFetcher decides it needs to
> pull the full index from a peer (isFullCopyNeeded == true), then the existing
> index directory should be deleted before the full copy is started to free up
> disk to pull a fresh index, otherwise the server will potentially need 2x the
> disk space (old + incoming new). Currently, the IndexFetcher removes the
> index directory after the new is downloaded; however, once the fetcher
> decides a full copy is needed, what is the value of the existing index? It's
> clearly out-of-date and should not serve queries. Since we're deleting data
> preemptively, maybe this should be an advanced configuration property, only
> to be used by those that are disk-space constrained (which I'm seeing more
> and more with people deploying high-end SSDs - they typically don't have 2x
> the disk capacity required by an index).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
