[
http://jira.amdatu.org/jira/browse/AMDATUCASSANDRA-103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivo Ladage - van Doorn resolved AMDATUCASSANDRA-103.
----------------------------------------------------
Assignee: Ivo Ladage - van Doorn
Resolution: Won't Fix
The problem is in the DatabaseDescriptor class of Cassandra. In this class a
static code snippet is executed in which the Cassandra configuration is read
from the cassandra.yaml. If some configuration properties are incorrect, it
catches the exception and does a System.exit().
So to resolve it we should either patch Cassandra (modify this class) or
perform a validation of the resulting cassandra.yaml before we pass it to
Cassandra. In the latter case we should copy/paste large portions of this
class, of which we know it is is highly subjective to change. So in both cases
we will introduce a lot of work, migration issues and possible new errors.
Furthermore, in most cases (even when you leave the seeds config empty for
example) the generated cassandra.yaml is valid, since we take the default
cassandra.yaml and only apply changes from the amdatu specific config (it took
me some time to find the reproduction path with setting the IP address to
0.0.0.0).
Note that we can still implement the extra validation for individual errors
that are likely to occur (as opposed to setting the IP address to 0.0.0.0). For
these cases, a separate JIRA issue should be created.
> Faulty cassandra configuration shuts down JVM
> ----------------------------------------------
>
> Key: AMDATUCASSANDRA-103
> URL: http://jira.amdatu.org/jira/browse/AMDATUCASSANDRA-103
> Project: Amdatu Cassandra
> Issue Type: Bug
> Components: Cassandra daemon
> Reporter: Bram de Kruijff
> Assignee: Ivo Ladage - van Doorn
> Fix For: 0.2.2
>
>
> When faulty configuration is supplied to the cassandra application (eg.
> missing property or occupied port) the JVM, thus the entire cassandra agent,
> is shut down
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
http://jira.amdatu.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
Amdatu-developers mailing list
[email protected]
http://lists.amdatu.org/mailman/listinfo/amdatu-developers