Re: Unappealing CMD Logging when using Chukwa Config Substitutes

2015-09-24 Thread Lewis John Mcgibbney
Hi Eric, Coming back to this. In the QuickStart this is not mentioned so I'm also going to mention it. The log messages look kinda concerning to one who is not familiar with them. It is not obvious that if processes are started in a different order then these will not be present. I'll send a PR soo

Re: Unappealing CMD Logging when using Chukwa Config Substitutes

2015-09-23 Thread Lewis John Mcgibbney
Hi Eric, Yeah it does help. I am actually about to submit a patch for some updates to the current quick start documentation which will include this within the commentary. Thanks for quick feedback. Lewis On Tue, Sep 22, 2015 at 10:44 PM, Eric Yang wrote: > Hi Lewis, > > The messages are showing

Re: Unappealing CMD Logging when using Chukwa Config Substitutes

2015-09-22 Thread Eric Yang
Hi Lewis, The messages are showing up because log4j socket appender writes to stderr for those warn messages when it is unable to stream logs to log4j socket server. If Chukwa agent is started with socket adaptors prior to Hadoop and HBase, those messages will not show up. Hope this helps regard