Currently after startup the node reads information about current nodes in the cluster and establish the connections and put own information in the database. Existing nodes, either periodically refresh information about nodes from the database and establish connection to newly read hostnames or do the refresh upon receiving incoming cluster connection.
However, sometimes it happens that node would read stale password from the database and the cluster connection handshaking fails.
One possibility for the improvement would be ability to set "static" password (for example via environment variables) which would allow opening return cluster connection to new node without the need to reload the database. Ideally cluster connections should only be allowed on the local network interface.
wojciech.kapcia@tigase.netbatch edited7 months ago
Currently after startup the node reads information about current nodes in the cluster and establish the connections and put own information in the database. Existing nodes, either periodically refresh information about nodes from the database and establish connection to newly read hostnames or do the refresh upon receiving incoming cluster connection.
However, sometimes it happens that node would read stale password from the database and the cluster connection handshaking fails.
One possibility for the improvement would be ability to set "static" password (for example via environment variables) which would allow opening return cluster connection to new node without the need to reload the database. Ideally cluster connections should only be allowed on the local network interface.