You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Cody A. Ray (JIRA)" <ji...@apache.org> on 2012/08/23 02:59:41 UTC
[jira] [Created] (CASSANDRA-4569) Cassandra configuration should
support a TokenProvider (like SeedProvider)
Cody A. Ray created CASSANDRA-4569:
--------------------------------------
Summary: Cassandra configuration should support a TokenProvider (like SeedProvider)
Key: CASSANDRA-4569
URL: https://issues.apache.org/jira/browse/CASSANDRA-4569
Project: Cassandra
Issue Type: New Feature
Components: Core
Reporter: Cody A. Ray
Priority: Minor
For added flexibility (and to allow more external management options without simply rewriting the configuration file), it would be great if Cassandra supported a TokenProvider interface like it does with the SeedProvider.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-4569) Cassandra configuration should
support a TokenProvider (like SeedProvider)
Posted by "Cody A. Ray (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-4569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13440058#comment-13440058 ]
Cody A. Ray commented on CASSANDRA-4569:
----------------------------------------
Nope. I'm looking for the initial_token value to be pluggable so that I can manage/generate the initial tokens using an external service. Right now, I either have to rewrite the cassandra.yaml with the correct initial_token value, or have to set the system property cassandra.initial_token. Ideally, it'd be more directly pluggable using a TokenProvider interface though, like the SeedProvider is.
> Cassandra configuration should support a TokenProvider (like SeedProvider)
> --------------------------------------------------------------------------
>
> Key: CASSANDRA-4569
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4569
> Project: Cassandra
> Issue Type: New Feature
> Components: Core
> Reporter: Cody A. Ray
> Priority: Minor
>
> For added flexibility (and to allow more external management options without simply rewriting the configuration file), it would be great if Cassandra supported a TokenProvider interface like it does with the SeedProvider.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Comment Edited] (CASSANDRA-4569) Cassandra configuration
should support a TokenProvider (like SeedProvider)
Posted by "Cody A. Ray (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-4569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13440058#comment-13440058 ]
Cody A. Ray edited comment on CASSANDRA-4569 at 8/23/12 4:09 PM:
-----------------------------------------------------------------
Nope. I'm looking for the initial_token value to be pluggable so that I can manage/generate the initial tokens using an external service. Right now, I either have to rewrite the cassandra.yaml with the correct initial_token value, or have to set the system property cassandra.initial_token. Ideally, it'd be more directly pluggable using a TokenProvider interface though, like the SeedProvider is.
To give more context, I'd like this so that the entire configuration file can be identical across nodes in the cluster, and managed using puppet. This is the last bit of machine specific info present in the config (I think).
was (Author: codyaray):
Nope. I'm looking for the initial_token value to be pluggable so that I can manage/generate the initial tokens using an external service. Right now, I either have to rewrite the cassandra.yaml with the correct initial_token value, or have to set the system property cassandra.initial_token. Ideally, it'd be more directly pluggable using a TokenProvider interface though, like the SeedProvider is.
> Cassandra configuration should support a TokenProvider (like SeedProvider)
> --------------------------------------------------------------------------
>
> Key: CASSANDRA-4569
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4569
> Project: Cassandra
> Issue Type: New Feature
> Components: Core
> Reporter: Cody A. Ray
> Priority: Minor
>
> For added flexibility (and to allow more external management options without simply rewriting the configuration file), it would be great if Cassandra supported a TokenProvider interface like it does with the SeedProvider.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CASSANDRA-4569) Cassandra configuration should
support a TokenProvider (like SeedProvider)
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-4569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis resolved CASSANDRA-4569.
---------------------------------------
Resolution: Not A Problem
The partitioner is already pluggable; it sounds like that is what you are looking for.
> Cassandra configuration should support a TokenProvider (like SeedProvider)
> --------------------------------------------------------------------------
>
> Key: CASSANDRA-4569
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4569
> Project: Cassandra
> Issue Type: New Feature
> Components: Core
> Reporter: Cody A. Ray
> Priority: Minor
>
> For added flexibility (and to allow more external management options without simply rewriting the configuration file), it would be great if Cassandra supported a TokenProvider interface like it does with the SeedProvider.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-4569) Cassandra configuration should
support a TokenProvider (like SeedProvider)
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-4569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13440077#comment-13440077 ]
Jonathan Ellis commented on CASSANDRA-4569:
-------------------------------------------
I see. This is basically obsolete in 1.2 because of virtual nodes (CASSANDRA-4119); each node will generate N random tokens. Specifying initial_token manually or programatically no longer makes sense.
> Cassandra configuration should support a TokenProvider (like SeedProvider)
> --------------------------------------------------------------------------
>
> Key: CASSANDRA-4569
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4569
> Project: Cassandra
> Issue Type: New Feature
> Components: Core
> Reporter: Cody A. Ray
> Priority: Minor
>
> For added flexibility (and to allow more external management options without simply rewriting the configuration file), it would be great if Cassandra supported a TokenProvider interface like it does with the SeedProvider.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira