[
https://issues.apache.org/jira/browse/HBASE-13852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14621106#comment-14621106
]
Andrew Purtell commented on HBASE-13852:
----------------------------------------
I think we can talk about our architecture and components in new language
independent of code changes, with clarifications as needed as to particular
class or method names where that is relevant. It's going to be a work in
progress over multiple releases if undertaken because we have API compatibility
guarantees to consider.
> Replace master-slave terminology in book, site, and javadoc with a more
> modern vocabulary
> -----------------------------------------------------------------------------------------
>
> Key: HBASE-13852
> URL: https://issues.apache.org/jira/browse/HBASE-13852
> Project: HBase
> Issue Type: Task
> Components: documentation, site
> Reporter: Andrew Purtell
> Priority: Minor
> Fix For: 2.0.0
>
>
> We should reconsider our use of historical master-slave terminology
> everywhere - book, site, and javadoc - and replace it with a more modern
> vocabulary. There was a conversation in the background at HBaseCon about this
> (I was involved in one on Twitter). Out of some of the suggestions, I like
> "coordinator" as replacement for "master", and "worker" as one replacement
> for "slave", with the other the more descriptive "regionserver" or "region
> server".
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
