[DISCUSS] Reducing default interpreters while building and releasing Zeppelin

[Jongyoul Lee]

Hi dev and users,

Recently, zeppelin.apache.org is being changed for increasing user
experiences and convenience. I like this kind of changes. I, however, saw
some arguments that which interpreters we will locate in the first page.
I'd like to expand its argument to the package we release.

Current zeppelin packages exceed 700MB with default option because Zeppelin
tried to include all interpreters by default. It was good at the early age
but, nowadays, Zeppelin community suffer from the size because ASF infra
allows the package size under 500MB. So I'd like to reduce the package size
by reducing default packages.

In case of rebuilding homepage, community proposed some criteria including
mailing list and # of question in stackoverflow. I think we can adapt same
criteria into release version of Zeppelin.

To handle this kind of issue, I think consensus of community is the most
important factor. If someone wants to have an idea to deal with it, please
feel free to talk about it.

Thanks,
Jongyoul Lee

-- 
이종열, Jongyoul Lee, 李宗烈
http://madeng.net

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

[Felix Cheung]

Are we proposing some interpreters to be built and released separately?

Is this going to be separate packaging? Or separate release pipeline?


_
From: Jongyoul Lee >
Sent: Friday, June 2, 2017 11:04 PM
Subject: [DISCUSS] Reducing default interpreters while building and releasing 
Zeppelin
To: dev >, 
>


Hi dev and users,

Recently, zeppelin.apache.org is being changed for 
increasing user experiences and convenience. I like this kind of changes. I, 
however, saw some arguments that which interpreters we will locate in the first 
page. I'd like to expand its argument to the package we release.

Current zeppelin packages exceed 700MB with default option because Zeppelin 
tried to include all interpreters by default. It was good at the early age but, 
nowadays, Zeppelin community suffer from the size because ASF infra allows the 
package size under 500MB. So I'd like to reduce the package size by reducing 
default packages.

In case of rebuilding homepage, community proposed some criteria including 
mailing list and # of question in stackoverflow. I think we can adapt same 
criteria into release version of Zeppelin.

To handle this kind of issue, I think consensus of community is the most 
important factor. If someone wants to have an idea to deal with it, please feel 
free to talk about it.

Thanks,
Jongyoul Lee

--
이종열, Jongyoul Lee, 李宗烈
http://madeng.net

unable to restart zeppelin on AWS EMR

[shyla deshpande]

I changed some configuration and want to restart  zeppelin on AWS EMR, but
unable to do. My local Zeppelin works fine.

I have tried
1.  zeppelin-daemon.sh restart   outputs[  OK  ]   but has
no effect.
2.  sudo stop zeppelin outputsstop: Unknown
instance:
3.  sudo start zeppelin outputs .  start: Job failed to
start

Zeppelin is running and able to login as anonymous user, unable to restart
. Appreciate your input.

Thanks