You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Dan Di Spaltro (JIRA)" <ji...@apache.org> on 2009/12/02 04:34:20 UTC

[jira] Created: (CASSANDRA-592) better nodeprobe loadbalance feedback

better nodeprobe loadbalance feedback
-------------------------------------

                 Key: CASSANDRA-592
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-592
             Project: Cassandra
          Issue Type: Bug
         Environment: trunk (r886010)
            Reporter: Dan Di Spaltro


It would be great if we could some how track progress on the nodeprobe loadbalance command.

One suggestion is that it leaves the visual ring until its ready to go.  As a user it seems like black magic right now...

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


[jira] Resolved: (CASSANDRA-592) better nodeprobe loadbalance feedback

Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CASSANDRA-592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Ellis resolved CASSANDRA-592.
--------------------------------------

    Resolution: Duplicate

this is a subset of CASSANDRA-709

> better nodeprobe loadbalance feedback
> -------------------------------------
>
>                 Key: CASSANDRA-592
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-592
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>         Environment: trunk (r886010)
>            Reporter: Dan Di Spaltro
>            Priority: Minor
>             Fix For: 0.6
>
>
> It would be great if we could some how track progress on the nodeprobe loadbalance command.
> One suggestion is that it leaves the visual ring until its ready to go.  As a user it seems like black magic right now...

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


[jira] Updated: (CASSANDRA-592) better nodeprobe loadbalance feedback

Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CASSANDRA-592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Ellis updated CASSANDRA-592:
-------------------------------------

      Component/s: Core
    Fix Version/s: 0.5
         Priority: Minor  (was: Major)
       Issue Type: Improvement  (was: Bug)

> better nodeprobe loadbalance feedback
> -------------------------------------
>
>                 Key: CASSANDRA-592
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-592
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>         Environment: trunk (r886010)
>            Reporter: Dan Di Spaltro
>            Priority: Minor
>             Fix For: 0.5
>
>
> It would be great if we could some how track progress on the nodeprobe loadbalance command.
> One suggestion is that it leaves the visual ring until its ready to go.  As a user it seems like black magic right now...

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


[jira] Commented: (CASSANDRA-592) better nodeprobe loadbalance feedback

Posted by "Hudson (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CASSANDRA-592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12788071#action_12788071 ] 

Hudson commented on CASSANDRA-592:
----------------------------------

Integrated in Cassandra #282 (See [http://hudson.zones.apache.org/hudson/job/Cassandra/282/])
    

> better nodeprobe loadbalance feedback
> -------------------------------------
>
>                 Key: CASSANDRA-592
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-592
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>         Environment: trunk (r886010)
>            Reporter: Dan Di Spaltro
>            Priority: Minor
>             Fix For: 0.9
>
>
> It would be great if we could some how track progress on the nodeprobe loadbalance command.
> One suggestion is that it leaves the visual ring until its ready to go.  As a user it seems like black magic right now...

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


[jira] Updated: (CASSANDRA-592) better nodeprobe loadbalance feedback

Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CASSANDRA-592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Ellis updated CASSANDRA-592:
-------------------------------------

    Fix Version/s:     (was: 0.5)
                   0.9

Added a couple log messages in r888022, but really what we want is some kind of "state" to show up in nodeprobe ring showing what the nodes are doing, which is outside of what I see as 0.5 scope unless someone contributes it Real Soon.

Note that a leaving node will stay in its original position on the ring until it has moved all its data to other nodes, which usually takes a relatively long time; then it will leave the ring and rejoin in the new position (after requesting and pulling the new data for that position).

> better nodeprobe loadbalance feedback
> -------------------------------------
>
>                 Key: CASSANDRA-592
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-592
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>         Environment: trunk (r886010)
>            Reporter: Dan Di Spaltro
>            Priority: Minor
>             Fix For: 0.9
>
>
> It would be great if we could some how track progress on the nodeprobe loadbalance command.
> One suggestion is that it leaves the visual ring until its ready to go.  As a user it seems like black magic right now...

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