accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Busbey (JIRA)" <j...@apache.org>
Subject [jira] [Created] (ACCUMULO-2844) Remove master/slave terminology
Date Mon, 26 May 2014 23:51:02 GMT
Sean Busbey created ACCUMULO-2844:
-------------------------------------

             Summary: Remove master/slave terminology
                 Key: ACCUMULO-2844
                 URL: https://issues.apache.org/jira/browse/ACCUMULO-2844
             Project: Accumulo
          Issue Type: Bug
    Affects Versions: 1.6.0, 1.5.1, 1.5.0
            Reporter: Sean Busbey
            Assignee: Sean Busbey
             Fix For: 1.5.2, 1.6.1, 1.7.0


I'd like to remove our use of master/slave terminology in favor of something that doesn't
carry a racially charged meaning.

As a side effect I'd also like to pick names that carry better meaning of how things work
within Accumulo.

In the case of a single cluster, I'd like to

* Change the Master role to Coordinator
* Change the associated master server package to coordinator
* Change the master configuration file to be named coordinators
* Change the slaves configuration file to be named tservers

In the case of the in-progress replication work I'd like to change terminology:

* use _Primary Cluster_  in place of _Master Cluster_
* use _Replica Clusters_ in place of _Slave Clusters_

I intend to do this in all active branches in a way that maintains compatibility of existing
configuration files and serialized actions (i.e. fate operations) within their major branch.
In the current unreleased major branch I expect upgrading will require user action (e.g. renaming
configuration files).



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

Mime
View raw message