Re: Release 0.7.2

[Jongyoul Lee]

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 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
>
> --
> 이종열, Jongyoul Lee, 李宗烈
> http://madeng.net
>



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

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

[Jongyoul Lee]

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 want to add more interpreters, I think
mailing questions and related issues are one of the proper criteria.

Jeff,
Agreed. We already had a menu but it just shows how to use
install-interpreter.sh.

On Mon, Jun 5, 2017 at 9:36 AM, Jeff Zhang  wrote:

>
> 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.
>>
>> https://lists.apache.org/thread.html/69f606409790d7ba11422e8c6df941
>> a75c5dfae0aca63eccf2f840bf@%3Cusers.zeppelin.apache.org%3E
>>
>> at this time, we have discussed about having bin-all (every
>> interpreters), bin-min (selected interpreters), bin-netinst (no
>> interpreters) package but didn't conclude the criteria and how we make a
>> decision.
>>
>> Jongyoul, do you have any idea about criteria?
>>
>> Thanks,
>> moon
>>
>> On Sun, Jun 4, 2017 at 10:47 AM Felix Cheung 
>> wrote:
>>
>>> 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 default interpreters while building and
>>> releasing Zeppelin
>>> To: dev 
>>>
>> Cc: 
>>>
>>
>>>
>>>
>>> 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, Jun 4, 2017 at 9:11 AM, Felix Cheung 
>>> wrote:
>>>
>>> > 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 mailto:jongy...@gmail.com
>>> >>
>>> > Sent: Friday, June 2, 2017 11:04 PM
>>> > Subject: [DISCUSS] Reducing default interpreters while building and
>>> > releasing Zeppelin
>>>
>> > To: dev mailto:d...@zeppelin.apache.org
>>> >>, <
>>>
>>
>>> > users@zeppelin.apache.org>> >>
>>> >
>>> >
>>> > 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
>>> >
>>> >
>>> >
>>>
>>>
>>> --
>>> 이종열, Jongyoul Lee, 李宗烈
>>> http://madeng.net
>>>
>>>
>>>


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

Release 0.7.2

[Jongyoul Lee]

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

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

Re: unable to restart zeppelin on AWS EMR

[shyla deshpande]

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 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. Since
>  sudo stop zeppelin did not work , I killed the process that wasusing 8890.
>
> Now I am able to start and stop zeppelin using sudo start zeppelin and
> sudo stop zeppelin.
>
> But now I have a new problem, The cassandra interpreter works fine, but
> the spark interpreter hangs, and I have to cancel the job. Even a simple
> job as the following hangs
> val df1 = sc.parallelize(1 to 10).toDF()
> df1.show()
>
> I see the following in the log
>
> WARN [2017-06-05 03:33:33,283] ({Timer-0} Logging.scala[logWarning]:66) -
> Initial job has not accepted any resources; check your cluster UI to ensure
> that workers are registered and have sufficient resources
>
> Please help, I just made some config changes and wanted to restart
> Zeppelin and now I messed up my presentation.
>
> On Sun, Jun 4, 2017 at 11:19 AM, moon soo Lee  wrote:
>
>> 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 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 the
>>> latest release, you might want to try that. Otherwise, if you're already
>>> using the latest version, there might be something else going on.
>>>
>>> ~ Jonathan
>>> On Sat, Jun 3, 2017 at 8:28 PM shyla deshpande 
>>> wrote:
>>>
 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

>>>
>

Re: unable to restart zeppelin on AWS EMR

[shyla deshpande]

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. Since
 sudo stop zeppelin did not work , I killed the process that wasusing 8890.

Now I am able to start and stop zeppelin using sudo start zeppelin and sudo
stop zeppelin.

But now I have a new problem, The cassandra interpreter works fine, but the
spark interpreter hangs, and I have to cancel the job. Even a simple job as
the following hangs
val df1 = sc.parallelize(1 to 10).toDF()
df1.show()

I see the following in the log

WARN [2017-06-05 03:33:33,283] ({Timer-0} Logging.scala[logWarning]:66) -
Initial job has not accepted any resources; check your cluster UI to ensure
that workers are registered and have sufficient resources

Please help, I just made some config changes and wanted to restart Zeppelin
and now I messed up my presentation.

