Github user revans2 commented on a diff in the pull request:
https://github.com/apache/incubator-storm/pull/236#discussion_r16676013
--- Diff: storm-core/src/ui/public/templates/component-page-template.html
---
@@ -133,11 +133,11 @@
</script>
<script id="bolt-executor-template" type="text/html">
<h2>Executors</h2>
-<table class="zebra-striped" id="bolt-executor-table"><thead><tr><th
class="header headerSortDown"><span class="tip right" title="The unique
executor ID.">Id</span></th><th class="header"><span data-original-title="The
length of time an Executor (thread) has been alive." class="tip
right">Uptime</span></th><th class="header"><span class="tip above" title="The
hostname reported by the remote host. (Note that this hostname is not the
result of a reverse lookup at the Nimbus node.)">Host</span></th><th
class="header"><span class="tip above" title="The port number used by the
Worker to which an Executor is assigned. Click on the port number to open the
logviewer page for this Worker.">Port</span></th><th class="header"><span
class="tip above" title="The number of Tuples emitted.">Emitted</span></th><th
class="header"><span class="tip above" title="The number of Tuples emitted that
sent to one or more bolts.">Transferred</span></th><th class="header"><span
class="tip above" title="If
this is around 1.0, the corresponding Bolt is running as fast as it can, so
you may want to increase the Bolt's parallelism. This is (number executed *
average execute latency) / measurement time.">Capacity (last
10m)</span></th><th class="header"><span data-original-title="The average time
a Tuple spends in the execute method. The execute method may complete without
sending an Ack for the tuple." class="tip above">Execute latency
(ms)</span></th><th class="header"><span class="tip above" title="The number of
incoming Tuples processed.">Executed</span></th><th class="header"><span
data-original-title="The average time it takes to Ack a Tuple after it is first
received. Bolts that join, aggregate or batch may not Ack a tuple until a
number of other Tuples have been received." class="tip above">Process latency
(ms)</span></th><th class="header"><span data-original-title="The number of
Tuples acknowledged by this Bolt." class="tip above">Acked</span></th><th
class="header"><span data
-original-title="The number of tuples Failed by this Bolt." class="tip
left">Failed</span></th></tr></thead>
+<table class="zebra-striped" id="bolt-executor-table"><thead><tr><th
class="header headerSortDown"><span class="tip right" title="The unique
executor ID.">Id</span></th><th class="header"><span data-original-title="The
length of time an Executor (thread) has been alive." class="tip
right">Uptime</span></th><th class="header"><span class="tip above" title="The
hostname reported by the remote host. (Note that this hostname is not the
result of a reverse lookup at the Nimbus node.)">Host</span></th><th
class="header"><span class="tip above" title="The port number used by the
Worker to which an Executor is assigned. Click on the port number to open the
logviewer page for this Worker.">Port</span></th><th class="header"><span
class="tip above" title="The number of Tuples emitted.">Emitted</span></th><th
class="header"><span class="tip above" title="The number of Tuples emitted that
sent to one or more bolts.">Transferred</span></th><th class="header"><span
class="tip above" title="If
this is around 1.0, the corresponding Bolt is running as fast as it can, so
you may want to increase the Bolt's parallelism. This is (number executed *
average execute latency) / measurement time.">Capacity (last
10m)</span></th><th class="header"><span data-original-title="The average time
a Tuple spends in the execute method. The execute method may complete without
sending an Ack for the tuple." class="tip above">Execute latency
(ms)</span></th><th class="header"><span class="tip above" title="The number of
incoming Tuples processed.">Executed</span></th><th class="header"><span
data-original-title="The average time it takes to Ack a Tuple after it is first
received. Bolts that join, aggregate or batch may not Ack a tuple until a
number of other Tuples have been received." class="tip above">Process latency
(ms)</span></th><th class="header"><span class="tip right" title="The length of
the executor's queue.">Queue Length</span></th><th class="header"><span
data-original-title="Th
e number of Tuples acknowledged by this Bolt." class="tip
above">Acked</span></th><th class="header"><span data-original-title="The
number of tuples Failed by this Bolt." class="tip
left">Failed</span></th></tr></thead>
--- End diff --
Can you split this line up? everything looks fine, but it is so long it is
really hard to tell what is happening with this line.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
