[ 
https://issues.apache.org/jira/browse/CASSANDRA-6572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14004097#comment-14004097
 ] 

Lyuben Todorov edited comment on CASSANDRA-6572 at 5/20/14 10:58 PM:
---------------------------------------------------------------------

bq. put any finished flushing QQs onto this CLQ when done so that we quickly 
reach an equilibrium point. 

Why do we want to store completed QQs onto the CLQ used for storing failed 
pre-flush CAS? Also what would be the best time to poll the CQL of failed flush 
QQs? I'd say on CAS success of the current queue submit multiple flushes in 
separate threads until the CLQ of failed QQs is emptied out.

Other than that commit with everything else in the comment on 
[c38080f|https://github.com/lyubent/cassandra/commit/c38080fd5e852901db903f59fff450e99f93d358].


was (Author: lyubent):
bq. put any finished flushing QQs onto this CLQ when done so that we quickly 
reach an equilibrium point. 

Why do we want to store completed QQs onto the CLQ used for storing failed 
pre-flush CAS? Also what would be the best time to poll the CQL of failed flush 
QQs? I'd say on CAS success of the current queue submit multiple flushes in 
separate threads until the CLQ of failed QQs is emptied out.

Other than that commit with everything else in the comment on 
[54e579b|https://github.com/lyubent/cassandra/commit/c38080fd5e852901db903f59fff450e99f93d358].

> 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)

Reply via email to