Upgrading from DataStax Enterprise 3.0 to 3.2
Upgrade from DataStax Enterprise 3.0.x to DataStax Enterprise 3.2.x.
Review this information and follow these instructions to upgrade from DataStax Enterprise 3.0.x to DataStax Enterprise 3.2.x.
dse.yaml
The location of the dse.yaml file depends on the type of installation:
Package installations |
/etc/dse/dse.yaml |
Tarball installations |
install_location/resources/dse/conf/dse.yaml |
cassandra.yaml
The location of the cassandra.yaml file depends on the type of installation:
Package installations |
/etc/cassandra/cassandra.yaml |
Tarball installations |
install_location/conf/cassandra.yaml |
Analytics nodes
While upgrading a cluster, some column families created through Hadoop interfaces might not appear to contain data. After the upgrade process has completed, the data is visible again.
Partitioner
Edit the cassandra.yaml file to change the partitioner setting to match the previous partitioner. The default RandomPartitioner (org.apache.cassandra.dht.RandomPartitioner) was the default partitioner prior to Apache Cassandra™ 1.2.
CQL 3
Do not issue any CQL 3 queries until all nodes are upgraded and schema disagreements are resolved.
Security recommendations
The client_encryption_options
for enabling client-to-node SSL have
been removed from dse.yaml
starting in 3.1.2. To enable client-to-node SSL, set the option in the
cassandra.yaml file.
dse_auth
keyspace greater than 1:- Kerberos
- Object permission management (internal authorization)
- Internal authentication
dse_auth
on each node in the
cluster. After updating the cassandra.yaml file and restarting
the node, run nodetool repair
to repair the first range returned by
the partitioner for the
keyspace:nodetool repair dse_auth -pr
This should only take a few seconds to complete.
- authenticator
- authorizer
- auth_replication_strategy
- auth_replication_options
- any other diffs
- authenticator: com.datastax.bdp.cassandra.auth.PasswordAuthenticator
- authorizer: org.apache.cassandra.auth.CassandraAuthorizer
INFO [NonPeriodicTasks:1 ] 2013-06-22 15:01:08,173
Auth.java (line 208 ) Migration of legacy auth data is complete.
You should now switch to org.apache.cassandra.auth implementations in cassandra.yaml.
After all nodes have been upgraded, change these options to the new Cassandra 1.2 values and perform a rolling restart as explained below.
- Edit the cassandra.yaml to switch to the official Apache
versions of
PasswordAuthenticator
andCassandraAuthorizer
:authenticator: org.apache.cassandra.auth.PasswordAuthenticator authorizer: org.apache.cassandra.auth.CassandraAuthorizer
- Remove or comment out these options from the cassandra.yaml
file:
- auth_replication_strategy
- auth_replication_options
- replication_factor
Note:If you have not disabled both
auth_replication_strategy
andreplication_factor
, you will see an error. For information about correcting this error, see Issues in the DataStax Enterprise 3.2.5 release notes. - Optionally, adjust the replication factor of the
system_auth
keyspace. The amount of data in this keyspace is typically very small, so leaving it replicated across the cluster is relatively cheap.
Virtual nodes (vnodes)
DataStax recommends using vnodes only on datacenters running Cassandra workloads. To disable vnodes on datacenters that run Hadoop or Solr workloads, set num_tokens to 1 in cassandra.yaml.
Solr
If you make changes to the configuration of a Solr node after upgrading, you must set the type mapping correctly as explained in Configuring the Solr type mapping version.Recommissioning a node
- Do not recommission the node until another 72 hours has passed.
- If you wish to recommission the node after 72 hours, run nodetool gossipinfo. Check the STATUS line for the token of the decommissioned node and verify that it does not exist. If it does not exist, then the node has been deleted and it is safe to recommission the node.
- If you need to bring the node into the cluster, contact Support on how to kill the node.