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

Mark Miller edited comment on SOLR-5656 at 7/9/14 5:41 PM:
-----------------------------------------------------------

ReviewBoard has been setup and this seems like a good issue to trial it with. I 
created a review request: https://reviews.apache.org/r/23371/

I also sent an email to the dev list so that we can have discussion around 
ReviewBoard and the Lucene project.


was (Author: [email protected]):
ReviewBoard has been setup and these seems like a good issue to trial it with. 
I created a review request: https://reviews.apache.org/r/23371/

I also sent an email to the dev list so that we can have discussion around 
reviewboard and the Lucene project.

> Add autoAddReplicas feature for shared file systems.
> ----------------------------------------------------
>
>                 Key: SOLR-5656
>                 URL: https://issues.apache.org/jira/browse/SOLR-5656
>             Project: Solr
>          Issue Type: New Feature
>            Reporter: Mark Miller
>            Assignee: Mark Miller
>         Attachments: SOLR-5656.patch, SOLR-5656.patch, SOLR-5656.patch, 
> SOLR-5656.patch
>
>
> When using HDFS, the Overseer should have the ability to reassign the cores 
> from failed nodes to running nodes.
> Given that the index and transaction logs are in hdfs, it's simple for 
> surviving hardware to take over serving cores for failed hardware.
> There are some tricky issues around having the Overseer handle this for you, 
> but seems a simple first pass is not too difficult.
> This will add another alternative to replicating both with hdfs and solr.
> It shouldn't be specific to hdfs, and would be an option for any shared file 
> system Solr supports.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to