[ https://issues.apache.org/jira/browse/KUDU-3311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Wong updated KUDU-3311: ------------------------------ Labels: newbie (was: ) > Allow masters to start up with a list of masters with a diff of one from > what's on disk > --------------------------------------------------------------------------------------- > > Key: KUDU-3311 > URL: https://issues.apache.org/jira/browse/KUDU-3311 > Project: Kudu > Issue Type: Improvement > Components: master > Reporter: Andrew Wong > Priority: Major > Labels: newbie > > Now that Kudu automatically adds a master if we start up a new master > alongside an existing only set of masters, we should also loosen the > restriction that the gflag is the same as the existing Raft config, in case > users want to add a master and then restart the entire cluster at the same > time. > This seems like it would be common enough for orchestration tools like CM, > which marks the cluster as stale and suggests a full service restart upon > adding a new master role. -- This message was sent by Atlassian Jira (v8.3.4#803005)