cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nick Bailey (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-1449) consistent nodetool blocking behavior
Date Mon, 20 Sep 2010 22:59:33 GMT

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

Nick Bailey commented on CASSANDRA-1449:
----------------------------------------

This patch also doesn't cover removeToken.  The current implementation only blocks until the
current node has replicated any data it needs. I can add blocking behavior in CASSANDRA-1216
although I had planned on making it non-blocking.  If it is blocking there is a chance something
fails and it blocks forever.

> consistent nodetool blocking behavior
> -------------------------------------
>
>                 Key: CASSANDRA-1449
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1449
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Tools
>            Reporter: Brandon Williams
>            Assignee: Nirmal Ranganathan
>            Priority: Minor
>             Fix For: 0.7.0
>
>         Attachments: 0001-Updated-all-non-blocking-Nodetool-commands-to-blocki.patch
>
>
> Some operations in nodetool block.  Some don't.  We should choose a behavior and enforce
it, preferably blocking.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message