[
https://issues.apache.org/jira/browse/SOLR-5756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14618910#comment-14618910
]
Noble Paul commented on SOLR-5756:
----------------------------------
bq.Do you think it would be safe to do this manually on a running cluster?
It is never fully safe , There are intermediate state changes which you may lose
bq. Suppose I wanted to try to write a patch for this issue to help solve it
for everyone, is that a reasonable thing to attempt for someone with a lot of
ZK knowledge but pretty new to Solr?
bq. Is it too "soon" to do that?
It is not too soon. 5.0 is out for a while
A lot of ZK knowledge is not required to do this. You need to know how overseer
updates state and how states are updated by
{{ZkStateReader.createClusterStateWatchersAndUpdate}} in each node
bq.Can you opine on the specifics of having an API to move the state out vs. a
forced migration?
I shall do a follow up comment of what are the steps involved in actually doing
this
> A utility API to move collections from internal to external
> -----------------------------------------------------------
>
> Key: SOLR-5756
> URL: https://issues.apache.org/jira/browse/SOLR-5756
> Project: Solr
> Issue Type: Bug
> Reporter: Noble Paul
> Assignee: Noble Paul
>
> SOLR-5473 allows creation of collection with state stored outside of
> clusterstate.json. We would need an API to move existing 'internal'
> collections outside
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
