[jira] [Created] (ZEPPELIN-4491) Deadlock happens in Zeppelin when deleting multiple paragraphs synchronously via RestAPI

2019-12-16 Thread KylinJN (Jira)
KylinJN created ZEPPELIN-4491:
-

 Summary: Deadlock happens in Zeppelin when deleting multiple 
paragraphs synchronously via RestAPI
 Key: ZEPPELIN-4491
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-4491
 Project: Zeppelin
  Issue Type: Bug
  Components: Core
Affects Versions: 0.8.0
Reporter: KylinJN
 Fix For: 0.8.0


 

The zeppelin server is consistently getting deadlocked when delete multiple 
paragraphs which belong to different notes synchronously

The RestApi called is below:

|

// zeppelin-server\src\main\java\org\apache\zeppelin\rest\NotebookRestApi.java

/**
 * Delete paragraph REST API
 *
 * @param noteId ID of Note
 * @return JSON with status.OK
 * @throws IOException
 */
@DELETE
@Path("\{noteId}/paragraph/\{paragraphId}")
@ZeppelinApi
public Response deleteParagraph(@PathParam("noteId") String noteId,
 @PathParam("paragraphId") String paragraphId) throws IOException {
 LOG.info("delete paragraph {} {}", noteId, paragraphId);

 Note note = notebook.getNote(noteId);
 checkIfNoteIsNotNull(note);
 checkIfUserCanRead(noteId,
 "Insufficient privileges you cannot remove paragraph from this note");

 Paragraph p = note.getParagraph(paragraphId);
 checkIfParagraphIsNotNull(p);

 AuthenticationInfo subject = new 
AuthenticationInfo(SecurityUtils.getPrincipal());
 note.removeParagraph(SecurityUtils.getPrincipal(), paragraphId);
 note.persist(subject);
 notebookServer.broadcastNote(note);

 return new JsonResponse(Status.OK, "").build();
}

|

The relevant thread dump is below:

|

Server compiler detected.
JVM version is 25.212-b10
Deadlock Detection:

Found one Java-level deadlock:
=

"qtp1188392295-14051":
 waiting to lock Monitor@0x7f3dc800a108 (Object@0xc7706788, a 
java/util/LinkedList),
 which is held by "qtp1188392295-14087"
"qtp1188392295-14087":
 waiting to lock Monitor@0x7f3d10009278 (Object@0xc78d3e78, a 
java/util/LinkedList),
 which is held by "qtp1188392295-14051"

Found a total of 1 deadlock.

|

The stacktrace information is below:

|

“qtp1188392295-14087”:
 [1] org.apache.zeppelin.notebook.Note.getParagraphs (Note.java:750)
 [2] org.apache.zeppelin.notebook.Notebook.getJobListByUnixTime 
(Notebook.java:871)
 [3] org.apache.zeppelin.socket.NotebookServer.broadcastUpdateNoteJobInfo 
(NotebookServer.java:554)
 [4] 
org.apache.zeppelin.socket.NotebookServer$NotebookInformationListener.onParagraphRemove
 (NotebookServer.java:2,180)
 [5] org.apache.zeppelin.notebook.Notebook.onParagraphRemove 
(Notebook.java:1,083)
 [6] org.apache.zeppelin.notebook.Note.removeParagraph (Note.java:446)
 [7] org.apache.zeppelin.rest.NotebookRestApi.deleteParagraph 
(NotebookRestApi.java:615)
 [8] sun.reflect.GeneratedMethodAccessor27.invoke (null)
 [9] sun.reflect.DelegatingMethodAccessorImpl.invoke 
(DelegatingMethodAccessorImpl.java:43)
 [10] java.lang.reflect.Method.invoke (Method.java:498)
 [11] 
org.glassfish.jersey.server.model.internal.ResourceMethodInvocationHandlerFactory.lambda$static$0
 (ResourceMethodInvocationHandlerFactory.java:76)
 [12] 
org.glassfish.jersey.server.model.internal.ResourceMethodInvocationHandlerFactory$$Lambda$159.invoke
 (null)
 [13] 
org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher$1.run
 (AbstractJavaResourceMethodDispatcher.java:148)
 [14] 
org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.invoke
 (AbstractJavaResourceMethodDispatcher.java:191)
 [15] 
org.glassfish.jersey.server.model.internal.JavaResourceMethodDispatcherProvider$ResponseOutInvoker.doDispatch
 (JavaResourceMethodDispatcherProvider.java:200)
 [16] 
org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.dispatch
 (AbstractJavaResourceMethodDispatcher.java:103)
 [17] org.glassfish.jersey.server.model.ResourceMethodInvoker.invoke 
(ResourceMethodInvoker.java:493)
 [18] org.glassfish.jersey.server.model.ResourceMethodInvoker.apply 
(ResourceMethodInvoker.java:415)
 [19] org.glassfish.jersey.server.model.ResourceMethodInvoker.apply 
(ResourceMethodInvoker.java:104)
 [20] org.glassfish.jersey.server.ServerRuntime$1.run (ServerRuntime.java:277)
 [21] org.glassfish.jersey.internal.Errors$1.call (Errors.java:272)
 [22] org.glassfish.jersey.internal.Errors$1.call (Errors.java:268)
 [23] org.glassfish.jersey.internal.Errors.process (Errors.java:316)
 [24] org.glassfish.jersey.internal.Errors.process (Errors.java:298)
 [25] org.glassfish.jersey.internal.Errors.process (Errors.java:268)
 [26] org.glassfish.jersey.process.internal.RequestScope.runInScope 
