Page History

Some Aspire components must be configured before the settings.json is read like the NoSQL provider. This configuration is done using environment variables or JVM parameters.

Some components configured in the settings file like the Worker and Manager node allows configuration with environment variables or JVM parameters as an alternative

Easy Heading Free

navigationTitle

Paneltitle

	On this

page

wrapNavigationText
Page

toc

true

maxLevel3

navigationExpandOption	expand-all-by-default

Format

All properties can be passed either as a environment variable or as a JVM parameter. The "." and "_" characters can be replaced with each other.

Code Block

language	bash
theme	RDark

SET aspire_.noSql_.elastic_.server=http://localhost:9200 //Setting a property as a environment variable
java -Daspire.noSql.elastic.server=http://localhost:9200 //Passing a property like JVM parameter

Warning
In the case of environment variables that , property name should always use "_" instead of "."

Elasticsearch NoSQL Provider

Memory settings

In Linux based systems, the memory usage can be changed with the following environment variablesBellow are the list of properties to configure the Elasticsearch NoSQL Provider

Parameter

Required

Default

Description

aspire.

noSql

max.

elastic

heap.

server

memory

yes

http://localhost:9200

The elasticsearch server url to use. It can be multiple urls separated by ","

no

2g

Maximum Heap the JVM will request and use from the host system

aspire.max.metaspace.size

no

256m

Maximum metaspace the JVM will request and use from the host system.

In windows-based systems, if using the aspire.bat file, the memory usage should be changed in the aspire.bat itself. Otherwise, if it is running as a Windows Service:

Browse to
- HKEY_LOCAL_MACHINE / SOFTWARE / WOW6432Node / Apache Software / Procrun 2.0 / AspireService / Parameters / Java
Modify JvmMs and JvmMx to what you need (in bytes), and then restart the service.

Elasticsearch NoSQL Provider

Below are the list of properties to configure the Elasticsearch NoSQL Provider

Enables elasticsearch AWS authenticationauthentication.useCredentialsProviderChainOption to use the AWS credentials provider chain to get the credentialsawsaccess.keyAWS access key for aws.secret.keyAWS secret key for aws.region AWS regionkeepSearchContextAliveThe amount of time to keep elasticsearch scrolls requests search context alive using "m" as a unitmaxRequestSizeThe maximum size for a bulk request. The value can be specified in B, K, M and G unitsmaxConnectionsmaxRetries amount of times to retry each requestretriesWaitTimeThe time to wait in ms between retriesuseThrottlingEnables requests throttling to elasticsearchthrottlingRate5000 throttling rate in msthrottlingConnectionRate500 maximum requests allowed in the period specified by the throttlingRatewaitTime4293000 time to wait in ms before retrying a 429 errorbulkEnables using bulk for requestsbulkSize500 documents to include in a bulk requestbulkInactivityTimeout5 inactivity in s before flushing a bulk requestbulkRegularTimeout30 maximum amount of time in s for a bulk request to be kept in memory before flushing

