[ https://issues.apache.org/jira/browse/CASSANDRA-6572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13985239#comment-13985239 ]
Lyuben Todorov commented on CASSANDRA-6572: ------------------------------------------- Once a switch is made to a buffer of queries is kept in memory rather than opening and writing to a file for each query, I'm wondering if there should be some timing on the log so it gets flushed to disk after x amount of time. Arguments against is that when the queue is full or query recording is disabled the log gets flushed but if no querying is going on and Cassandra gets shut down the log will be lost. Simpler way of handling that is to handle that case in the shutdown process, but then during the time that the query log remains enabled it will be consuming memory. > Workload recording / playback > ----------------------------- > > Key: CASSANDRA-6572 > URL: https://issues.apache.org/jira/browse/CASSANDRA-6572 > Project: Cassandra > Issue Type: New Feature > Components: Core, Tools > Reporter: Jonathan Ellis > Assignee: Lyuben Todorov > Fix For: 2.1.1 > > Attachments: 6572-trunk.diff > > > "Write sample mode" gets us part way to testing new versions against a real > world workload, but we need an easy way to test the query side as well. -- This message was sent by Atlassian JIRA (v6.2#6252)