Re: Drive Change for existing Solr Setup
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=server.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 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 -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” 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 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 creat
Drive Change for existing Solr Setup
Hi Solr Team, After subscription done with the *solr-user@lucene.apache.org * sending below issue details again to the Solr Mailing list. Please help us as earliest. As part of Solr project installation setup and instances(including clustered solr, zk services and indexing jobs scheduler services) are available in Windows 'E:\ ' drive in production environment. As business needs to remove the E:\ drive, going forward D:\ drive will be used and operational. 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) Please let us know your suggestions if required will create the JIRA ticket for this. Your earliest response will be appreciated!! Thanks, Srinivas __ 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.
Reg Solr System configuration
Hi Solr Team, We are facing Solr System Configuration issues(Existing Solr installation setup needs to move window New Drive) which needs help. Please let us know whom to post our Questions/Queries. Thanks, Srinivas __ 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.
Re: WELCOME to solr-user@lucene.apache.org
xLJF5n7j > kXE+R3STA6F1XfvdCznfy5qCY2BbHBqfex3UO+njnp+ > tiwfl5FDpzR9ZA9Hy2WYe4F9y > 6GrupTi+IXDLY62n0/Zz8YEDlPUc0SBT/xOAuU12vB7jvGzgAJX+ > lYep328dPosKWz19 > XWFX2+AlhKPCGGIIDI6Feg9PJAWMa7SDmAANdhgllYE+4e3zmHqaF+ > WpQNUnY3IilWFD > 1HzYLoQHjIadBI5NSEaUFYVSFnQqXM8HgHA7XNnOdIkCvQ31bN/ > lxGpNSXGf7oF+dnjl > iK0w== > X-Gm-Message-State: APt69E3yfSdF87bxkF9n5hmTozBUwH > y58gShrB0LRowp3Ybc2Hc2qngP > QkwovWm0dNpmuubj581RcNVsdl3OWLIfgOEJ5tLVFjvGG1lDuKqxEyaqJu7G > 2VLMiNyjQbC+VBh > /xBkVKBcmlGhU+GLDbrY/8wehbaVUwwb+nC7oyB3M1oUZLVm/ > JLS4nzivYyoanQlhOQDap2F8I8 > xxOA1JDbXY2JriUs+DdC/5uWELOQWBMt1QDO1YB4fyu+QmHMkgPZhcBQ== > X-Received: by 2002:ab0:4327:: with SMTP id k36-v6mr7127945uak.53. > 1529907723023; > Sun, 24 Jun 2018 23:22:03 -0700 (PDT) > X-Google-Smtp-Source: ADUXVKKcjyGQTtCYFeZxnYdzVYgfTPxRo3YM1Tj6/ > GvKEVjyagsv9UZ3JSAxnUzhEW+DXQLOudxgkNqMZzVaIMh36ZI= > X-Received: by 2002:ab0:4327:: with SMTP id k36-v6mr7127936uak.53. > 1529907722631; > Sun, 24 Jun 2018 23:22:02 -0700 (PDT) > MIME-Version: 1.0 > Received: by 2002:ab0:5207:0:0:0:0:0 with HTTP; Sun, 24 Jun 2018 23:21:42 > -0700 (PDT) > In-Reply-To: <1529907299.75224.ez...@lucene.apache.org> > References: <1529907299.75224.ez...@lucene.apache.org> > From: "Srinivas Muppu (US)" > Date: Mon, 25 Jun 2018 02:21:42 -0400 > Message-ID: mail.gmail.com> > Subject: Re: confirm subscribe to solr-user@lucene.apache.org > To: solr-user-sc.1529907299.ncdjeeajnmilfkaeoigb-srinivas.muppu= > pwc@lucene.apache.org > Content-Type: multipart/alternative; boundary=" > 592156056f71660f" > X-Proofpoint-PoS-Virus-Version: PwCProdVirusScanned > X-Proofpoint-Spam-Details: rule=notspam policy=outboundspam score=0 > priorityscore=1501 malwarescore=0 > suspectscore=14 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 > lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 > classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-180621 > definitions=main-1806250075 > > __ 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.
Drive Change for Solr Setup
Hi Solr Team,My Solr project installation setup and instances(including clustered solr, zk services and indexing jobs schedulers) is available in Windows 'E:\ ' drive in production environment. As business needs to remove the E:\ drive, going forward D:\ drive will be used and operational.Is there any possible solution/steps for the moving solr installation setup from 'E' drive to 'D' Drive without any impact to the existing application(it should not create re indexing again)Please let us know your suggestions if required will create the JIRA ticket for this.Your earliest help will be appreciated!!Thanks,Srinivas __ 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.
