Re: Release 0.7.2

I saw another mailing thread now. Ignore it. On Mon, Jun 5, 2017 at 1:45 PM, Jongyoul Lee wrote: > Hi all, > > We have umbrella issue for 0.7.2. See https://issues.apache.org/ > jira/browse/ZEPPELIN-2276 > > I think it's almost done and there're some trivial issues which

Re: [DISCUSS] Reducing default interpreters while building and releasing Zeppelin

Felix, Yes, I said a bit confused. I want to release Zeppelin with some - not-all - interpreters, but deploy all interpreters into maven to install them if users want to use them. Moon, I think it's the best to fit the list as same as homepage by default as it makes users confused less. But if we

Release 0.7.2

Hi all, We have umbrella issue for 0.7.2. See https://issues.apache.org/jira/browse/ZEPPELIN-2276 I think it's almost done and there're some trivial issues which don't look like blockers. How about starting release process for 0.7.2? And I suggest moving remaining issues into 0.8.0. Regards, JL

Re: unable to restart zeppelin on AWS EMR

I found from the spark History server , that my old Zeppelin application was still alive and using up the resources. After I killed that application, it is working fine. Thanks everyone for all your help. On Sun, Jun 4, 2017 at 8:48 PM, shyla deshpande wrote: > Thanks

Re: unable to restart zeppelin on AWS EMR

Thanks everyone for the reply. Still having issues. Moon, I had tried sudo -u zeppelin /usr/lib/zeppelin/bin/zeppelin-daemon.sh restart and it did not work. I am using the Zeppelin Version 0.7.1. I checked the logs and in the logs, I saw the error message that the port 8890 already in use.

Re: [DISCUSS] Reducing default interpreters while building and releasing Zeppelin

If possible, we need to integrate the install script in zeppelin UI. As I would expect many users would ask why some interpreter is missing and how to install them. moon soo Lee 于2017年6月5日周一 上午2:06写道： > Following is last discussion related to release package size. > > >

Re: unable to restart zeppelin on AWS EMR

Have you tried restart with 'sudo -u zeppelin'? sudo -u zeppelin /usr/lib/zeppelin/bin/zeppelin-daemon.sh restart worked for me. Thanks, moon On Sat, Jun 3, 2017 at 11:51 PM Jonathan Kelly wrote: > Shyla, > > What release of EMR are you using? There was a problem

Re: [DISCUSS] Reducing default interpreters while building and releasing Zeppelin

Following is last discussion related to release package size. https://lists.apache.org/thread.html/69f606409790d7ba11422e8c6df941a75c5dfae0aca63eccf2f840bf@%3Cusers.zeppelin.apache.org%3E at this time, we have discussed about having bin-all (every interpreters), bin-min (selected interpreters),

Re: [DISCUSS] Reducing default interpreters while building and releasing Zeppelin

Sure - I think it will be important to discuss what criteria to use to decide what is included vs what will be released separately. _ From: Jongyoul Lee > Sent: Sunday, June 4, 2017 9:47 AM Subject: Re: [DISCUSS] Reducing

Re: [DISCUSS] Reducing default interpreters while building and releasing Zeppelin

It means we release with some interpreters and deploy all interpreters into maven separately. We already had a install-interpreter script inside it. If someone wants to install specific interpreter not included in default release package, they can use that script to install specific one. On Sun,

Re: unable to restart zeppelin on AWS EMR

Shyla, What release of EMR are you using? There was a problem with earlier releases of EMR where upstart was not properly tracking the Zeppelin PID, so "sudo stop zeppelin" wouldn't work. This has been fixed for a while, but I don't remember what version contained the fix. If you are not using

Re: unable to restart zeppelin on AWS EMR

Please check the zeppelin log Best Regard, Jeff Zhang From: shyla deshpande > Reply-To: "users@zeppelin.apache.org" > Date: Sunday, June 4,