[
https://issues.apache.org/jira/browse/ACCUMULO-2844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17138386#comment-17138386
]
Sean Busbey commented on ACCUMULO-2844:
---------------------------------------
Broadly speaking, [~phrocker], yes I think these kinds of language adjustments
are still worthwhile for a project to make.
I don't think slack is considered a part of "it happened on the list" where as
GitHub is due to notifications? Ideally any discussion that is needed could
happen on the mailing list
> 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
> Priority: Major
> Fix For: 2.0.0
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> 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
(v8.3.4#803005)
