Hi Jeff Thanks for your reply. The zeppelin console output is continuous when my scala code (spark sql) is running. The same code runs very from a separate spark-shell, so im suspecting that Zeppelin is executing the code in DEBUG mode.
When I installed Zeppelin, I did not change any settings. My main concern is the very slow performance. Kind Regards Amer On Sat, Oct 14, 2017 at 2:16 AM, Jianfeng (Jeff) Zhang < jzh...@hortonworks.com> wrote: > > These are zeppelin server log which is controlled by log4.properties under > ZEPPELIN_CONF_DIR. And I don’t understand why would you say these log > would affect the performance. > > Could you explain more ? > > > > > Best Regard, > Jeff Zhang > > > From: Amer Sheikh <amersh...@gmail.com> > Reply-To: "users@zeppelin.apache.org" <users@zeppelin.apache.org> > Date: Saturday, October 14, 2017 at 12:15 AM > To: "users@zeppelin.apache.org" <users@zeppelin.apache.org> > Subject: Re: Zepplin 0.7.3 DEBUG console output, how do I switch it > off!!! Spark 2.2.0-bin-hadoop2.7 > > Hi there > > Please see the console output > > > > On Thu, Oct 12, 2017 at 1:25 PM, Jeff Zhang <zjf...@gmail.com> wrote: > >> >> What kind of DEBUG log you see ? Can you paste it ? >> >> >> amersh...@gmail.com <amersh...@gmail.com>于2017年10月12日周四 下午5:44写道： >> >>> >>> >>> On 2017-10-12 10:41, "amersh...@gmail.com"<amersh...@gmail.com> wrote: >>> > Hello there >>> > >>> > I have installed Spark 2.20 and from the spark-shell, my scala code >>> works perfectly and performs well. >>> > >>> > The same scala executed from Zeppelin causes lots of DEBUG statements >>> to be printed in the console (almost non-stop) and the performance is very >>> slow. >>> > >>> > I have just installed binaries and haven't changed any configurations, >>> but it seems Zeppelin is running in debug mode... >>> > >>> > Help.. >>> > >>> > I use bin\zeppelin.cmd to start zeppelin. I'm on Windows Server 2012 >>> > >>> > Please help... >>> > >>> > >>> > PS >>> >>> The scala works perfectly within Zeppelin... Just very slow performance >>> and lots of Debug output... >>> >> >
