[
https://issues.apache.org/jira/browse/CASSANDRA-1123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13444338#comment-13444338
]
Jonathan Ellis commented on CASSANDRA-1123:
-------------------------------------------
Hmm, looks like this broke our test log4j config somehow. ant test gives a lot
of this:
{noformat}
[junit] ERROR 14:02:56,567 Fatal exception in thread
Thread[MigrationStage:1,5,main]
[junit] java.lang.NullPointerException
[junit] at
org.apache.cassandra.db.ColumnFamilyStore.getColumnFamily(ColumnFamilyStore.java:1195)
[junit] at
org.apache.cassandra.db.ColumnFamilyStore.getColumnFamily(ColumnFamilyStore.java:1087)
[junit] at
org.apache.cassandra.db.ColumnFamilyStore.getColumnFamily(ColumnFamilyStore.java:1077)
[junit] at
org.apache.cassandra.config.ColumnDefinition.readSchema(ColumnDefinition.java:247)
[junit] at
org.apache.cassandra.config.CFMetaData.fromSchema(CFMetaData.java:1320)
[junit] at
org.apache.cassandra.config.KSMetaData.deserializeColumnFamilies(KSMetaData.java:293)
[junit] at
org.apache.cassandra.db.DefsTable.mergeColumnFamilies(DefsTable.java:342)
[junit] at
org.apache.cassandra.db.DefsTable.mergeSchema(DefsTable.java:255)
[junit] at
org.apache.cassandra.service.MigrationManager$1.call(MigrationManager.java:202)
[junit] at
java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
[junit] at java.util.concurrent.FutureTask.run(FutureTask.java:138)
[junit] at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
[junit] at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
[junit] at java.lang.Thread.run(Thread.java:662)
{noformat}
where CFS:1195 is a logger.debug call.
ant test uses test/conf/log4j-server.properties, which just specifies a file
and stdout at DEBUG.
> Allow tracing query details
> ---------------------------
>
> Key: CASSANDRA-1123
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1123
> Project: Cassandra
> Issue Type: New Feature
> Components: Core
> Reporter: Jonathan Ellis
> Assignee: David Alves
> Fix For: 1.2.0 beta 1
>
> Attachments: 1123-3.patch.gz, 1123.patch, 1123.patch, 1123.patch,
> 1123.patch, 1123-v6.txt, 1123-v7.patch, 1123-v8.patch, 1123-v9.txt,
> 1123-v9.txt
>
>
> In the spirit of CASSANDRA-511, it would be useful to tracing on queries to
> see where latency is coming from: how long did row cache lookup take? key
> search in the index? merging the data from the sstables? etc.
> The main difference vs setting debug logging is that debug logging is too big
> of a hammer; by turning on the flood of logging for everyone, you actually
> distort the information you're looking for. This would be something you
> could set per-query (or more likely per connection).
> We don't need to be as sophisticated as the techniques discussed in the
> following papers but they are interesting reading:
> http://research.google.com/pubs/pub36356.html
> http://www.usenix.org/events/osdi04/tech/full_papers/barham/barham_html/
> http://www.usenix.org/event/nsdi07/tech/fonseca.html
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
