You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@storm.apache.org by "P. Taylor Goetz" <pt...@gmail.com> on 2014/06/23 23:27:14 UTC
Storm UI Broken in Master
Can someone verify that Storm UI is working in the master branch?
It may just be my environment, but it’s not working for me (display is mostly blank).
Thanks,
Taylor
Re: Storm UI Broken in Master
Posted by Kishorkumar Patil <kp...@yahoo-inc.com.INVALID>.
Taylor, Harsha,
I created fix for this issue:
https://issues.apache.org/jira/browse/STORM-370
https://github.com/apache/incubator-storm/pull/160
https://github.com/apache/incubator-storm/pull/161
/Kishor
On 6/23/14, 5:58 PM, "P. Taylor Goetz" <pt...@gmail.com> wrote:
>Don't worry. I imagine it's my environment. I ran out of time before I
>had to step out, and just wanted to see if anyone had a master env. Up to
>confirm.
>
>> On Jun 23, 2014, at 6:11 PM, Harsha <ma...@harsha.io> wrote:
>>
>> Taylor,
>> Overall it works for me. Is the entire UI show up blank or some
>> pages.
>> -Harsha
>>
>>> On Mon, Jun 23, 2014, at 02:52 PM, Kishorkumar Patil wrote:
>>> Taylor,
>>>
>>> It fails on component page - mostly blank tables symptom. If the
>>> component
>>> json response has some of list elements empty ( e.g. boltStats,
>>>executors
>>> or spoutStats, outputStats inputStats).
>>>
>>> In such situation, I noticed earlier the component page call to js
>>> tablesorter throws exception ( - wherever table has 0 rows). This
>>> exception stops further rendering of elements. Hence you notice mostly
>>> empty UI.
>>>
>>> This requires additional check to ensure that table sorter is not
>>>invoked
>>> on empty tables.
>>>
>>> Earlier today, I created a pull request that handles this particular
>>> issue.
>>> Please look at the pull request for master branch
>>> [https://github.com/apache/incubator-storm/pull/154]
>>> For security, [https://github.com/apache/incubator-storm/pull/155]
>>>
>>> /Kishor
>>>
>>>
>>>
>>>
>>>
>>>
>>>> On 6/23/14, 4:27 PM, "P. Taylor Goetz" <pt...@gmail.com> wrote:
>>>>
>>>> Can someone verify that Storm UI is working in the master branch?
>>>>
>>>> It may just be my environment, but it¹s not working for me (display is
>>>> mostly blank).
>>>>
>>>> Thanks,
>>>>
>>>> Taylor
>>>
Re: Storm UI Broken in Master
Posted by "P. Taylor Goetz" <pt...@gmail.com>.
Don't worry. I imagine it's my environment. I ran out of time before I had to step out, and just wanted to see if anyone had a master env. Up to confirm.
> On Jun 23, 2014, at 6:11 PM, Harsha <ma...@harsha.io> wrote:
>
> Taylor,
> Overall it works for me. Is the entire UI show up blank or some
> pages.
> -Harsha
>
>> On Mon, Jun 23, 2014, at 02:52 PM, Kishorkumar Patil wrote:
>> Taylor,
>>
>> It fails on component page - mostly blank tables symptom. If the
>> component
>> json response has some of list elements empty ( e.g. boltStats, executors
>> or spoutStats, outputStats inputStats).
>>
>> In such situation, I noticed earlier the component page call to js
>> tablesorter throws exception ( - wherever table has 0 rows). This
>> exception stops further rendering of elements. Hence you notice mostly
>> empty UI.
>>
>> This requires additional check to ensure that table sorter is not invoked
>> on empty tables.
>>
>> Earlier today, I created a pull request that handles this particular
>> issue.
>> Please look at the pull request for master branch
>> [https://github.com/apache/incubator-storm/pull/154]
>> For security, [https://github.com/apache/incubator-storm/pull/155]
>>
>> /Kishor
>>
>>
>>
>>
>>
>>
>>> On 6/23/14, 4:27 PM, "P. Taylor Goetz" <pt...@gmail.com> wrote:
>>>
>>> Can someone verify that Storm UI is working in the master branch?
>>>
>>> It may just be my environment, but it¹s not working for me (display is
>>> mostly blank).
>>>
>>> Thanks,
>>>
>>> Taylor
>>
Re: Storm UI Broken in Master
Posted by Harsha <ma...@harsha.io>.
Taylor,
Overall it works for me. Is the entire UI show up blank or some
pages.
-Harsha
On Mon, Jun 23, 2014, at 02:52 PM, Kishorkumar Patil wrote:
> Taylor,
>
> It fails on component page - mostly blank tables symptom. If the
> component
> json response has some of list elements empty ( e.g. boltStats, executors
> or spoutStats, outputStats inputStats).
>
> In such situation, I noticed earlier the component page call to js
> tablesorter throws exception ( - wherever table has 0 rows). This
> exception stops further rendering of elements. Hence you notice mostly
> empty UI.
>
> This requires additional check to ensure that table sorter is not invoked
> on empty tables.
>
> Earlier today, I created a pull request that handles this particular
> issue.
> Please look at the pull request for master branch
> [https://github.com/apache/incubator-storm/pull/154]
> For security, [https://github.com/apache/incubator-storm/pull/155]
>
> /Kishor
>
>
>
>
>
>
> On 6/23/14, 4:27 PM, "P. Taylor Goetz" <pt...@gmail.com> wrote:
>
> >Can someone verify that Storm UI is working in the master branch?
> >
> >It may just be my environment, but it¹s not working for me (display is
> >mostly blank).
> >
> >Thanks,
> >
> >Taylor
>
Re: Storm UI Broken in Master
Posted by Kishorkumar Patil <kp...@yahoo-inc.com.INVALID>.
Taylor,
It fails on component page - mostly blank tables symptom. If the component
json response has some of list elements empty ( e.g. boltStats, executors
or spoutStats, outputStats inputStats).
In such situation, I noticed earlier the component page call to js
tablesorter throws exception ( - wherever table has 0 rows). This
exception stops further rendering of elements. Hence you notice mostly
empty UI.
This requires additional check to ensure that table sorter is not invoked
on empty tables.
Earlier today, I created a pull request that handles this particular issue.
Please look at the pull request for master branch
[https://github.com/apache/incubator-storm/pull/154]
For security, [https://github.com/apache/incubator-storm/pull/155]
/Kishor
On 6/23/14, 4:27 PM, "P. Taylor Goetz" <pt...@gmail.com> wrote:
>Can someone verify that Storm UI is working in the master branch?
>
>It may just be my environment, but it¹s not working for me (display is
>mostly blank).
>
>Thanks,
>
>Taylor