Parameter	Required	Default	New & Available from	Description
aspire.noSql.elastic.authentication.basic	no	false	Enables elasticsearch basic authentication
aspire.noSql.elastic.user	no	null	The elasticsearch user to use for basic authentication
aspire.noSql.elastic.password	no	null	The elasticsearch password to use for basic authentication
aspire.noSql.elastic.authentication.aws	no	false
aspire.noSql.elastic.	server	no	false	yes	http://localhost:9200		The Elasticsearch server URL to use. It can be multiple URLs separated by ","
aspire.noSql.elastic.	authentication.	basic	no	null	false		Enables Elasticsearch basic authentication
aspire.noSql.elastic.	user	no	null		The Elasticsearch user to use for basic authentication
aspire.noSql.elastic.	password	no	null		The	Elasticsearch password to use for basic authentication
aspire.noSql.elastic.authentication.	aws	no	5m	false		Enables Elasticsearch AWS authentication
aspire.noSql.elastic.authentication.	useCredentialsProviderChain	no	10485760B	false		Option to use the AWS credentials provider chain to get the credentials
aspire.noSql.elastic.aws.	assumeRole	no	100	The maximum amount of connections to mantain open.
aspire.noSql.elastic.maxConnectionsPerRoute	no	10	The maximum amount of connections per server
false	5.0.3	If a role must be assumed to access Elasticsearch. Must be true/false
aspire.noSql.elastic.	aws.roleArn	no	null	5.0.3	The	Role ARN to be assumed.
aspire.noSql.elastic.	aws.access.key	no	5000	null		AWS access key for authentication
aspire.noSql.elastic.aws.secret.	key	no	false	null		AWS secret key for authentication
aspire.noSql.elastic.aws.	region	no	null		The	AWS region
aspire.noSql.elastic.	keepSearchContextAlive	no	5m		The	amount of	time to keep Elasticsearch scrolls requests search context alive using "m" as a unit
aspire.noSql.elastic.	maxRequestSize	no	10485760B		The	maximum size for a bulk request. The value can be specified in B, K, M and G units
aspire.noSql.elastic.	maxConnections	no	true	100		The maximum number of connections to keep open.
aspire.noSql.elastic.	maxConnectionsPerRoute	no	10		The maximum number of	connections per server
aspire.noSql.elastic.readTimeout	no	30000		The socket timeout.
aspire.noSql.elastic.	connectionTimeout	no	15000		The	connection timeout.
aspire.noSql.elastic.	maxRetries	no	3		The
aspire.noSql.elastic.debugFile	no	null	The path to the debug file, request to ES are logged in this file
aspire.noSql.elastic.mappingFile	no	null	The file path (including file name) that includes the mapping for the indexes used by Aspire. By default mapping included in the provider is used
aspire.noSql.elastic.index.prefix	no	aspire	The prefix to use for the indexes created by the provider
aspire.noSql.elastic.debug	no	false	Enables debug logging information
aspire.noSql.elastic.usePooling	no	true	Enables HTTP connection pooling

SSL Certificates

Bellow are the list of properties to configure the SSL Certificates

ParameterRequiredDefaultDescriptioncom.accenture.aspire.ssl.trustAllnofalseConfigure if all certificates should be trustedcom.accenture.aspire.ssl.overwriteFactorynofalseConfigure if the created key managers should overwrite the Java connection factorycom.accenture.aspire.ssl.truststore.filenonullThe path of the trust store filecom.accenture.aspire.ssl.truststore.passwordnonullThe trust store file passwordcom.accenture.aspire.ssl.truststore.typenojksThe file format of the trust store filecom.accenture.aspire.ssl.keystore.filenonullThe path of the key store filecom.accenture.aspire.ssl.keystore.passwordnonullThe key store file passwordcom.accenture.aspire.ssl.keystore.typenojksThe file format of the key store file

Security and encryption

Bellow are the list of properties related to the Aspire security and encryption

ParameterRequiredDefaultDescriptionaspire.ldap.bind.dn.passwordnonullThe password of the User DN. Not required if the authentication is anonymous aspire.encryption.key.filenonullThe file path (including file name) where master key is located, if not provided a in memory hardcoded key will be used, for production installations it must be always provided.

