GitHub user d2r opened a pull request:

    https://github.com/apache/storm/pull/995

    [STORM-1430] ui worker checkboxes

    This adds new checkboxes to the Executors tables of the component pages. 
Selecting these will enable the debugging/profiling actions to be performed on 
multiple workers while making it much easier to choose workers—especially for 
topologies with hundreds of workers.
    
    Look at the documentation to see what has changed. This is a little hard to 
test, because of 
[STORM-1452](https://issues.apache.org/jira/browse/STORM-1452). As a 
work-around, manually copy flight.bash to somewhere on the supervisor process's 
PATH and it should work.
    
    This also cleans up some tooltip placement and removes some extra bindings 
from core.clj, and I put these in their own commits so it is clearer.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/d2r/storm storm-1430-ui-worker-checkboxes

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/storm/pull/995.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #995
    
----
commit 181a46dfa561ba863a170efc5b688e5427ee7089
Author: Derek Dagit <[email protected]>
Date:   2016-01-08T05:06:03Z

    removes unnecessary bindings

commit a1c3ebbc249e5d35ae59531b424f90b930471378
Author: Derek Dagit <[email protected]>
Date:   2016-01-08T05:22:40Z

    corrects tooltip placement

commit 497aa0991b05b1e8296511bbc3aacf0d9a0830ad
Author: Derek Dagit <[email protected]>
Date:   2016-01-08T05:26:17Z

    Adds debugging checkboxes and links to exec table

commit c34266924a0bcb7c17bddc0a602580e892153651
Author: Derek Dagit <[email protected]>
Date:   2016-01-08T05:27:30Z

    updates profiling docs for action checkboxes & links

----


---
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.
---

Reply via email to