cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pekka Enberg (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-7547) EC2 seed provider using DataStax Reflector
Date Wed, 16 Jul 2014 08:04:04 GMT


Pekka Enberg commented on CASSANDRA-7547:

Yes, I am aware of how it works. Primary motivation for using it is compatibility with DataStax
Community AMI. The reason I am interested in implemeting this as a Cassandra SeedProvider
is because I'm building the AMI using OSv ( which has no userspace to run boostrap
scripts during cloud-init. A custom SeedProvider seems like a nice fit and I thought it would
make sense as a generic feature in Cassandra as it is actually being used on EC2.

In any case, if you don't think this is appropriate in the tree, are you able to suggest a
way to do this in a way that makes sense for Cassandra? I could probably build this as a standalone
Jar and just add it to the Cassandra classpath, right? This only requires me to import SeedProvider
interface as source because there's no "Cassandra plugin" API Jar to build against, right?

> EC2 seed provider using DataStax Reflector
> ------------------------------------------
>                 Key: CASSANDRA-7547
>                 URL:
>             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

This message was sent by Atlassian JIRA

View raw message