Overview

The SearchStax Managed Search service lets you create as many deployments as you require for the unique needs of your Solr-based applications. When you create a deployment you can choose your Cloud Provider, Plan, and Solr version. Once a deployment is created, you can secure it using advanced networking capabilities. Then you can configure and populate your Solr collections.

Contents:

1. Creating a Deployment
2. Managing Your Deployments
3. Charges
4. Changing/Scaling a Deployment
5. Deleting a Deployment

Creating a Deployment

Deployments are created via the Dedicated Infrastructure screen.

To create a Deployment:

1. From your Dedicated Infrastructure screen, click on New Deployment.
2. Provide a name for the Solr Deployment.
3. Specify the Cloud Provider, Region, Plan Tier, and Solr version for your Deployment.
4. Select the number of nodes and amount of memory/disk space.
5. Click on Create Deployment.

To create a new Dedicated Deployment, click the Create Deployment button. This opens an interactive page that lets you configure all aspects of your deployment and see what each decision means in terms of your monthly fees.

The first decision is whether to use a single node or a cluster. In general, single nodes are for experiments and proof-of-concept systems, while clusters support production systems. (Often a client will create multiple clusters for production, disaster recovery, UAT testing, and QA.)

Enter a name for the deployment, and select an appropriate Solr version. Note that only certain versions of Solr are compatible with Sitecore.

Choose a Cloud Provider and a Region for the new deployment.

The sliders let you select the number of nodes to include in the cluster, and how much memory and disk space to include on each node.

Plan Tiers correspond to SearchStax Managed Search Support-Level Agreements (SLAs). They define what levels of responsiveness, up-time guarantees, and access to special features the deployment will have.

Backups are optional. If this will be a production system, daily backups are recommended.

Review the deployment specifications and the monthly fee and then proceed to the checkout page.

You can secure your new Solr deployment using its Security Settings. This lets you secure the cluster via a specific IP address, a range of IP addresses, and/or through Solr Basic Auth.

Managing Your Deployments

SearchStax Managed Search deployments are administered through the Dedicated Infrastructure screen and the Deployment Details overview.

When you create a Solr Deployment you will be sent an email with useful helper scripts for easily configuring Zookeeper, creating Solr collections, and populating your Solr collections with data (documents). You can then use the SearchStax Managed Search Dashboard to monitor the performance of your Solr deployment, including key server metrics such as CPU and Memory utilization, Search Throughput, and Indexing throughput. These reports help you to tune your Solr deployments.

The Termination Lock button blocks any attempt to delete this deployment until you manually reset the button.

Charges

SearchStax Managed Search pay-as-you-go deployments are billed automatically each month based on the chosen plan.

Scaling a Deployment

Dedicated clusters may be scaled up or down to meet seasonal needs.

You can add nodes to clusters on the Deployment Details page, and, once added, you can click a link to delete the node again. (See the note on “Short-Lived Deployments,” above, for billing details.)

Bear in mind that adding a node to an existing cluster might be a sign that you need to upgrade your deployment to the next plan.

Deleting a Deployment

You can delete a deployment from the SearchStax Managed Search Dashboard (list view) or the Deployment Details screen.

In the List View, use the trash can icon at the right end of the display:

On the Deployment Details screen, look for the trash can icon in the header:

To delete a deployment, click the trash can icon and then type the deployment name into the dialog box.

Deleting a deployment takes a few minutes to complete.

There are rare occasions when a new deployment fails to complete the setup and configuration process. In that case, the trash can icons are unavailable. Select the “Card” view of the deployment list and click the Edit Pencil icon. This exposes a menu where the final option is “Terminate.”

Questions?

Do not hesitate to contact the SearchStax Support Desk.

The post Dedicated Deployments appeared first on SearchStax Docs.

The SearchStax Managed Search service Quick Start page contains everything you need to know to take a Dedicated Solr Deployment for a test drive. We supply the Solr configuration and sample documents for you to load to make your trial go smoothly.

This page was illustrated using a Free Trial user account. The deployment is a two-node cluster. The instructions work equally well with a paid account except that the UI will offer you a broader range of features and options. Note that the instructions apply to both Linux and Windows.

Contents of this Solr Guide:

1. Set Up an Account
2. Create a Solr Deployment
3. Install the Zookeeper Script
4. Create an IP Filter
5. Upload a Solr Configuration
6. Create a Collection
7. Index Documents
8. Search the Collection

1. Set Up an Account

