Description
This is an additional safety check that stems from observing a somewhat brittle behaviour of the cluster metadata in early C* 2.1 versions. While investigating the issue in #91, we noticed that the proxy does not validate that the addresses of all cluster nodes are correctly populated.
If the topology metadata in the system tables of a cluster is malformed or incomplete, the proxy builds its topology view regardless and then tries to use potentially invalid assigned hosts (e.g. hosts missing the address) when establishing connections to the cluster. This of course results in a failure which affects the application and becomes a blocker for a migration.
We should add reasonable checks to validate that the data of each assigned host is complete, so that we know that it can be used without issues. If we detect incomplete or invalid metadata (and no fallback or remediation is possible), we should prevent the proxy from starting and display a clear message in the logs. This may sound drastic, but ignoring some hosts or silently working around this in some other suboptimal way would be unreliable, hiding problems that may become apparent only when the migration gets underway.
┆Issue is synchronized with this Jira Task by Unito
┆Components: Proxy
┆Issue Number: ZDM-512