[ 
https://issues.apache.org/jira/browse/SOLR-13609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16879412#comment-16879412
 ] 

Christine Poerschke commented on SOLR-13609:
--------------------------------------------

Some of the 
[https://lucene.apache.org/solr/guide/8_1/metrics-reporting.html#index-merge-metrics]
 metrics look like they might also provide the kind of visibility you are 
looking for, though presumably the metrics would not differentiate between any 
merges that you explicitly initiated and any merges that are occurring 
'naturally'.

> Ability to know when an expunge has finished
> --------------------------------------------
>
>                 Key: SOLR-13609
>                 URL: https://issues.apache.org/jira/browse/SOLR-13609
>             Project: Solr
>          Issue Type: Improvement
>      Security Level: Public(Default Security Level. Issues are Public) 
>    Affects Versions: 7.4
>            Reporter: Richard
>            Priority: Major
>
> At the company I work for, we do nightly expunges to clear down deleted docs 
> _(providing the threshold is above 5% in our case)_.
> Whilst this has been okay for us, we want the ability to know when an expunge 
> has completed. At the moment we do some calculations to estimate how long it 
> would take. 
> it would be nice if there was a way to see when an expunge has completed. 
> This could either be by assigning an async id to the call, or any other means 
> of having visibility.
> I started to look into this issue, but saw that the underlying call for 
> expunging starts to use the lucene side of the code base, so thought I was 
> digging to deep, so any advice on this issue would be much appreciated _(as 
> I'm trying to contribute more to OOS)_.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to