To sign up as a SearchStax user, go to the SearchStax Free-Trial page. You may create a single-node deployment or a two-node cluster and experiment with it for 14 days, free of charge. No credit card number is required.

For additional information concerning accounts, see the Account Setup page.

2. Create a Solr Deployment

Deployments are created from the SearchStax Dashboard.

For a Free Trial, the system will take you directly to the New Deployment screen.

You will need to choose the appropriate Cloud Provider and the Plan that works for you. (The Free Trial program offers a single-node deployment or a two-node cluster in Amazon Web Services (AWS), Microsoft Azure, or Google Cloud.)

SearchStax offers a wide variety of Solr versions for your convenience. For this exercise, we assume that your deployment uses Solr-9.8.1.

It will be necessary to choose a Cloud Provider and a region to house your deployment. Choose the region that is close to you.

The next few controls are grayed out in the Free Trial experience. In a paid account, they would let you set the number of nodes, size of memory and disk storage, support plan tier, and backup frequency.

This summary table describes your deployment and its features. In paid account, It also calculates the cost of this combination of features.

It usually takes five minutes to set up a single-node deployment, and up to fifteen minutes to set up a cluster, using AWS or GCP. Azure setup times range from twenty minutes to an hour. Feel free to explore our documentation until the process is completed.

When the deployment is ready, view the deployment summary card on the Dedicated Infrastructure screen by clicking the “Card View” button (upper right):

This display tells us that the deployment is up and running.

To check the health of the deployment, click QuickStart, then Monitoring and CPU, Memory, JVM. Check the boxes beside the two Solr servers (usually nodes 4 and 5). You can easily see that the system is running under almost zero load (CPU below 2% in this image).

To view the server details, click Overview. This opens the deployment details page.

The details page shows the status of all deployment servers plus the URLs of the deployment’s Solr HTTP Endpoint and Zookeeper Ensemble. This is an NDC4 cluster. It has two Solr servers (nodes 4 and 5) and three independent Zookeeper servers. The table shows the health of all five servers.

The Termination Lock button shields this deployment from unintended deletion by someone using the SearchStax API. It is a peace-of-mind feature that does not enter into the current exercise.

3. Install the Zookeeper Script

Apache ZooKeeper is a service for maintaining configuration information. In a SearchStax Managed Search deployment, Zookeeper is the central repository for your Solr configuration files.

A single-node deployment (such as the NDN2) has only one Zookeeper instance. It runs on the same server as Solr. A cluster (NDC4) has three Zookeeper instances, each on its own independent server. They are collectively called “the ensemble.” (For more information on this architecture see Apache Solr Architectures for Cloud Deployment.)

Zookeeper includes a standard command-line script, zkcli.sh, for managing your Zookeeper ensemble. Solr provides a modified version of ZKCLI that includes Solr-specific features. We have further modified the Solr ZKCLI by adding some data for this QuickStart exercise. We provide both Linux and Windows versions of the script.

You can download the SearchStax ZKCLI ZIP file here: searchstax-client-master.zip. It is about 270 MB.

Unzip the file on your local computer. The top-level directory is \searchstax-client-master. There are subdirectories for different versions of Solr.

Navigate to the scripts subdirectory (\searchstax-client-master\solr-9\scripts). Locate zkcli.sh and zkcli.bat in that directory. These are the Linux and Windows versions of the script, respectively.

4. Create an IP Filter

When SearchStax creates a new Solr deployment, it locks down the Zookeeper ensemble so that it cannot be reached from the Internet. To upload a configuration to Zookeeper, you have to add an IP Filter that whitelists your work computer or subnet.

1. From within a Deployment’s details page (where you saw the list of servers), click on the Security > IP filter menu.
2. Click on Add Row.
3. Add a specific IP address in the empty field. Note that SearchStax can detect your computer’s IP address. Click My current IP to enter it automatically.
4. Select the service you need access to (Zookeeper in this case).
5. Click Save changes.

To remove a filter, click on the X button and then Save Changes.

5. Upload a Solr Configuration

It is easy to deploy your Solr project to the cloud. The first step is uploading your Solr configuration files to the Zookeeper ensemble of your SearchStax deployment. Zookeeper, in turn, distributes the configuration files to the server(s) that need them.

We have provided example configuration files and data for the purposes of this exercise.

In a terminal window, navigate to the \searchstax-client-master\solr-9\scripts directory and then run the appropriate script:

Linux (Bash):

$ ./zkcli.sh -zkhost <zookeeper URL> -cmd upconfig -confdir <Solr configuration> -confname <configuration name>

