Cloudera Search upgrade from 1.1 to 1.

2 through Cloudera Manager Parcels

Note 1: Installation of cloudera search 1.1 was done using parcels.
Note 2: This procedural document is for upgrading cloudera search from 1.1 to 1.
2 using cloudera managed parcel.
Note 3: The parcel SOLR-1.2.0-1.cdh4.5.0.p0.4-el6.parcel is already downloaded to
location.
Note 4: Step 1 is already done in all the environments.
Note 5: Step 2 can be performed any time before maintenance window.
To upgrade Search in a Cloudera Manager managed environment, using parcels:
1. Configure the parcel repository URL/location in CM
1.1. log on to Cloudera Manager (CM)
1.2. In CM home page, go to Administrator ? settings ? parcels

1.3. In the parcels page, search for Remote Parcel Repository URLs parameter.
1.3.1. In the Remote Parcel Repository URLs list, click to open an additional
row
1.3.2. Enter the path http://stpuxa05/cloudera/rhel/parcels/solr/ to the repos
itory you want.
1.3.3. Click Save Changes to have your additions take effect
1.4. Click on save changes
2. Download and Distribute the parcel across all the nodes
2.1. In the Cloudera Manager Admin Console, click the Parcels indicator in th
e top navigation bar ( or ) to go to the Parcels page
2.2. Click on Download for the SOLR-1.2.0-1.cdh4.5.0.p0.4-el6.parcel parcel
2.3. Click Distribute for the SOLR-1.2.0-1.cdh4.5.0.p0.4-el6.parcel parcel
3. Activate the parcel
3.1. In the Cloudera Manager Admin Console, click the Parcels indicator in th
e top navigation bar ( or ) to go to the Parcels page
3.2. Click on Activate for the SOLR-1.2.0-1.cdh4.5.0.p0.4-el6.parcel parcel.
3.3. When prompted, click DO NOT RESTART services at this point click Close t
o remove the pop-up.
4. Restart solr1 services
4.1. Go to CM home page

4.2. Choose Restart option from the drop down corresponding to solr service
4.3. Select Restart on the pop-up window
5. Restart Hbase services
5.1. Restart Region Servers first, three at a time. DO NOT GO WITH THE OPTION R
OLLING RESTART OF REGION SERVERS
5.1.1. Go to CM home page
5.1.2. In the home page, click on hbase ? instances

5.1.3. Search for Any Role Type drop down and select Region server. All the region
servers present in the cluster will be listed
5.1.4. Select three region servers from top by clicking the check box
5.1.5. Search for Actions for Select dropdown and choose Restart option
5.1.6. Repeat the steps 5.1.1 through 5.1.5 until all the region servers are re
started
5.2. Restart Hbase Master
5.2.1. Go to CM home page
5.2.2. In the home page, click on hbase ? instances

5.2.3. Search for Any Role Type drop down and select Master. All the master servers
present in the cluster will be listed
5.2.4. Search for Actions for Select dropdown and choose ROLLING RESTART option
5.3. Restart HBase REST Server
5.3.1. Go to CM home page
5.3.2. In the home page, click on hbase ? instances

5.3.3. Search for Any Role Type drop down and select HBase REST Server. All the Hba
se REST servers present in the cluster will be listed
5.3.4. Search for Actions for Select dropdown and choose Restart option
5.4. Restart Hbase Thirft Server
5.4.1. Go to CM home page
5.4.2. In the home page, click on hbase ? instances

5.4.3. Search for Any Role Type drop down and select HBase Thrift Server. All the H
base Thrift servers present in the cluster will be listed
5.4.4. Search for Actions for Select dropdown and choose Restart option
6. Restart Hue server
6.1.1. Go to CM home page
6.1.2. In the home page, click on Hue ? instances

6.1.3. Select all the roles by clicking on check box adjacent to Name.
6.1.4. Search for Actions for Select dropdown and choose Restart option