Hi Bernd,

Thank you for the response.. Can you help me with details on what the 
"expungeDeletes=true" will do.. I tried google, but could not find much info 
related to this.

Thanks
Rajan

From: Bernd Fehling <bernd.fehl...@uni-bielefeld.de>
Date: Friday, 25 November 2022 at 6:54 PM
To: users@solr.apache.org <users@solr.apache.org>
Subject: [External] : Re: Solr 8.11.1 Optimise command not deleting the 
deletedDoc
Hi Rajan,

you show first send a commit command with "expungeDeletes=true" and after that 
do an optimize.

Regards, Bernd


Am 25.11.22 um 14:08 schrieb Nagarajan Muthupandian:
> Hi,
>
> I am trying to optimize the core which has deletedDocs of 120755870 ..
>
>
> Status Query for core the give’s the output as below..
>
> curl 
> 'https://urldefense.com/v3/__http://host:port/solr/admin/cores?action=STATUS&core=CORE_1__;!!ACWV5N9M2RV99hQ!NrHkGvqwNOcCEsKJc6eiPAmkDknTA8OTbZsOHiVfDx_LEwiHSGcS-GBEVAn5PshrxGYroUDrJPzYM74177NZrU5ZoCYYxoYFGJXeAtLJLQ$
>  '
>
>
>
> {
>
>    "responseHeader":{
>
>      "status":0,
>
>      "QTime":3},
>
>    "initFailures":{},
>
>    "status":{
>
>      "CORE_1":{
>
>        "name":"CORE_1",
>
>        "instanceDir":"/var/opt/CORE_1",
>
>        "dataDir":"/var/opt/data/CORE_1/",
>
>        "config":"solrconfig.xml",
>
>        "schema":"schema.xml",
>
>        "startTime":"2022-11-22T03:39:23.136Z",
>
>        "uptime":215152252,
>
>        "index":{
>
>          "numDocs":1505,
>
>          "maxDoc":120757375,
>
>          "deletedDocs":120755870,
>
>          "indexHeapUsageBytes":1865236,
>
>          "version":65511,
>
>          "segmentCount":33,
>
>          "current":false,
>
>          "hasDeletions":true,
>
>          
> "directory":"org.apache.lucene.store.NRTCachingDirectory:NRTCachingDirectory(MMapDirectory@/var/opt/data/CORE_1//index
>  lockFactory=org.apache.lucene.store.NativeFSLockFactory@958cb; 
> maxCacheMB=48.0 maxMergeSizeMB=4.0)",
>
>          "segmentsFile":"segments_8o",
>
>          "segmentsFileSizeInBytes":2894,
>
>          "userData":{
>
>            "commitCommandVer":"0",
>
>            "commitTimeMSec":"1668634574253"},
>
>          "lastModified":"2022-11-16T21:36:14.253Z",
>
>          "sizeInBytes":115324109450,
>
>          "size":"107.4 GB"}}}}
>
>
> I tried the below optimize command
>
>
> curl 
> 'https://urldefense.com/v3/__http://host:port/solr/CORE_1/update?optimize=true__;!!ACWV5N9M2RV99hQ!NrHkGvqwNOcCEsKJc6eiPAmkDknTA8OTbZsOHiVfDx_LEwiHSGcS-GBEVAn5PshrxGYroUDrJPzYM74177NZrU5ZoCYYxoYFGJUOSFvLQA$
>  '
>
>
>
> {
>
>    "responseHeader":{
>
>      "status":0,
>
>      "QTime":4}}
>
> Even after executing the above optimize command the status command returns 
> the same stats (assuming default maxSegments=1).
>
> Can someone help me understand why few cores is not getting optimized.. there 
> were few other which got optimized.
>
> Also would like understand the how the optimize command would work for 
> different values of maxSegments (say 2, 5 or N)
>
> Thanks
> Rajan
>

Reply via email to