[ https://issues.apache.org/jira/browse/ACCUMULO-2844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17136024#comment-17136024 ]
Marc Parisi edited comment on ACCUMULO-2844 at 6/16/20, 2:46 PM: ----------------------------------------------------------------- I think as situations evolve so do our understandings and opinions. Therefore, [~busbey], do you think this deserves to be re-visited? I do but am curious of your perspective ( I suspect you would given what you've said previously). May be useful to have a follow up that gets others discussing a rename for master. Do you think we should open up a follow up on GH or in slack? was (Author: phrocker): I think as situations evolve so do our understandings and opinions. Therefore, [~busbey], do you think this deserves to be re-visited? I do but am curious of your perspective. May be useful to have a follow up that gets others discussing a rename for master. > 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)