Description of problem:
When running the server installer on a second server in an HA deployment, Cassandra schema changes are applied when they should not be. I had a single server running with a 4 node cluster which means a in replication_factor of 3 for the rhq and system_auth keyspaces. Here is the relevant log statements from the second server installer,

21:39:26,450 INFO  [org.rhq.cassandra.schema.TopologyManager] Applying topology updates...
21:39:26,450 INFO  [org.rhq.cassandra.schema.TopologyManager] Starting to execute UpdateReplicationFactor task.
21:39:26,462 INFO  [org.rhq.cassandra.schema.AbstractManager] Applying update file: org.rhq.cassandra.schema.UpdateFile@1b382d35
21:39:26,463 INFO  [org.rhq.cassandra.schema.AbstractManager] Statement:

    ALTER KEYSPACE rhq WITH replication = {'class': 'SimpleStrategy', 'replication_factor': 2}

21:39:27,602 INFO  [org.rhq.cassandra.schema.AbstractManager] Statement:

    ALTER KEYSPACE system_auth WITH replication = {'class': 'SimpleStrategy', 'replication_factor': 2}

21:39:28,823 INFO  [org.rhq.cassandra.schema.AbstractManager] Applied update file: org.rhq.cassandra.schema.UpdateFile@1b382d35
21:39:28,823 INFO  [org.rhq.cassandra.schema.TopologyManager] Updated replication factor from 3 to  2
21:39:28,824 INFO  [org.rhq.cassandra.schema.TopologyManager] Successfully executed UpdateReplicationFactor task.

No schema changes should be made. In particular, the replication_factor should not be changed as that gets updated when nodes are added/removed. Moreover, we only ever reduce the replication_factor when removing a node. 

The problem is that we unconditionally call SchemaManager.updateTopology(). The updateTopology method should only be invoked for a new install.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info: