...
| Gliffy | ||||||
|---|---|---|---|---|---|---|
|
| Gliffy | ||||||
|---|---|---|---|---|---|---|
|
| Gliffy | ||||||
|---|---|---|---|---|---|---|
|
Cluster Policy
Cluster policy defines that how should a cluster reacts and work in the case of new and active:
- Users
- Connections
- Storage
- Server Resources
Cluster policy can be defined in the PowerFolder.config and also in the Cluster.config that is present in the server_maintenance folder under cluster.
As a default the cluster policy is set to:
cluster.newconnects.policy=external
That means the server should adopt the cluster policy that is defined in the external web server e.g. Nginx or Apache.
| Info |
|---|
As an improvement we are introducing the default cluster policy in PowerFolder Server v15.1.100 as:
After this improvement the new server connection is always connected to the server in cluster that contains the fewest folders and hence the resources can be managed automatically. |
As an example of cluster.newconnects.policy=fewest_folders please consider the following diagram:
The PowerFolder Server 1 has the fewest folders so that all the new connections are automatically directed to it and the new user and their data can be successfully registered on the server that has the minimum resources in the cluster setup.
Adopting the new Cluster Policy
To adopt the new cluster policy:
- Upgrade your server to v15.1.100
- Delete the configuration entry:
cluster.newconnects.policy=externalfrom PowerFolder.config and Cluster.config - Restart all the nodes of your cluster
- Cross-check the cluster policy, it should be automatically taken as
cluster.newconnects.policy=fewest_folders
Conclusion
The actual setup you choose is depended on your requirements, budget and existing infrastructure.
...