Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (nike.apache.org: domain of jbellis@gmail.com designates
 209.85.215.172 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CALgOR-KUjDO9mo-PfPWsjnnc5gZ=Y2fwiG40BM6-y3bvU=qOwQ@mail.gmail.com>
References: 
 <CALgOR-KUjDO9mo-PfPWsjnnc5gZ=Y2fwiG40BM6-y3bvU=qOwQ@mail.gmail.com>
From: Jonathan Ellis <jbellis@gmail.com>
Date: Tue, 15 Nov 2011 13:39:14 -0600
Message-ID: 
 <CALdd-zhMjRs9HYHZYhZjhExhrAv6bOaE5qxaWAD3syQ0GYT8RA@mail.gmail.com>
Subject: Re: Better way for logging ?
To: user@cassandra.apache.org
Content-Type: text/plain; charset=ISO-8859-1

Right, it only supports the properties file atm.

We're open to extending this to the xml configurator but is this
really a problem?  At INFO cassandra doesn't log much, and at DEBUG
you're going to suffer async or no. :)

On Tue, Nov 15, 2011 at 12:32 PM, Sachin Bhansali
<sachin.bhansali@gmail.com> wrote:
> Hi,
>
> Did anyone try to configure Async Logging in Cassandra 0.8.4 ? It seems only
> way to configure logging is through property file
> log4j-embedded-cassandra.properties which doesnt support Async logging.
>
> - Sachin
>


-- 
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of DataStax, the source for professional Cassandra support
http://www.datastax.com