Hi Shawn,
Thanks for the response.
Below are the high level Installation steps used for ZK and Solr setup in
Windows* D:\ drive*. Could you please go through once and suggest possible
solution/steps needs to be done for the setup moving to the E:\ Drive(New
drive) without any impacting to the existing application.
We have two cluster servers (IP addresses xx.xxx.xxx.100 and xx.xxx.xxx.101)
*1. Zookeeper installation*
xx.xxx.xxx.100 D:/Stage4/zookeeper/instance1
xx.xxx.xxx.101 D:/Stage4/zookeeper/instance2 and
D:/Stage4/zookeeper/instance3
*2. Example for editing zoo.cfg file as per mentioned like below did for 3
instances.*
*tickTime=2000*
*initLimit=10syncLimit=5dataDir= D:/Stage
/zookeeper/instance1/dataclientPort=xxxxserver.1= xx.xxx.xxx.101
:xxx7:xxx7server.2= xx.xxx.xxx.101 :xxx8:xxx8server.3= xx.xxx.xxx.101
:xxx9:xxx9**3.
Go to the main folder D:/Stage4*
a) Right click on folder “zookeeper” -> Properties -> Security -> Edit ->
Add -> Add both service accounts
b) Under permissions -> give full control
c) Click Ok.
d) Similarly, add the admin’s name who is working on the set up, and
provide full permission to this folder
*4. Create zookeeper as a Windows service*
a) Create a folder named “nssm” in D: drive.
b) Open command prompt and navigate to /nssm-2.24/win64.
c) Type the command to create windows service.
nssm.exe install Zookeeper_Stage4_instance1
“D:\Stage4\zookeeper\instance1\bin\zkServer.cmd”
nssm.exe install Zookeeper_Stage4_instance2
“D:\Stage4\zookeeper\instance2\bin\zkServer.cmd”
nssm.exe install Zookeeper_Stage4_instance3
“D:\Stage4\zookeeper\instance3\bin\zkServer.cmd”
e) An warning message may appear with text: Administrator access is needed
to install a service
Press “Yes” in the popup that appears.
It will continue and create the service.
*5. Go to Windows Start, search “services.msc” and open it. *
a) From Services window, select the newly created service and double click
on it.
b) Service Properties window opens.
a. Go to Log on tab.
b. Select “Log on as this account”
c. Provide the service account name and password
d. Click OK.
h) Start the service.
i) Status should show Running like shown in the below screenshot.
*6) Verify if zookeeper is set up correctly.*
Go to D:/Stage4/zookeeper/instance<number>
Folder named “logs” should be created, with the file zookeeper.log
*7. Solr installation*
There are 2 solr nodes below are the Server IP and its Folder structure
xx.xxx.xxx.100 D:/Stage4/solr/
xx.xxx.xxx.101 D:/Stage4/solr/
*8. Edit the file solr.cmd present in /bin folder*
Change the value of SOLR_JAVA_MEM from -Xms512m -Xmx512m to –Xms6g –Xmx6g
*9. Editing in solr_start.cmd file as per environment specific:*
D:\Stage4\Solr\instance2\bin\solr start -f -c -p xxxx -z
"xx.xxx.xxx.100::xxx7,xx.xxx.xxx.101:xxx8,xx.xxx.xxx.101:xxx9"
*10. Go to the main folder D:/Stage4 *
a) Right click on folder “solr” -> Properties -> Security -> Edit -> Add ->
Add both service accounts
b) Under permissions -> give full control
c) Click Ok.
d) Similarly, add the admin’s name who is working on the set up, and
provide full permission to this folder
Create solr as a Windows service
a) If “nssm” folder is not present in the machine, then create a folder
named “nssm” in D: drive.
b) Open command prompt and navigate to /nssm-2.24/win64.
c) Type the corresponding commands as in below table
10.240.194.100 nssm.exe install Solr_Stage4_instance1
“D:\Stage4\solr\instance1\bin\solr_start.cmd”
10.240.194.101 nssm.exe install Solr_Stage4_instance2
“D:\Stage4\solr\instance2\bin\ solr_start.cmd”
d) A warning message may appear with text: Administrator access is needed
to install a service.
Press “Yes” in the popup that appears.
*11. Go to Windows Start, search “services.msc” and open it. *
f) From Services window, select “Solr_Stage4_instance<number>” service and
double click on it.
g) Service Properties window opens.
a. Go to Log on tab.
b. Select “Log on as this account”
c. Provide the service account name and password
d. Click OK.
h) Start the service
*12. Copy deployment files from file share*
*13. Collection creation and validation and 1) Upload config files to
zookeeper:*
a) Open command prompt and navigate to
D:\Stage4\solr\instance2\server\scripts\cloud-scripts
b) Then type the following command: zkcli.bat –zkhost
“xx.xxx.xxx.100:xxx0,xx.xxx.xxx.101:xxx1,xx.xxx.xxx.101:xxx2” –cmd upconfig
–confname en_cache_config –confdir
D:/Stage4/PMDM_CacheIndexer/en_cache_config/conf
c) Once the upload is done, no success or failure message will be displayed
*14. Scheduling indexing tasks*
Thanks,
Srinivas
On Mon, Jun 25, 2018 at 11:34 AM, Shawn Heisey <[email protected]> wrote:
> On 6/25/2018 1:41 AM, Srinivas Muppu (US) wrote:
>
>> Is there any possible solution/steps for the moving solr installation
>> setup
>> from 'E' drive to 'D'-Drive (New Drive) without any impact to the existing
>> application(it should not create re indexing again)
>>
>
> You started a previous thread on this topic five days ago. I replied to
> the list at that time. This time I'm going to include you as a BCC -
> normally I do not do this, because list membership is usually required to
> post to the list. Here is the previous reply:
>
> ---------
>
> Exactly what needs to be done will be highly dependent on how you
> installed Solr on your system. The project doesn't have any specific
> installation steps for Windows, so we have absolutely no idea what you have
> done. Whoever set up your Solr install is going to know a LOT more about
> it than we ever can.
>
> At a high level, without any information specific to your setup, here's
> the steps you need:
>
> * Stop Solr
> * Move or copy files to the new location
> * Change the solr home and possibly other config
> * Start Solr.
>
> ---------
>
> It's very important that you understand that we have absolutely no idea
> how you've set *anything* up, so we cannot tell you what files need to be
> changed or where they will be. If you can get in touch with the person who
> set your Solr up, they should be able to help you make the change that you
> want to make.
>
> Thanks,
> Shawn
>
>
______________________________________________________________________
The information transmitted, including any attachments, 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, and all liability
arising therefrom is disclaimed. If you received this in error, please contact
the sender and delete the material from any computer. PricewaterhouseCoopers
LLP is a Delaware limited liability partnership. This communication may come
from PricewaterhouseCoopers LLP or one of its subsidiaries.
