In our production setup, we have migrated to logback for other reasons. I remember our flume build was failing for some modules.
Naveen, please proceed with filing a jira. Personally I prefer to move to logback than to log4j 2. On 31 December 2016 at 16:19, Naveenkumar Panchappanavar <nave...@gmail.com> wrote: > Hi Team, > > Should we have to do code change ,the if we have to ,Then we were gonna > make changes. > > Or shall i need to open new jira for this. > > Regards > Naveen > > On Sat, Dec 31, 2016 at 4:06 PM, UMESH CHAUDHARY <umesh9...@gmail.com> > wrote: > > > +1 to the idea for upgrading to log4j2 rather having this the code. > > > > As per its usability, this functionality should be among "must have" > items > > in next release. We can open a new thread to discuss the pros and cons > > further. > > > > I referred this <http://logging.apache.org/log4j/2.x/manual/migration. > html> > > and > > looks like we need to update the code instead of using Log4j 1.x bridge. > > > > On Sat, 31 Dec 2016 at 15:09 Attila Simon <s...@cloudera.com> wrote: > > > > > I know logback and log4j2 can do this. Flume is shipped with log4j 1.2 > > but > > > in theory nothing prevents you to use a different backend for logging. > > It > > > is not guaranteed that it will work in practice, but it may worth a > try. > > > http://logback.qos.ch/manual/configuration.html#autoScan > > > https://logging.apache.org/log4j/2.x/manual/configuration.html (search > > for > > > "automatic reconfiguration") > > > > > > Laxman's finding is correct but it will possibly add a code binding > on a > > > particular logger backend. It has benefits and downsides so worth > > > discussing. I would rather investigate in upgrading to log4j2 because > > log4j > > > 1.x reached end of life. > > > > > > Cheers, > > > Attila > > > > > > > > > On 2016. Dec 31., Sat at 4:21, Laxman Ch <laxman....@gmail.com> wrote: > > > > > > > We may just need to change the flume's bootstrap class > > (Application.java) > > > > > > > > to do this. Please file a jira. > > > > > > > > > > > > > > > > > > > > > > > > On 30-Dec-2016 8:37 PM, "Naveenkumar" <nave...@gmail.com> wrote: > > > > > > > > > > > > > > > > Hi Laxman > > > > > > > > I have checked the documentation what you have suggested but the > thing > > > is I > > > > > > > > don't want to do flume source code modification because, according to > > the > > > > > > > > documentation we have to add method called configureandwatch in > classes > > > > > > > > wherever we are using Log4j so ,if we go with this. then we need to > > > change > > > > > > > > each and every class and above all internally flume source code uses > > > slf4j > > > > > > > > framework that to with lig4j so,is there any other way to handle this > > out > > > > > > > > Regards > > > > > > > > Naveen > > > > > > > > > > > > > > > > Sent from my iPhone > > > > > > > > > > > > > > > > > On 30-Dec-2016, at 4:22 PM, Laxman Ch <laxman....@gmail.com> > wrote: > > > > > > > > > > > > > > > > > > Naveen, > > > > > > > > > > > > > > > > > > This is more of a log4j question and this can be done with > > > configuration. > > > > > > > > > Please check log4j documentation. > > > > > > > > > https://logging.apache.org/log4j/1.2/faq.html#a3.6 > > > > > > > > > > > > > > > > > > Flume uses log4j 1.2. > > > > > > > > > > > > > > > > > > -- > > > > > > > > > Thanks, > > > > > > > > > Laxman > > > > > > > > > > > > > > > > > > On 30 December 2016 at 15:00, Naveenkumar Panchappanavar < > > > > > > > > nave...@gmail.com> > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > >> Hi Team, > > > > > > > > >> > > > > > > > > >> I am try to get the dynamic log information from the flume engine > > > *ie*: > > > > > > > > >> lets say i have started the flume agent and in meanwhile if i > change > > > the > > > > > > > > >> log level in log4j.properties it should dynamically take affect > > > > according > > > > > > > > >> to the log level which i configured without restarting the flume > > > engine. > > > > > > > > >> > > > > > > > > >> can any please help regarding this. > > > > > > > > >> > > > > > > > > >> Regards > > > > > > > > >> Naveen. > > > > > > > > >> > > > > > > > > > > > > > > -- Thanks, Laxman
