Andrew Wong created KUDU-2146:
---------------------------------
Summary: Tool to determine the leader master
Key: KUDU-2146
URL: https://issues.apache.org/jira/browse/KUDU-2146
Project: Kudu
Issue Type: Improvement
Components: master
Reporter: Andrew Wong
Going through some docs regarding multi-master migration, it seems like some
processes are warned against in order to prevent data loss.
As an example, adding masters to an existing multi-master deployment may mess
up the deployment and lose ops if new masters are added using a stale follower
as its "reference" master (i.e. the existing master from which data is copied
to the new master). As such, the docs warn against doing this migration
entirely, when it _should_ be safe to add the new masters using the most
up-to-date master as the reference master.
It would thus be helpful to be able to determine which master is leader, or at
least has the highest op-id (finding the leader may be harder to figure out if
the masters are down).
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
