Solr Update Handler Test
The Update Handler handles requests to change the index. It basically takes care of any add, deletes, commits optimization etc.When new data is added to Solr or existing data is modified it si thr job of update handler to update the indexes so that future searches will remain as effective. This test monitors the Update Handler by collecting sme of the key metrics like number of adds, number of commits, number of deletes and merges etc. It is important for administrators to know if all of these operation are working efficiently to ensure that overall health of search capability is good.
Target of the test : Apache Solr server
Agent deploying the test : An internal/remote agent
Outputs of the test : One set of results for each Solr core in Apache Solr setup.
Parameter | Description |
---|---|
Test period |
How often should the test be executed |
Host |
The IP address of the host for which this test is to be configured. |
Port |
The port at which the target Apache Solr server listens to. |
Username & Password |
If JMX requires authentication only (but no security), then ensure that the user and password parameters are configured with the credentials of a user with read-write access to JMX. |
Confirm Password |
Confirm the password by retyping it in this box. |
SSL |
By default, SSL is disabled for Apache Solr, accordingly SSL flag is set to No by default. If the flag is set to Yes, the eG Agent will start communicating with Apache Solr server HTTPS. |
Timeout |
By default timeout is 5 secods. |
Detailed Diagnosis |
To make diagnosis more efficient and accurate, the eG Enterprise embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option. The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled:
|
Measurement | Description | Measurement Unit | Interpretation |
---|---|---|---|
Adds |
Indicates the total number "Add" requests since last commit. |
Number |
A large number of these operation can cause issue with indexes if update handler is not working porperly to update the indexes. |
Auto Commits |
Indicates the number of auto commits executed. |
MB |
A large number of these operation can cause issue with indexes if update handler is not working porperly to update the indexes. |
Commits |
Indicates the total number of commits executed. |
Number |
A large number of these operation can cause issue with indexes if update handler is not working porperly to update the indexes. |
Deletes by ID |
Indicates the total number of deletes by Id which are yet uncommitted. |
Number |
A large number of these operation can cause issue with indexes if update handler is not working porperly to update the indexes. |
Deletes by query |
Indicates the total number of deletes by query which are yet uncommitted. |
Number |
A large number of these operation can cause issue with indexes if update handler is not working porperly to update the indexes. |
Documents pending |
Indicates the number of error messages received while performing addition/deletion/commit/rollback actions on documents over the lifetime of the core. |
Number |
A large number of these operation can cause issue with indexes if update handler is not working porperly to update the indexes. |
Errors |
Indicates the number of cache entries during the last measurement period |
Number |
A large number of these operation can cause issue with indexes if update handler is not working porperly to update the indexes. |
Expunge deletes |
Indicates the number of commit commands issues with expunge delete. |
Percent |
A large number of these operation can cause issue with indexes if update handler is not working porperly to update the indexes. |
Merges |
Indicates the number index merges that have happened during the lifetime of the core. |
Number |
A large number of these operation can cause issue with indexes if update handler is not working porperly to update the indexes. |
Optimizes |
Indicates the number of optimize commands that have been issues so far. |
Number |
A large number of these operation can cause issue with indexes if update handler is not working porperly to update the indexes. |