number of times to retry each request
aspire.noSql.elastic.retriesWaitTime	no	5000		The time to wait in ms between retries
aspire.noSql.elastic.useThrottling	no	false		Enables requests throttling to Elasticsearch
aspire.noSql.elastic.throttlingRate	no	5000		The throttling rate in ms
aspire.noSql.elastic.throttlingConnectionRate	no	500		The maximum number of requests allowed in the period specified by the throttlingRate
aspire.noSql.elastic.waitTime429	no	3000		The time to wait in ms before retrying a 429 error
aspire.noSql.elastic.bulk	no	true		Enables using bulk for requests
aspire.noSql.elastic.bulkSize	no	500		The maximum number of documents to include in a bulk request
aspire.noSql.elastic.bulkInactivityTimeout	no	5		The inactivity in s before flushing a bulk request
aspire.noSql.elastic.bulkRegularTimeout	no	30		The maximum amount of time in s for a bulk request to be kept in memory before flushing
aspire.noSql.elastic.debugFile	no	null		The path to the debug file, request to ES are logged in this file
aspire.noSql.elastic.mappingFile	no	null		The file path (including file name) that includes the mapping for the indexes used by Aspire. By default, the mapping included in the provider is used
aspire.noSql.elastic.index.prefix	no	aspire		The prefix to use for the indexes created by the provider
aspire.noSql.elastic.debug	no	false		Enables debug logging information
aspire.noSql.elastic.usePooling	no	true		Enables HTTP connection pooling
aspire.nosql.elastic.timeSeriesType	no	index	5.0.3, 5.3 (Opensearch)	Enables rollover possibility for audit, error, log time series index. Value "index" - default without rollover, Value "dataStream" - rollover based on data stream. Value "dataStreamOpensearch" - rollover based on Opensearch data stream.
aspire.nosql.elastic.ilmPolicyFile	no	default provider policy file	5.0.3	The file path (including file name) that includes the ilm policy file for the indexes used by Aspire. Used only for the time series option "dataStream*".
aspire.nosql.elastic.indexTemplateFile	no	default provider template file	5.0.3	The file path (including file name) that includes the template file for the indexes used by Aspire. Used only for the time series option "dataStream*".

Index Sharding and Replicas settings

Each index sharding and replicas settings can be changed by using a custom mappingFile and configuring the aspire.noSql.elastic.mappingFile property.

Since 5.0.1, when using the default mapping settings, you can use the following prefix parameter:

aspire.noSql.elastic.index.shards.[indexName]
- Should hold an integer specifying the number of shards for the given index
aspire.noSql.elastic.index.replicas.[indexName]
- Should hold an integer specifying the number of replicas for the given index

If none of these properties are specified, the default replicas and shard number of the cluster will be used (usually 1 shard and 1 replica).

The different index names available are:

audit
base
errors
hierarchy
log
map
queue
retryLog
set
settings
snapshot
updateQueue
identityCache

SSL Certificates

Bellow are the list of properties to configure the SSL Certificates

Parameter	Required	Default	Description
aspire.ssl.trustAll	no	false	Configure if all certificates should be trusted
aspire.ssl.overwriteFactory	no	false	Configure if the created key managers should overwrite the Java connection factory
aspire.ssl.truststore.file	no	null	The path of the trust store file
aspire.ssl.truststore.password	no	null	The trust store file password
aspire.ssl.truststore.type	no	jks	The file format of the trust store file
aspire.ssl.keystore.file	no	null	The path of the key store file
aspire.ssl.keystore.password	no	null	The key store file password
aspire.ssl.keystore.type	no	jks	The file format of the key store file

Security and encryption

Below are the list of properties related to the Aspire security and encryption

Parameter	Required	Default	Description
aspire.ldap.bind.dn.password	no	null	The password of the User DN. Not required if the authentication is anonymous
aspire.security.api.auditing	no	true	It audits the Aspire API calls. It is available from Aspire 5.1 and on.

Encryption

When a password/secret/token in a configuration must be persisted, Aspire encrypts it and stores it encrypted. The default encryption mechanism is AES 256 given a local key. AWS KMS encryption can be used instead as of version 5.0.3

Standard AES 256 Encryption with local key

Parameter Required Default Description

aspire.encryption.key.file

no

null

(Optional) Path (including file name) where the encryption key is located, if not provided a default in-memory key will be used, for production installations it must be always provided. This can also be passed as a JVM parameter or as an environment variable, aspire_encryption_key_file.

This should be a 32 byte file, if longer, the first 32 bytes will be used as the encryption key.

