...
| Code Block | ||||
|---|---|---|---|---|
| ||||
<analytics-dataservice-configuration>
<!-- The name of the primary record store -->
<primaryRecordStore>EVENT_STORE</primaryRecordStore>
<!-- Analytics Record Store - properties related to record storage implementation -->
<analytics-record-store name="EVENT_STORE">
<implementation>org.wso2.carbon.analytics.datasource.rdbms.RDBMSAnalyticsRecordStore</implementation>
<properties>
<property name="datasource">WSO2_ANALYTICS_EVENT_STORE_DB</property>
<property name="category">large_dataset_optimized</property>
</properties>
</analytics-record-store>
<analytics-record-store name = "PROCESSED_DATA_STORE">
<implementation>org.wso2.carbon.analytics.datasource.rdbms.RDBMSAnalyticsRecordStore</implementation>
<properties>
<property name="datasource">WSO2_ANALYTICS_PROCESSED_DATA_STORE_DB</property>
<property name="category">large_dataset_optimized</property>
</properties>
</analytics-record-store>
<!-- The data indexing analyzer implementation -->
<analytics-lucene-analyzer>
<implementation>org.apache.lucene.analysis.standard.StandardAnalyzer</implementation>
</analytics-lucene-analyzer>
<!-- The number of index data replicas the system should keep, for H/A, this should be at least 1, e.g. the value 0 means
there aren't any copies of the data -->
<indexReplicationFactor>1</indexReplicationFactor>
<!-- The number of index shards, should be equal or higher to the number of indexing nodes that is going to be working,
ideal count being 'number of indexing nodes * [CPU cores used for indexing per node]' -->
<shardCount>6</shardCount>
<!-- The numberamount of batch index records,data the(in indexingbytes) nodeto willbe processprocessed perat eacha indexingtime thread.by Aa batchshard index recordworker. basicallyMinimum value encapsulates a batch of records retrieved from the receiver to be indexed is 1000. -->
<shardIndexRecordBatchSize>100<<shardIndexRecordBatchSize>20971520</shardIndexRecordBatchSize>
<!-- The interval in milliseconds, which a shard index processing worker thread will sleep during index processing operations. This setting
along with the 'shardIndexRecordBatchSize' setting can be used to increase the final index batched data amount the indexer processes
at a given time. Usually, higher the batch data amount, higher the throughput of the indexing operations, but will have a higher latency
of record insertion to indexing. Minimum value of this is 10, and a maximum value is 60000 (1 minute). -->
<shardIndexWorkerInterval>1500</shardIndexWorkerInterval>
<!-- Data purging related configuration -->
<analytics-data-purging>
<!-- Below entry will indicate purging is enable or not. If user wants to enable data purging for cluster then this property
need to be enable in all nodes -->
<purging-enable>false</purging-enable>
<cron-expression>0 0 0 * * ?</cron-expression>
<!-- Tables that need include to purging. Use regex expression to specify the table name that need include to purging.-->
<purge-include-tables>
<table>.*</table>
<!--<table>.*jmx.*</table>-->
</purge-include-tables>
<!-- All records that insert before the specified retention time will be eligible to purge -->
<data-retention-days>365</data-retention-days>
</analytics-data-purging>
</analytics-dataservice-configuration>
|
...
This option allows you to create servers that are dedicated for specific operations such as event receiving, analytics, indexing, etc.
Configuring common parameters
The following parameters are common for both the Analytics Record Store and the Analytics File SystemAll index data are stored in the file system, partitioned into unit is known as shards. For detailed information about shard configuration and allocation, see Storing Index Data.
Configuring common parameters
Data purging parameters
| Parameter | Description | Default Value |
|---|---|---|
<purging-enable> | This parameter specifies whether the functionality to purge data from event tables is enabled or not. | false |
<cron-expression> | A regex expression to select the tables from which data should be purged. | 0 0 0 * * ? |
<purge-include-tables> | A list of event tables from which data should be purged can be defined as subelements of this element. | |
<data-retention-days> | The number of days for which the data should be retained in the event tables that were selected to have their data purged. All the data in these tables are cleared once the number of days that equal the value specified for this parameter have elapsed. | 365 |
Other Parameters
| Parameter | Description | Default Value |
|---|---|---|
<analytics-lucene-analyzer> | The implementation of the Analytics Lucene Analyzer is defined as a subelement of this parameter. e.g., <implementation>org.apache.lucene.analysis.standard.StandardAnalyzer</implementation> | |
<indexReplicationFactor> | The index data replication factor to be used in clustered mode. This tells how many replicas that should be kept when indexing operations are done. 0 means, no replication. It should be set to 1 or higher to have high availability. | 1 | <shardCount> |
| Note |
|---|
This parameter can only be set once for the lifetime of the cluster, and cannot be changed later on. |
6<shardIndexRecordBatchSize>The number of batch index records the indexing node should process per each indexing thread at a given time.
An index record contains data of a record batch inserted in a single put operation. This batch can be as high as the event receiver queue data size, which is 10MB by default. Therefore, the highest amount of in-memory record data that an indexing processing thread can have is 10MB * 100. This parameter should be configured to change the maximum amount of memory available to the indexing node based on your requirement.
100<shardIndexWorkerInterval>
The interval in milliseconds during which a shard index processing worker thread will sleep during index processing operations. This parameter together with the shardIndexRecordBatchSize parameter can be used to increase the final index batched data amount processed by the indexer at a given time. Usually, a higher batch data amount results in a higher throughput of the indexing operations. However, it also causes an increased latency of record insertion to indexing. Minimum value of this is 10, and a maximum value is 60000 (1 minute).