You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Pekka Enberg (JIRA)" <ji...@apache.org> on 2014/07/15 10:07:05 UTC

[jira] [Updated] (CASSANDRA-7547) EC2 seed provider using Datastax Reflector

     [ https://issues.apache.org/jira/browse/CASSANDRA-7547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pekka Enberg updated CASSANDRA-7547:
------------------------------------

    Attachment: 0001-EC2-seed-provider.patch

> EC2 seed provider using Datastax Reflector
> ------------------------------------------
>
>                 Key: CASSANDRA-7547
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7547
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Core
>            Reporter: Pekka Enberg
>            Priority: Minor
>         Attachments: 0001-EC2-seed-provider.patch
>
>
> This is a request for comments. I am using this to build our EC2 AMIs but I thought I'd ask if this makes sense as a generic feature for Cassandra.
> Cassandra cluster auto-configuration on EC2 uses the Datastax reflector service for discovering seed nodes. Instead of relying on external scripts, this patch implements EC2 seed provider that uses the Datastax reflector service.
> This is particularly useful for EC2 AMIs that don't include a complete userspace (such as those built with OSv) where we ideally want to push as much configuration to the application itself.



--
This message was sent by Atlassian JIRA
(v6.2#6252)