You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "Corey J. Nolet (JIRA)" <ji...@apache.org> on 2014/12/18 04:29:15 UTC
[jira] [Updated] (ACCUMULO-2844) Remove master/slave terminology
[ https://issues.apache.org/jira/browse/ACCUMULO-2844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Corey J. Nolet updated ACCUMULO-2844:
-------------------------------------
Fix Version/s: (was: 1.6.2)
1.6.3
> Remove master/slave terminology
> -------------------------------
>
> Key: ACCUMULO-2844
> URL: https://issues.apache.org/jira/browse/ACCUMULO-2844
> Project: Accumulo
> Issue Type: Task
> Affects Versions: 1.5.0, 1.5.1, 1.6.0
> Reporter: Sean Busbey
> Assignee: Sean Busbey
> Fix For: 1.5.3, 1.7.0, 1.6.3
>
>
> 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.3.4#6332)