(RequestScope.java:289)
 [27] org.glassfish.jersey.server.ServerRuntime.process (ServerRuntime.java:256)
 [28] org.glassfish.jersey.server.ApplicationHandler.handle 
(ApplicationHandler.java:703)
 [29] org.glassfish.jersey.servlet.WebComponent.serviceImpl 
(WebComponent.java:416)
 [30] org.glassfish.j

[jira] [Created] (ZEPPELIN-4490) Update ZeppelinContext document

2019-12-16 Thread Jeff Zhang (Jira)
Jeff Zhang created ZEPPELIN-4490:


 Summary: Update ZeppelinContext document
 Key: ZEPPELIN-4490
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-4490
 Project: Zeppelin
  Issue Type: Sub-task
Affects Versions: 0.9.0
Reporter: Jeff Zhang






--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[GitHub] [zeppelin] zjffdu opened a new pull request #3556: [ZEPPELIN-4488]. Support Flink 1.10

2019-12-16 Thread GitBox
zjffdu opened a new pull request #3556: [ZEPPELIN-4488]. Support Flink 1.10
URL: https://github.com/apache/zeppelin/pull/3556
 
 
   ### What is this PR for?
   This ticket is to support Flink 1.10, support blink planner and more rich 
sql function. 
   
   
   ### What type of PR is it?
   [ Improvement ]
   
   ### Todos
   * [ ] - Task
   
   ### What is the Jira issue?
   * https://issues.apache.org/jira/browse/ZEPPELIN-4488
   
   ### How should this be tested?
   * CI pass
   
   ### Screenshots (if appropriate)
   
   ### Questions:
   * Does the licenses files need update? No
   * Is there breaking changes for older versions? No
   * Does this needs documentation? No
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [zeppelin] zjffdu opened a new pull request #3555: [ZEPPELIN-4485]. Update how to install page

2019-12-16 Thread GitBox
zjffdu opened a new pull request #3555: [ZEPPELIN-4485]. Update how to install 
page
URL: https://github.com/apache/zeppelin/pull/3555
 
 
   ### What is this PR for?
   
   Update how to install page, remove the support for windows.
   
   
   ### What type of PR is it?
   [ Documentation ]
   
   ### Todos
   * [ ] - Task
   
   ### What is the Jira issue?
   * https://issues.apache.org/jira/browse/ZEPPELIN-4485
   
   ### How should this be tested?
   * No test needed
   
   ### Screenshots (if appropriate)
   
   ### Questions:
   * Does the licenses files need update? No
   * Is there breaking changes for older versions? No
   * Does this needs documentation? No
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services


Re: [DISCUSS] Create a preview for Zeppelin 0.9.0 before making RC

2019-12-16 Thread moon soo Lee
Right, 3 days for each RC for a major release is too short.
+1 for creating a preview and docker image as well :)

On Mon, Dec 16, 2019 at 7:40 AM Andrea Santurbano  wrote:

> Yes please!
> Would be awesome have a Docker container in order test it :)
>
> Il giorno lun 16 dic 2019 alle ore 16:24 Jeff Zhang  ha
> scritto:
>
> > Hi Folks,
> >
> > We have already done lots of works on 0.9.0, I think we should consider
> > about make a release for 0.9.0. But since Zeppelin is a very complicated
> > project considering its rich features, the regular process of testing it
> > for 3 days for each RC is too short in my opinion, so I suggest to
> create a
> > preview for each major release. Then the community has more time to test
> it
> > and we have more time to fix bugs and ensure the release quality. What do
> > you think ?
> >
> >
> > --
> > Best Regards
> >
> > Jeff Zhang
> >
>


Re: [DISCUSS] Create a preview for Zeppelin 0.9.0 before making RC

2019-12-16 Thread Andrea Santurbano
Yes please!
Would be awesome have a Docker container in order test it :)

Il giorno lun 16 dic 2019 alle ore 16:24 Jeff Zhang  ha
scritto:

> Hi Folks,
>
> We have already done lots of works on 0.9.0, I think we should consider
> about make a release for 0.9.0. But since Zeppelin is a very complicated
> project considering its rich features, the regular process of testing it
> for 3 days for each RC is too short in my opinion, so I suggest to create a
> preview for each major release. Then the community has more time to test it
> and we have more time to fix bugs and ensure the release quality. What do
> you think ?
>
>
> --
> Best Regards
>
> Jeff Zhang
>


[DISCUSS] Create a preview for Zeppelin 0.9.0 before making RC

2019-12-16 Thread Jeff Zhang
Hi Folks,

We have already done lots of works on 0.9.0, I think we should consider
about make a release for 0.9.0. But since Zeppelin is a very complicated
project considering its rich features, the regular process of testing it
for 3 days for each RC is too short in my opinion, so I suggest to create a
preview for each major release. Then the community has more time to test it
and we have more time to fix bugs and ensure the release quality. What do
you think ?


-- 
Best Regards

Jeff Zhang


[GitHub] [zeppelin] zjffdu commented on issue #3554: [ZEPPELIN-4489] remove zeppelin.anonymous.allowed configuration

2019-12-16 Thread GitBox
zjffdu commented on issue #3554: [ZEPPELIN-4489] remove 
zeppelin.anonymous.allowed configuration
URL: https://github.com/apache/zeppelin/pull/3554#issuecomment-566076723
 
 
   LGTM, thanks @prabhjyotsingh , let's wait for the Ci pass


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services