Deprecate MASTER and SLAVE terminology

[cmayer68]

problematic and unclear language relating to usage of the words MASTER and SLAVE are deprecated. in order or priority, outward facing use of these terms are to replaced by more specific terms like origin and replica.

as instances of the offending terms surface, please add them to comments on this issue.

[scosol]

These is the terminology I like:

Data Location and Authority (database): "Primary" and "Replica" ("primary" indicates that it is the authoritative source, "replica" is a copy) (^^ under the hood, it doesn't really matter that technically it's MASTER:MASTER, the role, the authority, and the data-flow changes without changing that relationship) "In normal operation, the metrics come in to the Primary, and are replicated to the Replica"

Metric ingest and Controller Operation (appserver): "Active" and "Secondary" (Or "Backup") - the "Active" one is self-describing, "Secondary" is a bit more ambiguous than "Backup", and our HA operations fit more of a "failing over to the backup" model- so I actually think I like "Backup" here" "In normal operation, Metrics come in to the Active Controller and are written to its local Primary Database. Upon failover, metrics instead are ingested by the Backup Controller and are written to its local Replica Database"

[cmayer68]

agreement across the board.

--curt

On Wed, Jul 1, 2020 at 10:37 AM scosol notifications@github.com wrote:

These is the terminology I like:

Data Location and Authority (database): "Primary" and "Replica" ("primary" indicates that it is the authoritative source, "replica" is a copy) (^^ under the hood, it doesn't really matter that technically it's MASTER:MASTER, the role, the authority, and the data-flow changes without changing that relationship) "In normal operation, the metrics come in to the Primary, and are replicated to the Replica"

Metric ingest and Controller Operation (appserver): "Active" and "Secondary" (Or "Backup") - the "Active" one is self-describing, "Secondary" is a bit more ambiguous than "Backup", and our HA operations fit more of a "failing over to the backup" model- so I actually think I like "Backup" here" "In normal operation, Metrics come in to the Active Controller and are written to its local Primary Database. Upon failover, metrics instead are ingested by the Backup Controller and are written to its local Replica Database"

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_Appdynamics_HA-2Dtoolkit_issues_110-23issuecomment-2D652555112&d=DwMCaQ&c=3_5eq9zYXWRS8ywqccmjfTRKM8mRLoQp6HBg1Tdb_Pc&r=nsJ1Vt4kkj1MF7fPuYx_OHpUcucCi7WPVJJQ5IIS6oA&m=lWc9LANgLhsG_S9ybBd4GZkaV_kr_WVbvW6xA5prhXw&s=CiXjNwOPdRJ8o4IHIZqrFOWgBt7x1DClLfPVeyF_AG0&e=, or unsubscribe https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_ADZV4TDHH53RYY25SFSXFOLRZNX3TANCNFSM4ONRETGA&d=DwMCaQ&c=3_5eq9zYXWRS8ywqccmjfTRKM8mRLoQp6HBg1Tdb_Pc&r=nsJ1Vt4kkj1MF7fPuYx_OHpUcucCi7WPVJJQ5IIS6oA&m=lWc9LANgLhsG_S9ybBd4GZkaV_kr_WVbvW6xA5prhXw&s=CSpiGXEXp1PZ0a8ag-c3g2alax-1Y7S6LyxAe6S3APk&e= .

-- Curt Mayer | Senior Architect, Customer Success Office 707.540.3441 | Mobile 707.540.3441 http://appdynamics.com/ Watch http://appdynamics.wistia.com/medias/56gnkuk6mvour Video | Try https://portal.appdynamics.com/account/signup/signupFormour FREE Trial | Twitter http://www.twitter.com/appdynamics| Facebook http://www.facebook.com/pages/AppDynamics/193264136815?ref=nf| appdynamics.com http://www.appdynamics.com/