DataStax Enterprise 2.1 Documentation

Troubleshooting Tips

This section lists some common problems experienced with DataStax Enterprise and solutions or workarounds.

Mahout Jobs that Use Lucene Not Supported

DataStax does not currently support Mahout jobs, such as built-in support for creating vectors from Lucene indexes, that use Lucene features. Attempting to run Mahout jobs that use Lucene features results in this type of error message:

Error: class org.apache.mahout.vectorizer.
DefaultAnalyzer overrides final method
tokenStream.

MX4J Warning Message During Installation

When Cassandra loads, you may notice a message that MX4J will not load and that mx4j-tools.jar is not in the classpath.

You can ignore this message. MX4j provides an HTML and HTTP interface to JMX and is not necessary to run Cassandra. DataStax recommends using OpsCenter. It has more monitoring capabilities than MX4J.

Confusing Solr Error Messages

  • When uploading the schema.xml, Solr issues an error message if the solrconfig.xml doesn't exist in the Solr core. You can ignore this message.

For example:

WARNING: "java.lang.RuntimeException: org.apache.solr.common.SolrException:
Could not find: schema.xml"
Posted solrconfig.xml to http://localhost:8983/solr/resource/
demo.solr/solrconfig.xml
SUCCESS
Posted schema.xml to http://localhost:8983/solr/resource/
demo.solr/schema.xml
  • When uploading the solrconfig.xml, Solr issues an error message if the schema.xml hasn't been uploaded. You can ignore this message. After uploading the schema and the configuration file, you should see a SUCCESS message.
  • If you upload a malformed xml files, Solr issues an error message. Do not ignore these messages. Fix the xml.