Advisory questions
Hello, I have tried to subscribe to general forums but i wasn't able to, hence i would appreciate if we can keep this thread and have the replies over email. I want to have more background about the dependencies of solr/zookeeper services and the task schedulers -ful/incremental indexing. So in case of a manual restart or unplanned reboot our services are set to start manually hence i wanted to setup the dependency between them so I wanted to confirm if the order is the following one: 1.First Zookeeper service 2.Solr service If there is any documentation on this matter please let me know. Another similar topic is the following one: Yesterday we encountered a dirty reboot and right after the incremental indexing task was failing with : " Job Id: 172605, Status: Failed Indexing failed. Refer incremental-indexing.log for more information. java.lang.Exception: File ./index.properties does not exist to read the property "last_index_time"" The file was there but was empty without any timestamp So i did the following: Do the following: 1.open it check if is empty or not and take a backup of it 2.disable the task, take the content of that file from stage 3.check in the database the last successful one --timestamp 4.updat that file with the above timestamp 5.probably it wont work 6.if doesn t work update the timestamp with the current date and run the job,, once got successfully completed end it disable it and update the timestamp with the value from 2nd step 5 update [X].[dbo].[C_CACHE_SEARCH_INDEX_JOB_AUDIT] set Status = 'Failed' where Status ='In Progress' 6.enable the task and run it and also monitor it will complete successfully So my question is when this scenario can happen and also is there any procedure to stop/start the components in a controlled way? Any maintenance procedure will be highly appreciated. Many thanks in advance, Ana -- 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. Please familiarize yourself with our privacy policy.
SOLR issues after data Migration
Hi, I have the following architecture : 2 SOLR servers Load balanced SOLR1 and SOLR 2 whereby we have installed 4 instances on both SOLRs. Version: What happened was that the E partition (where all instances where installed) has been oversized therefore we wanted to migrate the data on a new drive and swap the letter drivers. The same was adviced also when I raised the concern on an older topic [https://lists.apache.org/thread.html/096ac35a70c31846fbe73694046d6f adc8fe930b822bddf338babcc2@%3Csolr-user.lucene.apache.org%3E] After applying the changes i am running under following scenarios: 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 Could you kindly reply back to this email with your suggestions? Last time i couldn't see the thread on Apache site so I would appreciate if you would reply back on this email thread also for visibility purposes (as many people are CCed). Thanks, Ana -- 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.
Re: SOLR migration
Hello guys, I would appreciate if you could kindly treat this topic with priority as the lack of documentation is kind of a blocker for us. Thanks in advance, Ana On Mon, Jun 18, 2018 at 4:56 PM, Ana Mercan (RO) wrote: > Hi, > > 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? > > Thanks, > > Ana > -- 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.
SOLR migration
Hi, 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? Thanks, Ana -- 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.
