lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [jira] [Commented] (SOLR-11147) Restore command does not copy .fdt file correctly
Date Tue, 01 Aug 2017 11:07:00 GMT


MANUEL S. FUENTES commented on SOLR-11147:

Some more workarounds/hints:

- Apart from deleting the index before restoring, you also get a consistent restore if you
optimize the index previously.
- If you have already restored but you're missing the big fdt file, the best you can do is
unload the core temporarily (the missing file shows up just when you do it).

> Restore command does not copy .fdt file correctly
> -------------------------------------------------
>                 Key: SOLR-11147
>                 URL:
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: Backup/Restore
>    Affects Versions: 6.3, 6.6
>         Environment: Windows 2012 R2. 
> Oracle Corporation Java HotSpot(TM) 64-Bit Server VM 1.8.0_91 25.91-b15-
> Solr 6.3 (6.6) Standalone
>            Reporter: MANUEL S. FUENTES
>            Priority: Minor
> This is my first issue here, so excuse me if anything is wrong.
> When recovering a core backup according to the API, the process goes normally restoring
all the files except the biggest (.fdt file). If you restart SoLR then that core is not loaded.
> Some other times I've found that the .fdt file is copied partially, so restarting has
the same effect. The log says that the .fdt file is copied, but it's not.
> The only workarounds found are:
> - Copy the .fdt file manually from the backup
> - Deleting the index completely before restoring
> - Optimizing the index before restarting SoLR (weird with one file missing but worked).
> Thanks,
> Manuel F.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message