[ https://issues.apache.org/jira/browse/ACCUMULO-2844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15477388#comment-15477388 ]
Mike Walch commented on ACCUMULO-2844: -------------------------------------- bq. I will grep around to see what's there for replication, but am leaning towards just merging it in today. For the design docs for ACCUMULO-378, I can do a simple find/replace to change master/slave to primary/replica. I didn't touch that because i didn't know what to use. However, I see now in previous comments that this was suggested. > 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: Mike Walch > Fix For: 2.0.0 > > Time Spent: 50m > 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 (v6.3.4#6332)