Grant read access to the Aspire user only (chmod 400 <file>)

This file could be generated randomly

$ head -c 32 /dev/urandom > encryption.key

AWS KMS Encryption

Available since Aspire 5.0.3, Uses AWS Key Management Service (KMS) to encrypt the sensitive data. It uses a key in KMS to encrypt and decrypt data. See more details about this encryption provider at Aspire KMS encryption

Parameter	Required	Default	Description
aspire.encryption.kms.roleARN	no	null	(Optional) If the KMS service must be accessed through the assumption of an IAM role, specify the role ARN.
aspire.encryption.kms.keyARN	yes	N/A	The KMS key ARN. See Aspire KMS encryption for more information about creating a KMS key for Aspire.
aspire.encryption.kms.region	yes	N/A	The AWS region on which the KMS service will be used
aspire.encryption.kms.accessKey	no	null	(Optional) Specify the access key if static credentials must be used. If this is not specified, the Default Credential Provider Chain will be used.
aspire.encryption.kms.secretKey	no	null	(Optional) Specify the secret key if static credentials must be used. If this is not specified, the Default Credential Provider Chain will be used.

Worker Node

These properties will be used by all worker nodes in the cluster.

Parameter	Required	Default	Description
aspire.node.worker.maxMemQueueSize	yes	4000	The maximum number of items to keep in the in-memory queue
aspire.node.worker.queueSizeThreshold	yes	0.5	The capacity threshold of the in memory queue before requesting more items to the managers
aspire.node.worker.cleanUpWaitTime	yes	300000	The wait time in ms for the thread that checks the connectors clean up threshold
aspire.node.worker.cleanUpThreshold	yes	3600000	The time in ms for a connector to be idle before being removed from memory
aspire.node.worker.maxEnqueueRetries	yes	5	The number of retries to enqueue an item into the framework pipeline
aspire.node.worker.workflow.appCleanUpWaitTime	yes	60000	The wait time in ms for the thread that checks the workflow application's clean-up threshold
aspire.node.worker.workflow.appCleanUpThreshold	yes	3600000	The time in ms for a workflow application to be idle before being removed from memory
aspire.node.worker.tags	no		The tags of the worker node. These tags will determine which items this node can process. It should be a comma separated list of tags.
aspire.node.worker.entryProcessorBaseSleep	yes	10	The base sleep time in ms for the thread in charge of queuing received items into the connector framework pipelines
aspire.node.worker.entryProcessorMaxSleep	yes	2000	The maximum sleep in ms for the thread in charge of queuing received items into the connector framework pipelines
aspire.node.worker.entryProcessorMaxIterations	yes	5	The number of iterations without queuing items before in increasing the sleep time
aspire.node.worker.entryProcessorMultiplier	yes	1.25	The multiplier used to increase the sleep time after the specified iterations without queuing items
aspire.node.worker.batchLoaderBaseSleep	yes	10	The base sleep time in ms for the thread in charge of requesting batches to the manager nodes
aspire.node.worker.batchLoaderMaxSleep	yes	2000	The maximum sleep in ms for the thread in charge of requesting batches to the manager nodes
aspire.node.worker.batchLoaderMaxIterations	yes	5	The number of iterations without receiving batches from the managers nodes before in increasing the sleep time
aspire.node.worker.batchLoaderMultiplier	yes	1.25	The multiplier used to increase the sleep time after the specified iterations without receiving batches from the managers nodes
aspire.node.worker.connectionTimeout	yes	20000	The connection timeout for requests to other aspire nodes
aspire.node.worker.socketTimeout	yes	20000	The socket timeout for requests to other aspire nodes
aspire.node.worker.maxRetries	yes	3	The number of retries for requests to other aspire nodes
aspire.node.worker.proxyHost	no	null	The proxy host to use for requests to other aspire nodes
aspire.node.worker.proxyPort	no	0	The proxy port to use for requests to other aspire nodes. Must be provided if the proxyHost is configured
aspire.node.worker.proxyUser	no	null	The proxy user to use for requests to other aspire nodes
aspire.node.worker.proxyPassword	no	null	The proxy password to use for requests to other aspire nodes.
aspire.node.worker.pingFrequency	yes	15000	The frequency for the node to ping to Elasticsearch. The pings are used to determine if a node is alive and working properly
aspire.node.worker.nodeFailureTimeout	yes	30000	The ping timeout used to determine if a node is not working. The node will be marked as failed in this case and the node eventually will shut down itself

