-
I've analyzed the issue and prepared a fix for it. It is in
server-1563branch. In this fix, I've speed up reload of the cluster nodes repository items, so they are now available faster. Then I've delayed notifications of connections managers, that they can open as cluster nodes are connected, until server startup is finished.With those changes, when all connections are ready and when server startup is completed, then connection managers will start listening in the cluster mode.
| Type |
Improvement
|
| Priority |
Normal
|
| Assignee | |
| Version |
8.5.0
|
| Sprints |
n/a
|
| Customer |
n/a
|
Iterations
-
tigase-server-8.5.0 Open
Issue Votes (0)
There is a ~15s delay between Tigase finishes starting up and actually starts listening on the ports. This mechanism was introduced to prevent data inconsistency when adding new node while not being correctly and fully connected to the cluster. However it looks like the logic detecting that state is not working correctly. On my local machine with single Tigase instance there is a long delay:
Wich cluster mode off (
'cluster-mode' = 'false') Listening is immediate (though there is no information that the prots stated already, IMHO we could/shoud add it as well):Detailed log