[ 
https://issues.apache.org/jira/browse/SOLR-658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Shalin Shekhar Mangar updated SOLR-658:
---------------------------------------

    Description: 
This is a requirement for java based Solr replication 

Usecase for arbitrary index directory:
if the slave has a corrupted index and the filesystem does not allow 
overwriting files in use (NTFS) replication will fail. The solution is to copy 
the index from master to an alternate directory on slave and load 
indexreader/indexwriter from this alternate directory.



  was:
This is a requirement for java based Solr replication 

Usecase for arbitrary index directory:
if the slave has a corrupted index and the filesystem does not allow 
overwriting files in use (NTFS) replication will fail. The solution is to copy 
the index from master to an alternate directory on slave and load 
indexreader/indexwriter from this alternate directory.

Usecase for arbitrary commitpoint :
Replication can also provide rollback feature . The rollback should be able to 
mention a comitpoint /generation so that rollback is possible.





        Summary: Allow Solr to load index from arbitrary directory in dataDir  
(was: Allow Solr to load index from arbitrary directory in dataDir and Commit 
point)

Removing reference to rollbacks and commit points which is being handled in 
SOLR-670

> Allow Solr to load index from arbitrary directory in dataDir
> ------------------------------------------------------------
>
>                 Key: SOLR-658
>                 URL: https://issues.apache.org/jira/browse/SOLR-658
>             Project: Solr
>          Issue Type: Improvement
>    Affects Versions: 1.4
>            Reporter: Noble Paul
>            Assignee: Shalin Shekhar Mangar
>             Fix For: 1.4
>
>         Attachments: SOLR-658.patch, SOLR-658.patch, SOLR-658.patch, 
> SOLR-658.patch, SOLR-658.patch, SOLR-658.patch
>
>
> This is a requirement for java based Solr replication 
> Usecase for arbitrary index directory:
> if the slave has a corrupted index and the filesystem does not allow 
> overwriting files in use (NTFS) replication will fail. The solution is to 
> copy the index from master to an alternate directory on slave and load 
> indexreader/indexwriter from this alternate directory.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to