[GitHub] zeppelin issue #2544: [ZEPPELIN-2724] Another Attempt to solve the dead lock...

2017-09-11 Thread FireArrow
Github user FireArrow commented on the issue: https://github.com/apache/zeppelin/pull/2544 Any updates on this? ---

[GitHub] zeppelin issue #2544: [ZEPPELIN-2724] Another Attempt to solve the dead lock...

2017-08-24 Thread zjffdu
Github user zjffdu commented on the issue: https://github.com/apache/zeppelin/pull/2544 Is it must to have threadpool for this deadlock issue ? Can it be solved in a more clean way like you did in #2465 ? --- If your project is set up for it, you can reply to this email and have

[GitHub] zeppelin issue #2544: [ZEPPELIN-2724] Another Attempt to solve the dead lock...

2017-08-24 Thread sadhen
Github user sadhen commented on the issue: https://github.com/apache/zeppelin/pull/2544 No, this PR is for the master, we recently upgraded from 0.6.0 to master. Still to be confirmed and verified. However, we are running my PR in production for over 50 analysts (we mainly

[GitHub] zeppelin issue #2544: [ZEPPELIN-2724] Another Attempt to solve the dead lock...

2017-08-24 Thread 1ambda
Github user 1ambda commented on the issue: https://github.com/apache/zeppelin/pull/2544 I have a question (regarding concurrency issue, I think other might help to review this one) you said that > I confirm the code I wrote for Zeppelin 0.6.0 solved the dead lock