This documentation is for WSO2 Private PaaS 4.0.0. View documentation for the latest release.
Clustering - WSO2 Private PaaS 4.0.0 - WSO2 Documentation
                                                                                                                                                                                                                                                                                                                                                                                                           
||
Skip to end of metadata
Go to start of metadata

Well Known Address (WKA) membership scheme is used for clustering in WSO2 Private PaaS. Apache Stratos Auto-scaler will maintain a given number of well known members. While, Apache Stratos Cartridge Agent will ensure that all the well known member configurations are configured in each cartridge instance. In addition, Cartridge Agent will handle the different clustering configuration steps for each WSO2 product via the extension handlers and extension shell scripts.

  • The number of well known members N(wk) will be always equal to the minimum member count in a partition (partitionMin).

  • The Auto-scaler will ensure to maintain the exact number of well known members when scaling up or down.

  • To enable clustering for a cartridge, the following property must be set in the cartridge definition JSON file.
    PRIMARY: true
    “payload_parameter.CLUSTERING: true”

  • Auto-scaler will decide which cartridge instances are primary (or well known) members and which ones are workers.

    • The primary instance will have the following parameter in the payload:
      “PRIMARY=true” 

    • The worker instances will have the following parameter in the payload:
      “PRIMARY=false”  

    • If clustering is enabled as mentioned above, all instances will have the following parameter in the payload:
      “CLUSTERING=true” 

Clustered Deployment

WSO2 API Manager uses the following four main components:

  • Gateway
    Responsible for securing, protecting, managing, and scaling API calls.
  • Store
    Enables consumers to self-register, discover API functionality, subscribe to APIs, evaluate them, and interact with API publishers.
  • Publisher
    Enables API providers to easily publish their APIs, share documentation, provision API keys, and gather feedback on API features, quality, and usage.
  • Key Manager
    Responsible for all security and key-related operations.

All the products share the userstore and governance database. In API Manager the apim_db database is shared by the gateway, store, publisher and key manager. Separate databases are used to maintain API Manager configurations. These databases are as follows: gateway_config database for gateway configuration, store_pub_config database for store and publisher configurations and keymanager_config database for keymanager configurations. 

In WSO2 Private PaaS separate clusters can be maintained for each service (e.g., esb cluster, appserver cluster, api manager cluster, bps cluster and is cluster); while, worker manager separation can be maintained between them.

  • No labels