Thanks for the follow up Moon.
I just happened to witness this blinking paragraph's output on his PC.
It's interesting that it only happens in Chrome for him.
(I use the same version of Chrome as him, and can't reproduce it)
We also checked that it happens for different interpreters - %sh and %spark
both show output, then it disappers very quickly.
It doesn't happen in IE for that user. (IE has other issues like it doesn't
show "Took x min y sec. Last updated by z at ..." at the bottom of a
paragraph).
ps. We also checked that user doesn't have ad blocking extensions in Chrome
or anything like that.
--
Ruslan Dautkhanov
On Sun, Jan 29, 2017 at 2:43 PM, moon soo Lee <m...@apache.org> wrote:
> Hi,
>
> I'm not sure which action can possibly make output blinks and disappears.
> But
>
> ERROR [2017-01-28 11:13:53,338] ({pool-4-thread-1}
> AppendOutputRunner.java[run]:68) - Wait for OutputBuffer queue
> interrupted: null
>
> can occur when interpreter process is terminating (e.g. user click
> interpreter restart).
>
> Thanks,
> moon
>
>
> On Sun, Jan 29, 2017 at 6:18 AM Ruslan Dautkhanov <dautkha...@gmail.com>
> wrote:
>
>> We upgraded our Zeppelin to yesterday's master snapshot.
>>
>> One of users complains that all his notes don't produces output
>> after the upgrade. It "blinks" with output and then output disappears.
>>
>> Here's quote from his email:
>>
>> My notebooks are having problems printing output. I can see the output
>> flash on the screen but then it disappears.
>>
>>
>> See that user's log attached. It has exceptions, including:
>>
>> ERROR [2017-01-28 11:13:53,338] ({pool-4-thread-1}
>> AppendOutputRunner.java[run]:68) - Wait for OutputBuffer queue
>> interrupted: null
>> ERROR [2017-01-28 11:41:53,272] ({qtp691893263-18}
>> ResourcePoolUtils.java[getAllResourcesExcept]:64)
>> -
>>
>>
>> I can't reproduce this issue, but we're running Zeppelin instances out of
>> the same
>> Zeppelin installation (running under different users though), so wanted
>> to bounce
>> this at other users. Have you seen this error before? Is this a known
>> issue?
>>
>>
>> Thanks,
>> Ruslan Dautkhanov
>>
>
