Thrift to CQL migration under new Keyspace or Cluster

Hi guys, We are running one of our Cassandra cluster under 2.0.17 Thrift version and we started the 2.0.17 CQL migration plan through CQLSSTableWriter/sstableloader method. Simple question, maybe someone worked in similar scenario, is there any problem to do the migration under the same Cassandra

cassandra getendpoints do not match with tracing

Hi all, Recently we added some nodes to our cluster. After adding nodes we noticed that when we nodetool getendpoints tims "MESSAGE_HISTORY" partitionkey1 it reports three nodes per dc with 6 nodes in total which is expected since RF is 3. But when we run a query with local_one and tracing on ,