With DSE 2.0, after a failure in creating a solr core (due to errors in corename, solfconfig, or schema), additional requests to create new solr cores (even with different column family names) keep on failing. It seems like DSE could not recover from previous failure. Does anyone know how to handle this kind of issue? Thanks!
In an effort to consolidate free help offered for our products we have decided to move these forums to a more widely used forum. Please use one of the following queries (or any combination):
- Cassandra: tag search or plain text search
- DataStax Enterprise: tag search or plain text search
- DataStax OpsCenter: tag search or plain text search
DSE 2.0: Unable to create new solr cores after a failure(7 posts) (4 voices)
Does restarting the node help?
Restarting did not help on my local machine. DSE recovered only after I deleted all solr data. I am trying to replicate the issue in another environment. Are there are closed/open issues for this problem for DSE 2.0? Thanks!
There is DSE 2.2 released recently. The issue you have many not be resolved in the latest release. but the new release has many other fix.
So check it out.
Looks like the issue is related to Cassandra's schema disagreement error. Has this issue been resolved in DSE2.2? Thanks.
With the use of Cassandra 1.1.x as part of DSE 2.2 the schema updates are much less of an issue in general. Once DSE switches to using Cassandra 1.2 schema updates will no longer be an issue et al. To answer your next question (the one you would ask for sure) as to when that switch will happen. It is certainly planned, but we do not yet have a time line. Cassandra 1.2 is not official as of now, and there will be extra work to utilize the new capabilities of Cassandra 1.2 in DSE.
Thanks for the answers. We have to prevent such errors from happening at application level. A couple more questions:
1. Is it possible to configure DSE so that one node is assigned to handle all schema changes?
2. When posting solrconfig.xml and schema.xml, is it possible to pass parameter for Cassandra's write consistency?