In order to fix problems with SNI initialization we basically had to re-create the logic

in init() which... didn't make a whole lot of sense.  So this commit changes init() to
be usable in the refresh case.  Base use (with no args) will still behave as it did
but on a refresh we should get a complete rebuild of expected state now.

Author: absurdfarce

lib/control-connection.js

@@ -176,8 +176,8 @@ class ControlConnection extends events.EventEmitter {
    * Initializes the control connection by establishing a Connection using a suitable protocol
    * version to be used and retrieving cluster metadata.
    */
-  async init() {
-    if (this.initialized) {
+  async init(reinit) {
+    if (this.initialized && !reinit) {
       // Prevent multiple serial initializations
       return;
     }
@@ -429,20 +429,10 @@ class ControlConnection extends events.EventEmitter {
         this.log("info", `Current host IDs: ${this.options.contactPoints}`);
       }
 
-      if (!this.options.sni) {
-
-        /* NODEJS-632: do fresh DNS lookups on contact points since some hostnames may have
-         * shifted during the flight. */
-        this.log("info", "Refreshing contact points");
-        this._contactPoints.clear();
-        this._resolvedContactPoints.clear();
-
-        await Promise.all(this.options.contactPoints.map(name => this._parseContactPoint(name)));
-        const refreshedContactPoints = Array.from(this._contactPoints).join(',');
-        this.log('info', `Refreshed contact points: ${refreshedContactPoints}`);
-      }
-
-      await this._initializeConnection();
+      this.log("info", "Re-initializing the control connection");
+      this._contactPoints.clear();
+      this._resolvedContactPoints.clear();
+      await this.init(true)
     }
   }