Hey Lukas, Log attachments seem to be filtered out. Could you try posting on a public paste, or github gist?
Cheers, Chris On 12/23/14 1:20 PM, "Lukas Steiblys" <[email protected]> wrote: >Unfortunately, that didn't help. Not only did the log show up in STDOUT, >the >job also failed to start (but the process didn't stop). Log attached. > >Lukas > >-----Original Message----- >From: Chris Riccomini >Sent: Tuesday, December 23, 2014 1:08 PM >To: [email protected] >Subject: Re: Changes to logging in Samza 0.8 > >Hey Lukas, > >I believe this is because you're using: > > job.factory.class=org.apache.samza.job.local.ThreadJobFactory > >Config settings you have that need to be set at JVM start time can't be >applied using the ThreadJobFactory, since the JVM has already started. As >a result, you get whatever JVM settings your run-job.sh script uses. For >log4j, I believe this means it'll pick up the log4j-console.xml in your >bin directory. > >Can you try using: > > job.factory.class=org.apache.samza.job.local.ProcessJobFactory > > >Cheers, >Chris > >On 12/23/14 1:00 PM, "Lukas Steiblys" <[email protected]> wrote: > >>I do not have a custom task.opts. >> >>Here's the full package we deploy: >>http://imbusy.org/temp/samza-package-0.1-SNAPSHOT-dist.tar.gz . I have >>also >>attached one of the deploy scripts we use for one of the five jobs >>available. They are all run locally. >> >>Lukas >> >>-----Original Message----- >>From: Chris Riccomini >>Sent: Tuesday, December 23, 2014 12:32 PM >>To: [email protected] >>Subject: Re: Changes to logging in Samza 0.8 >> >>Hey Lukas, >> >>The changes are probably from this ticket: >> >> https://issues.apache.org/jira/browse/SAMZA-109 >> >>The behavior you're observing does not sound correct, though. By default, >>if you have a log4j.xml in your lib directory, and don't have a custom >>task.opts, then you should get proper .log files. Do you have a custom >>task.opts? If so, could you paste it? >> >>Cheers, >>Chris >> >>On 12/23/14 11:23 AM, "Lukas Steiblys" <[email protected]> wrote: >> >>>I have recently upgraded from Samza 0.7 to 0.8 and noticed that, instead >>>of logging to a file using log4j to the log directory specified in the >>>environment variable SAMZA_LOG_DIR, all the logs are dumped to STDOUT. >>> >>>What changed in 0.8 and what¹s the path to upgrading to get the old >>>functionality back? >>> >>>Lukas
