cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CASSANDRA-7504) Log the disruptor server at ERROR like we do in 2.1
Date Tue, 25 Aug 2015 04:16:45 GMT

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

Jonathan Ellis resolved CASSANDRA-7504.
---------------------------------------
       Resolution: Won't Fix
    Fix Version/s:     (was: 2.0.x)

Closing out 2.0, apparently not a problem in 2.1.

> 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
>
> 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.3.4#6332)

Mime
View raw message