You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Ana (JIRA)" <ji...@apache.org> on 2018/07/27 12:03:00 UTC

[jira] [Commented] (SOLR-12494) Migration documentation

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

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

Hi Erick,

I followed your suggestion in migrating the data and swapping the drive
letter and now i ran in the following scenario:

SOLR 1 issues -Server 1

Cannot run zookeeper services on all intances

Error in the zookeeper logs:

Unable to load database on disk
java.io.IOException: The accepted epoch, 19 is less than the current epoch,
63d

Research over the internet
https://issues.apache.org/jira/browse/ZOOKEEPER-2307

Notes:
I can navigate to http://xx.xxx.xxx.xxx:8986/solr/ - however i cannot see
the collections and instances
http://xx.xxx.xxx.xxx:8983/solr/en_cache/admin/ping -ok   --instance 1
http://xx.xxx.xxx.xxx:8984/solr/en_cache/admin/ping - 500 internal
error   --instance
2
http://xx.xxx.xxx.xxx:8985/solr/en_cache/admin/ping - 500 internal
error  --instance
3
http://xx.xxx.xxx.xxx:8986/solr/en_cache/admin/ping - 500 internal
error  --instance
4

SOLR 2 -Server 2

http://xx.xxx.xxx.xxx:8983/solr/en_cache/admin/ping -ok   --instance 1
http://xx.xxx.xxx.xxx:8984/solr/en_cache/admin/ping - 500 internal error
--instance 2
http://xx.xxx.xxx.xxx:8985/solr/en_cache/admin/ping - 500 internal
error  --instance
3
http://xx.xxx.xxx.xxx:8986/solr/en_cache/admin/ping - 500 internal
error  --instance
4
http://localhost:8983/solr/#/en_cache_shard1_replica2- icann see the
collections

All services are started and are in running state

However the error found is:
Zookeeper error: Cannot open channel to X at election address

Architecture:

We have 2 SOLR servers Load balanced SOLR1 and SOLR 2 whereby we have
installed 4 instances on both SOLRs.

Many thanks in advance!!
Ana




On Thu, Jul 5, 2018 at 8:29 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org