Question
Achmea
NL
Last activity: 1 May 2017 5:38 EDT
Information about Search indexing DSS
Hello.
I would like to know as much as possible about the effects of all the Dynamic System Settings regarding the Search Engine. After our upgrade from 7.1.8 to 7.2.2 we see some strange behaviour. For example we see our Search index host node settings changed after we restart.
These are the Dynamic System Settings I would like to have explained:
Thank in advance!
IN
Request you to take a look at https://pdn.pega.com/sites/pdn.pega.com/files/help_v722/procomhelpmain.htm#engine/search/eng-full-text-search-con.htm%3FTocPath%3DSystem%2520management%7CFull-text%2520search%7C_____0
Could observe explanations pertaining to the configurations which you had specified.
Accepted Solution
Pegasystems Inc.
IN
Hello,
Please find the description for the required DSS below:
|
indexing/distributed/search_timeout_millis
|
Timeout for a search request (in milliseconds)
|
|
indexing/distributed/queue/maxrecords
|
Maximum number of records to process from the queue in one invocation by the incremental indexing agent
|
|
indexing/distributed/attachmentcharacterlimit
|
Character limit for parsed attachment content
|
|
indexing/distributed/batch/requestbatchsize
|
Size of a bulk index request for batch indexing
|
|
indexing/distributed/batch/workqueuesize
|
Size of the in-memory work queue for batch indexing
|
|
indexing/distributed/batch/numworkers
|
Number of worker threads (batch requestor tasks) for batch indexing |
Hello,
Please find the description for the required DSS below:
|
indexing/distributed/search_timeout_millis
|
Timeout for a search request (in milliseconds)
|
|
indexing/distributed/queue/maxrecords
|
Maximum number of records to process from the queue in one invocation by the incremental indexing agent
|
|
indexing/distributed/attachmentcharacterlimit
|
Character limit for parsed attachment content
|
|
indexing/distributed/batch/requestbatchsize
|
Size of a bulk index request for batch indexing
|
|
indexing/distributed/batch/workqueuesize
|
Size of the in-memory work queue for batch indexing
|
|
indexing/distributed/batch/numworkers
|
Number of worker threads (batch requestor tasks) for batch indexing
|
|
indexing/distributed/index_enabled
|
Option to enable / disable indexing using elasticsearch (Internal)
|
|
indexing/distributed/search_enabled
|
Option to enable / disable search using elasticsearch (Internal)
|
|
indexing/distributed/enabled
|
Option to enable / disable the elasticsearch embedded node when a PRPC node initializes (Internal)
|
|
indexing/distributed/search/fuzzy/max_expansions
|
The maximum number of terms the search string can expand to
|
|
indexing/distributed/search/fuzzy/prefix_length
|
Prefix length of the fuzzy query; the number of initial characters that should be entered for getting the results
|
|
indexing/distributed/host_node_monitoring
|
Option to enable/ disable email notification after the reconfiguration is complete; when a new node is added/removed as a search node
|
|
indexing/distributed/search/fuzzy/enabled
|
Option to enable/disable fuzzy search
|
|
indexing/distributed/search/fuzzy/fuzziness
|
Fuzziness of search query. AUTO /ZERO/ONE/TWO
|
|
indexing/distributed/autonodecleanupandreindex
|
Used for removing any stale index node entries found during server start-up; Also used for triggering full indexing if none of the index nodes are available [Available only from 7.2.2]
|
|
indexing/useDataInstances
|
Option to enable usage of Data-CustomProperties-Search instances instead of pySearchModel data transforms to get the custom list of index fields.
|
|
indexing/distributed/rebuild_indexes_onupgrade
|
Option to chose the indexes that need to be re-built during an upgrade (Default: Rule/Data)[Available from 7.2.2]
|
Sincerely,
Pawan