Page Comparison

...

For each node, enter a unique ID for the id property under the wso2.carbon section. This is used to identify each node within a cluster. For example, you can add IDs as shown below.
- For node 1:
  Code Block
  language xml
  wso2.carbon: id: wso2-sp-1
- For node 2:
  Code Block
  language xml
  wso2.carbon: id: wso2-sp-2

Enable partitioning aggregations for each node, and assign a unique shard ID for each node. To do this, set the partitionById and shardId parameters as Siddhi properties as shown below.

Info
Assigning shard IDs to nodes allows the system to identify each unique node when assigning parts of the aggregation. If the shard IDs are not assigned, system uses the unique node IDs (defined in step 1) for this purpose.

For node 1:

Code Block

language	xml

siddhi:
  properties:
    partitionById: true
    shardId: wso2-sp-1

For node 2:

Code Block

language	xml

siddhi:
  properties:
    partitionById: true
    shardId: wso2-sp-2

Tip

To maintain data consistency, do not change the shard IDs after the first configuration
When you enable the aggregation partitioning feature, a new column ID named SHARD_ID is introduced to the aggregation tables. Therefore, you need to do one of the following options after enabling this feature to avoid errors occuring due to the differences in the table schema.
- Delete all the aggregation tables for SECONDS, MINUTES, HOURS, DAYS, MONTHS, YEARS.
- Edit the aggregation tables by adding a new column named SHARD_ID, and specify it as a add that to the existing primary key list of the table.

Configure a database, and then update the default configuration for the TEST_DB data source with parameter values suitable for your requirements

...

Versions Compared

Old Version 4

New Version Current

Key