cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paulo Motta (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-7276) Include keyspace and table names in logs where possible
Date Wed, 30 Sep 2015 23:39:05 GMT


Paulo Motta commented on CASSANDRA-7276:

[~eitikimura] some comments:
I'm not able to compile:
    [javac] /home/paulo/workspace/cassandra/src/java/org/apache/cassandra/utils/
error: package org.apache.log4j does not exist
    [javac] import org.apache.log4j.MDC;

There were also some warnings when applying the patch:
cassandra-2.1.9-7276.txt:54: trailing whitespace.
cassandra-2.1.9-7276.txt:141: trailing whitespace.
cassandra-2.1.9-7276.txt:219: trailing whitespace.
cassandra-2.1.9-7276.txt:222: trailing whitespace.
        for (ColumnFamily columnFamily : getColumnFamilies()) 
cassandra-2.1.9-7276.txt:228: trailing whitespace.
warning: squelched 17 whitespace errors
warning: 22 lines add whitespace errors.

Also, I just noticed there might be some inconsistencies with MDC and [managed threads|],
so it would be nice to verify that all mdc statements that you put will be run on the same
thread as the logging statements, as well as cleanup with MDC.clear or MDC.remove after the
operation is finished so we don't risk propagating garbage to other threads (you may find
more information about thread locality of MDC on this [post|]).

> Include keyspace and table names in logs where possible
> -------------------------------------------------------
>                 Key: CASSANDRA-7276
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Tyler Hobbs
>            Assignee: Nitzan Volman
>            Priority: Minor
>              Labels: bootcamp, lhf
>             Fix For: 2.1.x
>         Attachments: 2.1-CASSANDRA-7276-v1.txt, cassandra-2.1-7276-compaction.txt, cassandra-2.1-7276.txt,
> Most error messages and stacktraces give you no clue as to what keyspace or table was
causing the problem.  For example:
> {noformat}
> ERROR [MutationStage:61648] 2014-05-20 12:05:45,145 (line 198) Exception
in thread Thread[MutationStage:61648,5,main]
> java.lang.IllegalArgumentException
>     at java.nio.Buffer.limit(Unknown Source)
>     at org.apache.cassandra.db.marshal.AbstractCompositeType.getBytes(
>     at org.apache.cassandra.db.marshal.AbstractCompositeType.getWithShortLength(
>     at
>     at
>     at edu.stanford.ppl.concurrent.SnapTreeMap$1.compareTo(
>     at edu.stanford.ppl.concurrent.SnapTreeMap.attemptUpdate(
>     at edu.stanford.ppl.concurrent.SnapTreeMap.updateUnderRoot(
>     at edu.stanford.ppl.concurrent.SnapTreeMap.update(
>     at edu.stanford.ppl.concurrent.SnapTreeMap.putIfAbsent(
>     at org.apache.cassandra.db.AtomicSortedColumns$Holder.addColumn(
>     at org.apache.cassandra.db.AtomicSortedColumns.addAllWithSizeDelta(
>     at org.apache.cassandra.db.Memtable.resolve(
>     at org.apache.cassandra.db.Memtable.put(
>     at org.apache.cassandra.db.ColumnFamilyStore.apply(
>     at org.apache.cassandra.db.Keyspace.apply(
>     at org.apache.cassandra.db.Keyspace.apply(
>     at org.apache.cassandra.db.RowMutation.apply(
>     at org.apache.cassandra.db.RowMutationVerbHandler.doVerb(
>     at
>     at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
>     at java.util.concurrent.ThreadPoolExecutor$ Source)
>     at Source)
> {noformat}
> We should try to include info on the keyspace and column family in the error messages
or logs whenever possible.  This includes reads, writes, compactions, flushes, repairs, and
probably more.

This message was sent by Atlassian JIRA

View raw message