StackSaga Cassandra-Agent Configuration Properties
Stacksaga MYSQL agent does support both eureka based and kubernetes based environments. There is a list of common configuration properties for both and as well as there are some configuration properties specific to eureka and kubernetes.
Common Configuration Properties
Property Name |
Default Value |
Type |
Description |
|---|---|---|---|
|
|
|
There are two profiles available as |
|
|
|
The name of the agent application. It is recommended to use this format: |
|
|
|
The port of the agent service. |
NOTE: Due to StackSaga Mysql-Agent internally uses spring default datasource and HikariCP for managing the connection pool, It can be configured the datasource properties in the same way that spring boot provides. |
|||
|
|
|
The keyspace(Database) name of the event-store. |
|
- |
|
The host name of the target service that retry tasks should be submitted to. |
|
- |
|
The name of the target service. (The transactions are fetched based on this name from the event-store) |
|
|
|
Whether the master service acts as the slave or not. If the cluster is small, you can run one instance and run as the master and as well as the slave. |
|
|
|
core number of threads in the IOPool. |
|
|
|
maximum number of threads in the IOPool. |
|
|
|
the time limit for which threads may remain idle before being terminated. |
|
|
|
the capacity of the queue. |
|
|
|
the maximum time the executor is supposed to block on shutdown. |
|
|
|
core number of threads in the IOPool. |
|
|
|
the time limit for which threads may remain idle before being terminated. |
|
|
|
the capacity of the queue. |
|
|
|
the maximum time the executor is supposed to block on shutdown. |
|
|
|
how long to wait before retrying the transaction at the beginning of the application. |
|
|
|
the fixed rate for retrying the transaction. As per the default value, the transaction retry process is repeated every 60 seconds. The executions are not overlapped even the old execution exceeds the interval |
|
|
|
The name of the target service. The number of transactions that should be fetched from the event-store for each batch. |
Eureka profile’s Configuration Properties
If you are in the Eureka environment, then you have to configure the following configuration properties.
Property Name |
Default Value |
Type |
Description |
|---|---|---|---|
|
- |
|
The type of this agent. Whether this agent is master or slave. in the cluster, it should have at least one master node. |
|
- |
|
if the instance is a master instance, the delay time to update the token range. (Master will send the token range to the slave agent in withing this delay time.) |
|
- |
|
if the instance is a master instance, the initial delay for updating the token range by the master. |
|
- |
|
How long time the token range should be valid. This valid time is sent to the slave instance, and its executions are based on this time. The default value is tokenRangeUpdateDelay + 2 minutes = 7 minutes. The extra 5 minutes are added to avoid the network delay. The tokenRangeValidDuration should be greater than tokenRangeUpdateDelay all the time. |
Kubernetes profile’s Configuration Properties
If you are in the kubernetes environment, then you have to configure the following configuration properties.
Property Name |
Default Value |
Type |
Description |
|---|---|---|---|
|
|
|
the topology name of the zone in the kubernetes cluster. |
|
|
|
the topology name of the region in the kubernetes cluster. |
|
|
|
the namespace that the application is deployed in the kubernetes cluster. |