|
wojciech.kapcia@tigase.net opened 2 years ago
|
|||||||||
|
|
Changes from comit:8319c936482363b242bf766d451da91e984d8669 should probably address the issue... |
|||||||||
|
|
wojciech.kapcia@tigase.net batch edited 6 months ago
|
|||||||||
|
|
wojciech.kapcia@tigase.net batch edited 6 months ago
|
| Type |
New Feature
|
| Priority |
If you are bored
|
| Assignee | |
| Version |
tigase-server-8.5.0
|
Iterations
-
tigase-server-8.5.0 Open
Related
-
tigase-private/systems-maintenance/servers#398 You are not authorized to access this issue
-
tigase-private/systems-maintenance/servers#384 You are not authorized to access this issue
Issue Votes (0)
Watchers (2)
To avoid any collisions (or locks) and lower impact on the repository, in cluster deployments, only single node
CertificateRepositoryshould be responsible for writing certificate to the repository.