geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "William Markito Oliveira (JIRA)" <>
Subject [jira] [Commented] (GEODE-182) Generate "random" member names if no name is provided
Date Fri, 31 Jul 2015 20:24:04 GMT


William Markito Oliveira commented on GEODE-182:

Thanks Darrel! 

Commands to restart/stop the members would require the name of the node as they do today.
 What this feature would be actually doing is just providing random names if none are provided
in order to make it easy to repeat the exact same startup command without controlling names
externally, which is the current unique solution.

I'd say that for cases where you have redundancy and don't have persistence, it should be
fine. But for persistent use cases you can (and should) still fall back to normal usage and
provide server names.

I'd really appreciate others perspective on this as well... 

> Generate "random" member names if no name is provided
> -----------------------------------------------------
>                 Key: GEODE-182
>                 URL:
>             Project: Geode
>          Issue Type: New Feature
>          Components: core
>            Reporter: William Markito Oliveira
>            Priority: Critical
> In current cloud and container deployments it's very common to allow the infrastructure
to just re-execute the same command in order to provision a new node for a system.
> Since Geode require unique member names on a system I'm proposing to create something
similar to what Docker and other projects does and generate "random" names on when none are
> Following the Docker implementation, I'd suggest something like:
> * List of adjectives
> * List of gems 
> and a combination using _ for example:
> {code}
> clever_alexandrite
> sharp_emerald
> tender_sapphire
> {code}
> Those would be server names when *-name* param is not specified OR if a *property file*
doesn't have a name as well. 
> From the initial list I'm thinking the model would have:
> * Adjectives = 56
> * Names = 70
> * Total names possible = 3920
> Other benefits I can see for non-cloud deployments as well is for example setting member
ports to 0 and by providing no name, it's also easier to create multiple geode nodes on the
same physical host without specifying names.
> This wouldn't change current naming features and capabilities.  I'm not planning to implement
the feature for locators initially.

This message was sent by Atlassian JIRA

View raw message