The ownership of the Hadoop mapred staging directory in the CassandraFS has changed. After upgrading, you need to set the owner of /tmp/hadoop-<dseuser>/mapred/staging to the dse user. For example, if you run DataStax Enterprise 3.1 as root, use the following command on Linux:
dse hadoop fs -chown root /tmp/hadoop-root/mapred/staging
Do not issue Solr queries after upgrading from DataStax Enterprise 2.1.x or earlier until all nodes are upgraded and schema disagreements are resolved.
Solr configuration files from previous versions of Datastax Enterprise will be invalidated by the new version of Solr included in this release. Follow these steps to update your Solr config file on the first solr node you upgrade, before upgrading any other nodes:
Open the system.log and look for the message about the Solr error.
The error message briefly describes the changes you need to make.
Correct these errors in your solrconfig.xml files, then post the corrected files.
Existing cores cannot be loaded until the solrconfig.xml errors are resolved.
You will also need to issue the following command to recover indexes on each solr node upgraded. On the first node upgraded, this process should happen after the Solr configuration file has been uploaded. Note that in the command below you will need to substitute the name of your solr core.
curl -v "http://localhost:8983/solr/admin/cores?action=CREATE&<solr core>.solr&recovery=true"
The following is an example of how to perform these steps using our Solr-based demos. If you wish to do this on a test cluster, first run the solr, wiki and logging demos on a test cluster running the older version of DSE.
Go to the directory containing your Solr application. For example, go to the demos directory:
Run the following commands to HTTP-POST your modified custom solrconfig.xml to DSE-Search. For example, from the demos or dse-demos directory, run the following commands:
From the solr_stress directory:
curl -v --data-binary @solrconfig.xml -H 'Content-type:text/xml; charset=utf-8' http://localhost:8983/solr/resource/demo.solr/solrconfig.xml
From the wikipedia directory:
curl -v --data-binary @solrconfig.xml -H 'Content-type:text/xml; charset=utf-8' http://localhost:8983/solr/resource/wiki.solr/solrconfig.xml
From the log_search directory:
curl -v --data-binary @solrconfig.xml -H 'Content-type:text/xml; charset=utf-8' http://localhost:8983/solr/resource/Logging.log_entries/solrconfig.xml
After running each curl command, a SUCCESS message appears.
This step is only required once, when the first node is upgraded.
After each node is upgraded, run the CREATE command with the the recovery option set to true, and the distributed option set to false:
curl -v "http://localhost:8983/solr/admin/cores?action=CREATE&name=demo.solr&recovery=true" curl -v "http://localhost:8983/solr/admin/cores?action=CREATE&name=wiki.solr&recovery=true" curl -v "http://localhost:8983/solr/admin/cores?action=CREATE&name=Logging.log_entries&recovery=true"
If you wish to use security you must upgrade the entire cluster before setting up security and then do another rolling restart.