You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2014/07/08 22:52:05 UTC

[jira] [Assigned] (CASSANDRA-7504) Log the disruptor server at ERROR like we do in 2.1

     [ https://issues.apache.org/jira/browse/CASSANDRA-7504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Ellis reassigned CASSANDRA-7504:
-----------------------------------------

    Assignee: Pavel Yaskevich

> Log the disruptor server at ERROR like we do in 2.1
> ---------------------------------------------------
>
>                 Key: CASSANDRA-7504
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7504
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Jeremy Hanna
>            Assignee: Pavel Yaskevich
>            Priority: Trivial
>             Fix For: 2.0.10
>
>
> Since we updated to use the disruptor hsha server in 2.0, we need to change the package that logs we specify at level ERROR.
> See CASSANDRA-6530 and particularly:
> https://github.com/apache/cassandra/blob/cassandra-2.0/conf/log4j-server.properties#L43
> versus
> https://github.com/apache/cassandra/blob/cassandra-2.1/conf/logback.xml#L52
> Also, do we want to log at FATAL?



--
This message was sent by Atlassian JIRA
(v6.2#6252)