> On April 26, 2017, 2:36 p.m., Alejandro Fernandez wrote: > > ambari-server/src/main/resources/common-services/KNOX/0.5.0.2.2/configuration/gateway-site.xml > > Line 61 (original), 61 (patched) > > <https://reviews.apache.org/r/58735/diff/1/?file=1700384#file1700384line61> > > > > Does this value have to change for existing clusters? > > If so, should an Ambari Upgrade modify the property if unkerberized.
I don't think that we need to change this for existing clusters.. maybe the users expect the logs to be there since it was turned on from the beginning. If Kerberos is not enabled (or was disabled), then no logging will be done... so the value of the property is irrelevant (when Kerberos is not enabled). - Robert ----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/58735/#review173072 ----------------------------------------------------------- On April 26, 2017, 9:09 a.m., Laszlo Puskas wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/58735/ > ----------------------------------------------------------- > > (Updated April 26, 2017, 9:09 a.m.) > > > Review request for Ambari, Robert Levas and Sandor Magyari. > > > Bugs: AMBARI-20849 > https://issues.apache.org/jira/browse/AMBARI-20849 > > > Repository: ambari > > > Description > ------- > > When enabling kerberos for a cluster containing KNOX the amount of loges > generated is too high by default. > > > Diffs > ----- > > > ambari-server/src/main/resources/common-services/KNOX/0.5.0.2.2/configuration/gateway-site.xml > ad599e0 > > > Diff: https://reviews.apache.org/r/58735/diff/1/ > > > Testing > ------- > > In progress. > > > Thanks, > > Laszlo Puskas > >
