Eric Hubert commented on CASSANDRA-13396:

[~jasobrown], fair enough. From what I read/understood the majority of users 
(if not all, definitely including us) facing this issue, wanted to use 
Cassandra as an embedded server (mostly for integration testing purposes) 
utilizing class org.apache.cassandra.service.CassandraDaemon - so no production 
deployment of a standalone server or cluster.

While running alongside an application using slf4j with any slf4j supported 
backend != logback your are in trouble and no longer able to start the 
cassandra server, although logging/logging performance are none of your 
(primary) goals/concerns.

I doubt there are many users who want to configure a standalone single or 
multi-node Cassandra installation using a different logging backend to use this 
in production and have your support, but many users want to write automated 
integration/scenario tests of their own application interacting with Cassandra 
using an embedded Cassandra server in addition to plain unit tests using mocks 
without being forced to switch the logging backend chosen for their application 
for similar reasons you have. Therefore I see no conflict at all.

An implementation could even somehow enforce the differentation between 
embedded and standalone similar to "runManaged" to only allow/support other 
logging backends (skip special logging backend specific configuration) if 
CassandraDeamon is used/configured differently than from main() as done by a 
standalone server installation, this this is really a concern you want to see 

> Cassandra 3.10: ClassCastException in ThreadAwareSecurityManager
> ----------------------------------------------------------------
>                 Key: CASSANDRA-13396
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-13396
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Edward Capriolo
>            Assignee: Eugene Fedotov
>            Priority: Minor
> https://www.mail-archive.com/user@cassandra.apache.org/msg51603.html

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

Reply via email to