Manager Node

These properties will be used by all manager nodes in the cluster.

Parameter	Required	Default	Description
aspire.node.manager.scanBatchCreatorBaseSleep	yes	30	The base sleep time in ms for the thread in charge of creating batches from the scan queue
aspire.node.manager.scanBatchCreatorMaxSleep	yes	2000	The maximum sleep in ms for the thread in charge of creating batches from the scan queue
aspire.node.manager.scanBatchCreatorMaxIterations	yes	10	The number of iterations without creating new scan batches before in increasing the sleep time
aspire.node.manager.scanBatchCreatorMultiplier	yes	1.25	The multiplier used to increase the sleep time after the specified iterations without creating new scan batches
aspire.node.manager.processBatchCreatorBaseSleep	yes	30	The base sleep time in ms for the thread in charge of creating batches from the process queue
aspire.node.manager.processBatchCreatorMaxSleep	yes	2000	The maximum sleep in ms for the thread in charge of creating batches from the process queue
aspire.node.manager.processBatchCreatorMaxIterations	yes	10	The number of iterations without creating new process batches before in increasing the sleep time
aspire.node.manager.processBatchCreatorMultiplier	yes	1.25	The multiplier used to increase the sleep time after the specified iterations without creating new process batches
aspire.node.manager.crawlProgressManagerBaseSleep	yes	100

Worker Node

These properties will be used by all worker nodes in the cluster.

ParameterRequiredDefaultDescriptioncom.accenture.aspire.node.worker.maxMemQueueSizeyes1000The maximum number of items to keep in the in memory queuecom.accenture.aspire.node.worker.queueSizeThresholdyes0.75The capacity threshold of the in memory queue before requesting more items to the managerscom.accenture.aspire.node.worker.cleanUpWaitTimeyes300000The wait time in ms for the thread that checks the connectors clean up thresholdcom.accenture.aspire.node.worker.cleanUpThresholdyes3600000The time in ms for a connector to be idle before being removed from memorycom.accenture.aspire.node.worker.maxEnqueueRetriesyes5The number of retries to enqueue a item into the framework pipelinecom.accenture.aspire.node.worker.workflow.appCleanUpWaitTimeyes60000The wait time in ms for the thread that checks the workflow applications clean up thresholdcom.accenture.aspire.node.worker.workflow.appCleanUpThresholdyes3600000The time in ms for a workflow application to be idle before being removed from memorycom.accenture.aspire.node.worker.tagsnoThe tags of the worker node. These tags will determine which items this node can processcom.accenture.aspire.node.worker.entryProcessorBaseSleepyes200The base sleep time in ms for the thread in charge of enqueueing received items into the connector framework pipelinescom.accenture.aspire.node.worker.entryProcessorMaxSleepyes10000The maximum sleep in ms for the thread in charge of enqueueing received items into the connector framework pipelinescom.accenture.aspire.node.worker.entryProcessorMaxIterationsyes5The number of iterations without enqueueing items before in increasing the sleep timecom.accenture.aspire.node.worker.entryProcessorMultiplieryes2The multiplier used to increase the sleep time after the specified iterations without enqueueing itemscom.accenture.aspire.node.worker.batchLoaderBaseSleepyes200The base sleep time in ms for the thread in charge of requesting batches to the manager nodescom.accenture.aspire.node.worker.batchLoaderMaxSleepyes10000The maximum sleep in ms for the thread in charge of requesting batches to the manager nodescom.accenture.aspire.node.worker.batchLoaderMaxIterationsyes5The number of iterations without receiving batches from the managers nodes before in increasing the sleep timecom.accenture.aspire.node.worker.batchLoaderMultiplieryes2The multiplier used to increase the sleep time after the specified iterations without receiving batches from the managers nodescom.accenture.aspire.node.worker.connectionTimeoutyes20000The connection timeout for requests to other aspire nodescom.accenture.aspire.node.worker.socketTimeoutyes20000The socket timeout for requests to other aspire nodescom.accenture.aspire.node.worker.maxRetriesyes3The number of retries for requests to other aspire nodescom.accenture.aspire.node.worker.proxyHostnonullThe proxy host to use for requests to other aspire nodescom.accenture.aspire.node.worker.proxyPortno0The proxy port to use for requests to other aspire nodes. Must be provided if the proxyHost is configuredcom.accenture.aspire.node.worker.proxyUsernonullThe proxy user to use for requests to other aspire nodescom.accenture.aspire.node.worker.proxyPasswordnonullThe proxy password to use for requests to other aspire nodes.com.accenture.aspire.node.worker.pingFrequencyyes15000The ping timeout used to determine if a node is not working. The node will be marked as failed in this case and the node eventually will shutdown itselfcom.accenture.aspire.node.worker.nodeFailureTimeoutyes30000The frequency for the node to ping to Elastisearch. The pings are used to determine if a node is alive and working properly

