Re: Podling Report Reminder - November 2016

I do think it would be helpful to label our issues with tags, like "newbie". That's still a limitation imposed by INFRA with our preferred choice of issue tracker. On Tue, Nov 1, 2016 at 10:57 PM Christopher wrote: > I think growing our community is really the only

Re: Podling Report Reminder - November 2016

I think growing our community is really the only outstanding area of concern (with respect to graduation) that we need to work on. However, I'm not sure how we can do that. One thing is that we could reach out to Rya, and any other developers who are using Fluo that we know about, to explicitly

Re: Nice Report...

Hi John. Thanks for the advice. I think we basically agreed among ourselves that editing on the Wiki, with discussion on the list, as needed, was sufficient. But, that was really early on, and if we want to grow, it makes sense to utilize the mailing list for more discussions in advance. I think

Nice Report...

Fluo Podling, Thanks for posting your report. Looks good. A couple of notes from my side (as shepherd). - Try wherever possible to post/discuss the report on your MLs before posting to the incubator wiki. Its not a rule per se, but it helps ensure that you have community involvement

Re: Podling Report Reminder - November 2016

Thanks for posting, Keith. A couple of thoughts: * Growing the community is probably worth a few spots on the top-3 things to do * Lots of good things are written up that Fluo has done, but nothing on how you intend to grow Fluo beyond the current size. Good enough to sign off, but this is

Podling Report Reminder - November 2016

Dear podling, This email was sent by an automated system on behalf of the Apache Incubator PMC. It is an initial reminder to give you plenty of time to prepare your quarterly board report. The board meeting is scheduled for Wed, 16 November 2016, 10:30 am PDT. The report for your podling will

Re: debugging fluo

I suppose you don't see oracle files either? $ pwd /home/kturner/uno/install/logs/yarn/application_1478030941494_0001 $ find . . ./container_1478030941494_0001_01_01 ./container_1478030941494_0001_01_01/stdout ./container_1478030941494_0001_01_01/stderr

Re: debugging fluo

Which version of Fluo are you using? The properties 'io.fluo.log.*' were used before Apache incubation in 1.0.0-beta-1 or 1.0.0-beta-2. These properties were renamed in Fluo 1.0.0 to 'fluo.log.*'. You could be having problems if you built your application using Fluo 1.0.0-beta-2 and ran it

RE: debugging fluo

Hey Keith, Not seeing the worker logs in my container. Think my logback is configured incorrectly... [root@c190sv193 container_1476563020088_0069_01_02]# grep Rolling stdout 18:36:49,174 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type

Re: debugging fluo

I also saw the following line printed in stdout. Maybe this line was printed by LogbackUtil Logging to /home/kturner/uno/install/logs/yarn/application_1478030941494_0001/container_1478030941494_0001_01_04 using config ./conf/logback.xml On Tue, Nov 1, 2016 at 4:22 PM, Meier, Caleb

Re: debugging fluo

Yes. Keith, you are right. Logging config changes need to be made to /path/to/fluo/apps/$APPNAME/conf/logback.xml On Tue, Nov 1, 2016 at 4:21 PM Keith Turner wrote: > On Tue, Nov 1, 2016 at 4:02 PM, Mike Walch wrote: > > Were you able to find a

Re: debugging fluo

Caleb, I just ran Fluo locally with Uno. Below is some info I am seeing. Do you see anything about RollingFileAppender in the stdout file? $ pwd /home/kturner/uno/install/logs/yarn/application_1478030941494_0001/container_1478030941494_0001_01_04 $ ls stderr stdout worker_1_host1.log $

RE: debugging fluo

Hey Mike, So I’m not seeing any worker logs on my machines. The search find / | grep worker yielded nothing. Any ideas as to why these don't exist? I'm not sure that my fluo.log.dir system property is successfully being set by the LogbackUtil class. Maybe this has something to do with it?

Re: debugging fluo

Were you able to find a worker_*.log file for each of your workers? Below are some tips for debugging: - Each YARN container should have a 'stdout' and 'stderr' file. These files may have helpful error messages. Especially if a worker failed to start. Also, any calls to System.out and

Re: Podling Report Reminder - November 2016

I just udpated the wiki if anyone wants to review the changes. On Mon, Oct 31, 2016 at 3:56 PM, Josh Elser wrote: > I know you're already in a writing "mood", Keith. > > Don't forget about this one, please. Needs to be done by Wednesday this week > (48hrs). > > >

Re: debugging fluo

Hi Caleb, The logs for a Fluo application can be found in YARN but they are tricky to find. Fluo should have better documentation on this which I will add now. The easiest way to view the logs for a Fluo application is to use the web interface for the YARN resource manager

debugging fluo

Hello, I'm attempting to debug a Fluo application and am having difficulty locating the logs for my observers. I've looked within the logs for hadoop-yarn, but am not seeing any logging statements for my observers. Where do observers log out of the box in a normal cloudera distribution? Do