Windows PowerShell:

> .\zkcli.bat -zkhost <zookeeper URL> -cmd upconfig -confdir <Solr configuration> -confname <configuration name>

where <zookeeper URL> is the Zookeeper Ensemble URL from your deployment details page. If you are running a cluster, the <zookeeper URL> is a comma-separated list. Use the entire list as the <zookeeper URL>.

<Solr configuration> is the path to your Solr configuration directory, which is ../configsets/_default/conf/ for the solr-9 ZKCLI. <configuration name> will be Zookeeper’s internal name for this configuration (test).

Look in your email for a message from SearchStax announcing the creation of your new deployment. This message contains a customized ZKCLI command with values appropriate to your project. You can copy and paste the command into your Bash or PowerShell window.

./zkcli.sh -zkhost ss123456-na1labcj-1-us-west-aws.searchstax.com:2181,ss123456-na1labcj-2-us-west-2-aws.searchstax.com:2181,ss123456-na1labcj-3-us-west-2-aws.searchstax.com:2181 -cmd upconfig -confdir ../configsets/_default/conf/ -confname test

ZKCLI always issues boilerplate warnings, so don’t be alarmed by those messages. When successful, you’ll also see a number of INFO messages scroll by but no explicit confirmation of success. This is normal.

6. Create a Collection

A collection is a logical index. The next step is to create a collection so we can send data to it.

The easiest way to create a collection in the Solr versions supported by SearchStax is to open the Solr Dashboard and fill out a simple form:

From the Deployment Details page, click on the deployment’s Solr HTTP Endpoint URL. Select the Collections tab on the left. Click the Add Collection button.

Fill out the pop-up form:

1. For this exercise, the name is testcollection.
2. When we uploaded the configuration using ZKCLI, we called the config set test.
3. The numShards parameter should always be 1 unless a Solr expert tells you otherwise.
4. The replicationFactor is the number of Solr servers in your deployment. It is critical to set it correctly. It does not always default to the correct value.
5. Click the Add Collection button.

7. Index Documents

Once the Solr index has been initialized by creating a collection, you can load your documents.

In a Bash or PowerShell window, navigate to the \searchstax-client-master\solr-9\data directory. This is where our example data file, sample.json resides. This file contains two extremely brief documents:

[
 {"id" : "TestDoc1", "title_s" : "test1"},
 {"id" : "TestDoc2", "title_s" : "another test"}
]

Run the following command in the Linux terminal window:

Linux (Bash) or Windows PowerShell:

$ curl -X POST -H 'Content-type:application/json' -d '<datafile>'
    '<Solr HTTP Endpoint><collectionName>/update?commit=true'

<datafile> is the path and file name of the file to upload (either the full file path or ‘@sample.json‘ if the focus is in the data directory). <Solr HTTP Endpoint> is the URL from the SearchStax dashboard for your deployment. <collectionName> is the name of the new Solr collection (testcollection).

The email message about your new collection contains a cURL command similar to this one. Copy it and paste it into your command window. Note: For Windows, put single-quote (‘) marks around ‘@sample.json’.

$ curl -X POST -H 'Content-type:application/json' -d '@sample.json' 'https://ss123456-na1labcj-us-west-aws.searchstax.com/solr/testcollection/update?commit=true'

On success, you’ll see a message confirming that two records have been committed to the index.

8. Search the Collection

A simple query will demonstrate that all of the previous steps have been accomplished correctly.

The easiest way to query your collection is to return to the Solr Dashboard and use the query page.

1. From the Deployment Details page, click on the deployment’s Solr HTTP Endpoint URL.
2. Select the testcollection in the droplist in the left margin.
3. Click the Query tab, also in the left margin.
4. Scroll to the bottom of the Query page and click the Execute Query button.

If you have been successful, you will see our two sample documents in the response as shown above.

Note the URL at the top of this display. You can copy/paste this URL into any browser and obtain the same response. The only difference is that certain characters must be % encoded in the query string, notably the “*:*” must be encoded as *%3A*.

Next Steps

Success! You have created your first SearchStax deployment with a Solr Collection. You have deployed a Solr project, loaded documents into the index, and have performed a successful query!

Now you can explore the rest of the documentation to learn the details of everything that SearchStax can do for you.

Contact Us!

Don’t hesitate to reach out to the SearchStax Support Desk. We are happy to answer your questions.

The post Dedicated Quick Start appeared first on SearchStax Docs.