I'm sorry but there was a mistake in my way of checking.
Now, I can see the "RUNNING" status on a notebook while a paragraph is
executing. Last night, I didn't see "RUNNING" status because an interpreter
was in state of launching and a paragraph was not executing.
On Fri, Dec 1, 2017 at 10:23 PM,
Github user asfgit closed the pull request at:
https://github.com/apache/zeppelin/pull/2688
---
Github user asfgit closed the pull request at:
https://github.com/apache/zeppelin/pull/2693
---
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/2693
Thanks @kjmrknsn for the fix! LGTM and merge this to master as a hotfix.
---
Github user kjmrknsn commented on the issue:
https://github.com/apache/zeppelin/pull/2658
I sent a PR to fix this issue: https://github.com/apache/zeppelin/pull/2693
---
GitHub user kjmrknsn opened a pull request:
https://github.com/apache/zeppelin/pull/2693
Downgrade JGit from 4.9.0 to 4.5.4
### What is this PR for?
The version of JGit was updated to 4.9.0 at
https://github.com/apache/zeppelin/pull/2658.
However, this version is not s
Github user kjmrknsn commented on the issue:
https://github.com/apache/zeppelin/pull/2658
@kokes I confirmed that CI test against JGit 4.9.0 always fails and one
against JGit 4.5.4 passed.
## JGit 4.9.0
* comimt:
https://github.com/kjmrknsn/zeppelin/commit/2afba274c83d4e9
Danilo Ascione created ZEPPELIN-3088:
Summary: Run paragraph is not working in pyspark
Key: ZEPPELIN-3088
URL: https://issues.apache.org/jira/browse/ZEPPELIN-3088
Project: Zeppelin
Issue
I’d +1 docker or container support (mesos, dc/os, k8s)
But I think that they are separate things. If users are authenticated and
interpreter is impersonating each user, the risk of system disruption should be
low. This is typically how to secure things in a system, through user directory
(eg LD
Github user kokes commented on the issue:
https://github.com/apache/zeppelin/pull/2658
It looks a bit better, only one build errs, of the four tests there are two
timeouts, will try it again to see if it helps.
---
Github user kokes commented on the issue:
https://github.com/apache/zeppelin/pull/2658
Darn, that's unfortunate (and it didn't click initially, because a lot of
the other builds are based on Java 7).
A better interim solution would be to downgrade the library (but still
upgra
Thanks for verifying it. It looks like a bug
On Fri, Dec 1, 2017 at 9:56 PM, Keiji Yoshida wrote:
> Me too. I could not see the "RUNNING" state on the git commit:
> 4dc6bf57080e11ebf0533bbedcdba780c5e71398.
>
> On Fri, Dec 1, 2017 at 9:25 PM, Jongyoul Lee wrote:
>
> > Hi dev,
> >
> > In current
Github user kjmrknsn commented on the issue:
https://github.com/apache/zeppelin/pull/2658
And it seems that this change causes the failure of the test
https://travis-ci.org/kokes/zeppelin/jobs/299146854 because Zeppelin process
didn't respond to any requests.
---
Github user kjmrknsn commented on the issue:
https://github.com/apache/zeppelin/pull/2658
I noticed that the JGit minimum execution environment became Java 8 from
JGit 4.6.
https://projects.eclipse.org/projects/technology.jgit/releases/4.6
> Update JGit minimum execution
Me too. I could not see the "RUNNING" state on the git commit:
4dc6bf57080e11ebf0533bbedcdba780c5e71398.
On Fri, Dec 1, 2017 at 9:25 PM, Jongyoul Lee wrote:
> Hi dev,
>
> In current master, Can anyone see "RUNNING" state when running script? I've
> run long running script but cannot see "RUNNING
Hi dev,
In current master, Can anyone see "RUNNING" state when running script? I've
run long running script but cannot see "RUNNING" state, it's just left
"PENNING" for a long time then changed "FINISHED".
Can anyone verify it?
Regards,
Jongyoul
--
이종열, Jongyoul Lee, 李宗烈
http://madeng.net
Github user hero0926 commented on the issue:
https://github.com/apache/zeppelin/pull/2011
We're meeting same problem as karuppayya. when we trying to unpersist in
pyspark+zeppelin, memory dosen't released - so sc.stop for second hand,
zeppelin interpreter dies... I concern OOM error c
17 matches
Mail list logo