Currently, if one tries to start a node with incorrect SSL configuration (i.e. node with SSL disabled tries to connect to secured cluster or other way around), this new node does not show any exceptions or warnings. Instead user may end up having two topologies - one secured and another non-secured.
This is counterintuitive. We should try to detect this and throw an exception in this case.
Here are possible scenarios that we should consider:
- Unsecured server tries to join secured cluster.
- Secured server tries to join unsecured cluster.
- Unsecured client tries to join secured cluster.
- Secured client tries to join unsecured cluster.
IGNITE-16054 Skipped attempt to connect to other TcpDiscovery nodes if SSL is enabled and first node from list is down.
- links to