On Sun, Jun 4, 2017 at 11:19 AM, moon soo Lee  wrote:

> 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 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 the
>> latest release, you might want to try that. Otherwise, if you're already
>> using the latest version, there might be something else going on.
>>
>> ~ Jonathan
>> On Sat, Jun 3, 2017 at 8:28 PM shyla deshpande 
>> wrote:
>>
>>> 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
>>>
>>

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

[Jeff Zhang]

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.
>
>
> 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), bin-netinst (no interpreters) package but
> didn't conclude the criteria and how we make a decision.
>
> Jongyoul, do you have any idea about criteria?
>
> Thanks,
> moon
>
> On Sun, Jun 4, 2017 at 10:47 AM Felix Cheung 
> wrote:
>
>> 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 default interpreters while building and
>> releasing Zeppelin
>> To: dev 
>>
> Cc: 
>>
>
>>
>>
>> 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, Jun 4, 2017 at 9:11 AM, Felix Cheung 
>> wrote:
>>
>> > 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 mailto:jongy...@gmail.com
>> >>
>> > Sent: Friday, June 2, 2017 11:04 PM
>> > Subject: [DISCUSS] Reducing default interpreters while building and
>> > releasing Zeppelin
>>
> > To: dev mailto:d...@zeppelin.apache.org
>> >>, <
>>
>
>> > users@zeppelin.apache.org> >>
>> >
>> >
>> > 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
>> >
>> >
>> >
>>
>>
>> --
>> 이종열, Jongyoul Lee, 李宗烈
>> http://madeng.net
>>
>>
>>

Re: unable to restart zeppelin on AWS EMR

[moon soo Lee]

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 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 the
> latest release, you might want to try that. Otherwise, if you're already
> using the latest version, there might be something else going on.
>
> ~ Jonathan
> On Sat, Jun 3, 2017 at 8:28 PM shyla deshpande 
> wrote:
>
>> 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
>>
>

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

[moon soo Lee]

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), bin-netinst (no interpreters) package but
didn't conclude the criteria and how we make a decision.

Jongyoul, do you have any idea about criteria?

Thanks,
moon

On Sun, Jun 4, 2017 at 10:47 AM Felix Cheung 
wrote:

> 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 default interpreters while building and
> releasing Zeppelin
> To: dev 
> Cc: 
>
>
>
> 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, Jun 4, 2017 at 9:11 AM, Felix Cheung 
> wrote:
>
> > 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 mailto:jongy...@gmail.com
> >>
> > Sent: Friday, June 2, 2017 11:04 PM
> > Subject: [DISCUSS] Reducing default interpreters while building and
> > releasing Zeppelin
> > To: dev mailto:d...@zeppelin.apache.org
> >>, <
> > users@zeppelin.apache.org >>
> >
> >
> > 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
> >
> >
> >
>
>
> --
> 이종열, Jongyoul Lee, 李宗烈
> http://madeng.net
>
>
>

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

[Felix Cheung]

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 mailto:jongy...@gmail.com>>
Sent: Sunday, June 4, 2017 9:47 AM
Subject: Re: [DISCUSS] Reducing default interpreters while building and 
releasing Zeppelin
To: dev mailto:d...@zeppelin.apache.org>>
Cc: mailto:users@zeppelin.apache.org>>


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, Jun 4, 2017 at 9:11 AM, Felix Cheung 
mailto:felixcheun...@hotmail.com>>
wrote:

> 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 
> mailto:jongy...@gmail.com>>
> Sent: Friday, June 2, 2017 11:04 PM
> Subject: [DISCUSS] Reducing default interpreters while building and
> releasing Zeppelin
> To: dev 
> mailto:d...@zeppelin.apache.org>>,
>  <
> users@zeppelin.apache.org>
>
>
> 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
>
>
>


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

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

[Jongyoul Lee]

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, Jun 4, 2017 at 9:11 AM, Felix Cheung 
wrote:

> 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 mailto:jongy...@gmail.com>>
> Sent: Friday, June 2, 2017 11:04 PM
> Subject: [DISCUSS] Reducing default interpreters while building and
> releasing Zeppelin
> To: dev mailto:d...@zeppelin.apache.org>>, <
> users@zeppelin.apache.org>
>
>
> 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
>
>
>


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