Manager Node

These properties will be used by all manager nodes in the cluster.

Parameter	Required	Default	Description
com.accenture.aspire.node.manager.scanBatchCreatorBaseSleep	yes	200	The base sleep time in ms for the thread in charge of creating batches from the scan queuemonitoring active crawls
com.accenture.aspire.node.manager.scanBatchCreatorMaxSleepschedulerBaseSleep	yes	10000	The maximum base sleep time in ms for the thread in charge of creating batches from the scan queueexecuting seeds based on the configured schedules
com.accenture.aspire.node.manager.scanBatchCreatorMaxIterationsmaxBatches	yes	101000	The maximum number of iterations without creating new scan batches before in increasing the sleep timebatches the manager will keep in memory
com.accenture.aspire.node.manager.scanBatchCreatorMultipliermaxBatchItems	yes	2	The multiplier used to increase the sleep time after the specified iterations without creating new scan batches	100	The maximum number of documents per batch
com.accenture.aspire.node.manager.processBatchCreatorBaseSleepconnectionTimeout	yes	20020000	The base sleep time in ms for the thread in charge of creating batches from the process queueconnection timeout for requests to other aspire nodes
com.accenture.aspire.node.manager.processBatchCreatorMaxSleepsocketTimeout	yes	1000020000	The maximum sleep in ms for the thread in charge of creating batches from the process queuesocket timeout for requests to other aspire nodes
com.accenture.aspire.node.manager.processBatchCreatorMaxIterationsmaxRetries	yes	103	The number of iterations without creating new process batches before in increasing the sleep timeretries for requests to other aspire nodes
aspire.node.manager.proxyHost	no	null	The proxy host to use for requests to other aspire nodes
com.accenture.aspire.node.manager.processBatchCreatorMultiplierproxyPort	yesno	20	The multiplier used to increase the sleep time after the specified iterations without creating new process batches proxy port to use for requests to other aspire nodes. Must be provided if the proxyHost is configured
com.accenture.aspire.node.manager.crawlProgressManagerBaseSleepproxyUser	yes	200	The base sleep time in ms for the thread in charge of monitoring active crawls	no	null	The proxy user to use for requests to other aspire nodes
com.accenture.aspire.node.manager.schedulerBaseSleepproxyPassword	yesno	10000null	The base sleep time in ms for the thread in charge of executing seeds based on the configured schedulesproxy password to use for requests to other aspire nodes.
com.accenture.aspire.node.manager.maxBatchespingFrequency	yes	100015000	The maximum number of batches the manager will keep in memory
com.accenture.aspire.node.manager.maxBatchItems	yes	100	The maximum number of documents per batch
frequency for the node to ping to Elasticsearch. The pings are used to determine if a node is alive and working properly
com.accenture.aspire.node.manager.connectionTimeoutnodeFailureTimeout	yes	2000030000	The connection ping timeout for requests to other aspire nodes
com.accenture.aspire.node.manager.socketTimeout	yes	20000	The socket timeout for requests to other aspire nodes
used to determine if a node is not working. The node will be marked as failed in this case and the node eventually will shutdown itself
com.accenture.aspire.node.manager.maxRetriesinProgressJobTimeout	yes	3	3600000	The maximum time in ms, a job can be in "in-progress" status before being released. Default is 1 hour
The number of retries for requests to other aspire nodes	com.accenture.aspire.node.manager.proxyHostinProgressJobTimeoutCheckFrequency	noyes	null	1800000	How frequently to verify for timed-out "in-progress" jobs
The proxy host to use for requests to other aspire nodes	com.accenture.aspire.node.manager.proxyPortackCleanBaseSleep	no	0	5000	How frequently the manager should check for Acknowledged Batches that need to be removed from memory.
The proxy port to use for requests to other aspire nodes. Must be provided if the proxyHost is configured	com.accenture.aspire.node.manager.proxyUserproxyCall	no	null	The proxy user to use for requests to other aspire nodes	false	Configure if you want to perform a proxy call to the main manager from a non-main manager and avoid redirect calls.
com.accenture.aspire.node.manager.proxyPasswordtags	no	null		The tags of the manager node. These tags will determine which seeds this node can process. It should be a comma separated list of tags.
The proxy password to use for requests to other aspire nodes.	com.accenture.aspire.node.manager.pingFrequencyworkerRoundRobin	yesno	false	If round-robin should be applied when serving workers with batches
15000	The ping timeout used to determine if a node is not working. The node will be marked as failed in this case and the node eventually will shutdown itself	com.accenture.aspire.node.manager.nodeFailureTimeoutworkerRoundRobinTimeout	yesno	30000600000	The frequency for the node to ping to Elastisearch. The pings are used to determine if a node is alive and working properly
com.accenture.aspire.node.manager.inProgressJobTimeout	yes	3600000	The maximum time in ms a job can be in "in-progress" status before being released. Default is 1 hour
time in ms after which the worker is considered timed out when round-robin is used.

User Interface

Since 5.0.3, the following properties are also available for managing the behavior of the user interface.

Parameter	Required	Default	Description
aspire.ui.refreshRate	no	5s	How often trigger the auto-refresh for the listing pages. It can be defined with a time unit, i.e. 15s, 1 m.	com.accenture.aspire.node.manager.inProgressJobTimeoutCheckFrequency	yes	1800000	How frequently to verify for timed-out "in-progress" jobs

Dashboards

These properties will be used to generate the dashboard links in the UI

Parameter	Required	Default	Description
aspire.dashboards.enabled	no	false	Enables the dashboard links on the UI
aspire.dashboards.base	no		Base URL to Kibana
aspire.dashboards.main	no		Main Dasboard Dashboard relative URL
aspire.dashboards.metrics	no		Metrics Dashboard relative URL

Page tree

Versions Compared

Old Version 15

New Version Current

Key

Format

Elasticsearch NoSQL Provider

Memory settings

Elasticsearch NoSQL Provider

SSL Certificates

Security and encryption

Index Sharding and Replicas settings

SSL Certificates

Security and encryption

Encryption

Standard AES 256 Encryption with local key

AWS KMS Encryption

Worker Node

Manager Node

Worker Node

Manager Node

User Interface

Dashboards