+1 The Metadata response now has the controller broker in it too leveraging KafkaController.isActive. Clients can use that to identify the controller.
On Thu, Jun 23, 2016 at 7:17 PM, Gwen Shapira <[email protected]> wrote: > +1 from me too > > On Thu, Jun 23, 2016 at 3:06 PM, Ismael Juma <[email protected]> wrote: > > +1 from me. > > > > Ismael > > > > On Thu, Jun 23, 2016 at 11:57 PM, Roger Hoover <[email protected]> > > wrote: > > > >> Hi all, > >> > >> Does anyone have an issue with removing the broker state called > >> "RunningAsController"? > >> > >> The reasons to remove it are: > >> 1. It's currently broken. The purpose of the JIRA > >> <https://issues.apache.org/jira/browse/KAFKA-3761> was to report that > the > >> RunningAsController state gets overwritten back to "RunningAsBroker". > >> 2. It's not a useful state. > >> a. If clients want to use this metric to know whether a broker is > ready > >> to receive requests or not, they do not care whether or not the broker > is > >> the controller > >> b. there is already a separate boolean property, > KafkaController.isActive > >> which contains this information. > >> > >> Thanks, > >> > >> Roger > >> > -- Grant Henke Software Engineer | Cloudera [email protected] | twitter.com/gchenke | linkedin.com/in/granthenke
