When you submit application to cluster using dtcli, log4j properties are usually taken NodeManager unless you set custom log4j in config property file.
Thanks - Gaurav > On Aug 25, 2015, at 1:56 PM, Ganelin, Ilya <[email protected]> > wrote: > > I’m more or less running the default config here when running local tests. > I’m not sure what log4j it’s using when we submit to cluster with dtcli. > > log4j.rootLogger=WARN,CONSOLE > > log4j.appender.CONSOLE=org.apache.log4j.ConsoleAppender > log4j.appender.CONSOLE.layout=org.apache.log4j.PatternLayout > log4j.appender.CONSOLE.layout.ConversionPattern=%d{ISO8601} [%t] %-5p > %c{2} %M - %m%n > > log4j.appender.RFA=org.apache.log4j.RollingFileAppender > log4j.appender.RFA.layout=org.apache.log4j.PatternLayout > log4j.appender.RFA.layout.ConversionPattern=%d{ISO8601} [%t] %-5p %c{2} %M > - %m%n > log4j.appender.RFA.File=/tmp/app.log > > # to enable, add SYSLOG to rootLogger > log4j.appender.SYSLOG=org.apache.log4j.net.SyslogAppender > log4j.appender.SYSLOG.syslogHost=127.0.0.1 > log4j.appender.SYSLOG.layout=org.apache.log4j.PatternLayout > log4j.appender.SYSLOG.layout.conversionPattern=${dt.cid} %-5p [%t] %c{2} > %x - %m%n > log4j.appender.SYSLOG.Facility=LOCAL1 > > log4j.logger.org=info > #log4j.logger.org.apache.commons.beanutils=warn > log4j.logger.com.datatorrent=warn > > > > On 8/25/15, 12:11 PM, "Gaurav Gupta" <[email protected]> wrote: > >> Hi Ganelin, >> >> Can you please share your log4j settings? >> >> Thanks >> -Gaurav >> >> On Mon, Aug 24, 2015 at 7:57 PM, Ganelin, Ilya >> <[email protected]> >> wrote: >> >>> Apologies! This was a half-baked e-mail that I didn¹t intend to send. >>> >>> For others¹ reference, one may also be able to use. >>> >>> yarn logs -applicationId APP_ID -ContainerId ContainerID to get logs >>> for a >>> specific container. >>> >>> One other thing that we¹re seeing is that the yarn logs are saved by >>> node, >>> rather than by container. >>> E.g. >>> /tmp/logs/yarn_logs/NODE_1 >>> /tmp/logs/yarn_logs/NODE_2 >>> >>> /tmp/logs/yarn_logs/NODE_3 >>> >>> >>> Is this by design? Is there a way to change it so logs are output per >>> container? This would greatly facilitate debugging since then we would >>> have a unique log per JVM. >>> >>> Thank you! >>> >>> On 8/24/15, 7:53 PM, "Chinmay Kolhatkar" <[email protected]> >>> wrote: >>> >>>> Hi, >>>> >>>> If you have applicationId of the application you can use following >>> command >>>> to get all the logs of all the containers: >>>> >>>> yarn logs -applicationId <applicationId> >>>> >>>> Output of this command will be huge, so you might want to redirect the >>>> output to a file for analysis. >>>> >>>> -Chinmay. >>>> >>>> >>>> On Tue, Aug 25, 2015 at 6:32 AM, Ganelin, Ilya >>>> <[email protected]> >>>> wrote: >>>> >>>>> Hi all we¹re seeing failures in individual containers and wanted to >>>>> figure out how to retrieve logs. >>>>> ________________________________________________________ >>>>> >>>>> The information contained in this e-mail is confidential and/or >>>>> proprietary to Capital One and/or its affiliates and may only be used >>>>> solely in performance of work or services for Capital One. The >>>>> information >>>>> transmitted herewith is intended only for use by the individual or >>>>> entity >>>>> to which it is addressed. If the reader of this message is not the >>>>> intended >>>>> recipient, you are hereby notified that any review, retransmission, >>>>> dissemination, distribution, copying or other use of, or taking of >>> any >>>>> action in reliance upon this information is strictly prohibited. If >>> you >>>>> have received this communication in error, please contact the sender >>> and >>>>> delete the material from your computer. >>>>> >>> >>> ________________________________________________________ >>> >>> The information contained in this e-mail is confidential and/or >>> proprietary to Capital One and/or its affiliates and may only be used >>> solely in performance of work or services for Capital One. The >>> information >>> transmitted herewith is intended only for use by the individual or >>> entity >>> to which it is addressed. If the reader of this message is not the >>> intended >>> recipient, you are hereby notified that any review, retransmission, >>> dissemination, distribution, copying or other use of, or taking of any >>> action in reliance upon this information is strictly prohibited. If you >>> have received this communication in error, please contact the sender and >>> delete the material from your computer. >>> >>> > > ________________________________________________________ > > The information contained in this e-mail is confidential and/or proprietary > to Capital One and/or its affiliates and may only be used solely in > performance of work or services for Capital One. The information transmitted > herewith is intended only for use by the individual or entity to which it is > addressed. If the reader of this message is not the intended recipient, you > are hereby notified that any review, retransmission, dissemination, > distribution, copying or other use of, or taking of any action in reliance > upon this information is strictly prohibited. If you have received this > communication in error, please contact the sender and delete the material > from your computer.
