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

Ana commented on SOLR-12494:
----------------------------

Many thanks for your reply!
I will do so.

Regards,
Ana

On Fri, Jul 27, 2018 at 7:48 PM, Alexandre Rafalovitch (JIRA) <


-- 
The information transmitted is intended only for the person or entity to 
which it is addressed and may contain confidential and/or privileged 
material. Any review, retransmission, dissemination or other use of, or 
taking of any action in reliance upon, this information by persons or 
entities other than the intended recipient is prohibited. If you received 
this in error, please contact the sender and delete the material from any 
computer.


> Migration documentation 
> ------------------------
>
>                 Key: SOLR-12494
>                 URL: https://issues.apache.org/jira/browse/SOLR-12494
>             Project: Solr
>          Issue Type: Wish
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: documentation
>    Affects Versions: 6.4.2
>         Environment: Stage
>            Reporter: Ana
>            Priority: Trivial
>
> I have the following scenario, I'm having a shared cluster solr installation 
> environment (app server 1-app server 2 load balanced) which has 4 solr 
> instances.
>  
> After reviewing the space audit we have noticed that the partition where the 
> installation resides is too big versus what is used in term of space.
>  
> Therefore we have installed a new drive which is smaller and now we want to 
> migrate from the old dive (E:) to the new drive (F).
>  
> Can you please provide an official answer whether this is a supported 
> scenario?
>  
> If yes, will you please share the steps with us?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

Reply via email to