Re: Are storm metrics reported through JMX too?

y also provide ping, health-check, thread dump etc which are useful too. Please ignore if its already there in the code shared above and I could not find it. Thanks, SG On Mon, Dec 5, 2016 at 9:49 PM, Alessandro Bellina <abell...@yahoo-inc.com> wrote: > Hi Taylor > > Please see la

Re: Are storm metrics reported through JMX too?

I suggested over the weekend.  This is definitely a work in progress, but you should be able to instantiate reporters for your purposes. Thanks, Alessandro On Monday, December 5, 2016, 1:26:41 PM CST, Alessandro Bellina <abell...@yahoo-inc.com.INVALID> wrote:Yes. Will PR this tonight

Re: Are storm metrics reported through JMX too?

porter configuration stuff you have. If what you have is incomplete/WIP, that’s not a big deal as the metrics_v2 branch is a feature branch and we’ll have plenty of opportunities to clean things up. -Taylor > On Nov 29, 2016, at 3:27 PM, Alessandro Bellina <abell...@yahoo-inc.com> >

Re: Are storm metrics reported through JMX too?

X too? Alessandro, Where do you stand with the reporter configuration via the storm.yaml config file? I have metrics collection for workers and disruptor queues almost ready, but now I’m looking for flexible configuration (right now I have reporters hard coded). -Taylor > On Nov 29, 2016, at 1:5

Re: Are storm metrics reported through JMX too?

how we progress. > > Cheers, > -- > Abhishek > > On Tue, Oct 18, 2016 at 1:23 PM Alessandro Bellina <abell...@yahoo-inc.com > > > wrote: > > > + Naren, Austin, and Abhishek, the students from the University of > > Illinois Open Source class. > > > >

Re: Storm UI does not load

Serkan I think the screenshot would be useful. Mind filing a JIRA with the details? This would help:- what version of chrome/firefox?- what page(s)?- output from the developer console.. if you have a line number/file that is really useful I ran 1.0.2 UI locally and submitted a topology but was

Re: Is this the list of metrics reported by storm in JMX?

T.I. I ran jconsole and ended up with the same result for a worker. That said, if you turn on JMX for the daemons you end up with a new MBean "metrics" (as given by storm.daemon.metrics.reporter.plugin.domain). This is coming from: JmxPreparableReporter. - For nimbus I see stuff like:

Re: Are storm metrics reported through JMX too?

blockquote, div.yahoo_quoted { margin-left: 0 !important; border-left:1px #715FFA solid !important; padding-left:1ex !important; background-color:white !important; } Yeap that's a requirement from our perspective (working through this list). Sure I think as usual we can start with master with

Re: Are storm metrics reported through JMX too?

k. > > Anyway, someone volunteer to renew metrics system via Dropwizard or JStorm > metrics it would be awesome. I'm focused to improve Storm SQL and there's > no other active contributor on Storm SQL yet so I couldn't look at the > other side. > > - Jungtaek Lim (HeartSaVioR) &g

Re: Are storm metrics reported through JMX too?

system On Tuesday, October 11, 2016 1:13 PM, Alessandro Bellina <abell...@yahoo-inc.com.INVALID> wrote: I think what Bobby is referring to is that the metrics consumer is another bolt, so stats are flowing through storm. What does changing the model to polling buy us? I could see case

Re: Are storm metrics reported through JMX too?

I think what Bobby is referring to is that the metrics consumer is another bolt, so stats are flowing through storm. What does changing the model to polling buy us? I could see cases were we'd need more error handling for instance slow/busy workers. If we think that writing a new system is the

[jira] [Created] (STORM-2078) Enable paging in worker data tables

Alessandro Bellina created STORM-2078: - Summary: Enable paging in worker data tables Key: STORM-2078 URL: https://issues.apache.org/jira/browse/STORM-2078 Project: Apache Storm Issue

[jira] [Created] (STORM-2066) Fix scheduler status when in isolation and running with less slots than requested

Alessandro Bellina created STORM-2066: - Summary: Fix scheduler status when in isolation and running with less slots than requested Key: STORM-2066 URL: https://issues.apache.org/jira/browse/STORM-2066

[jira] [Assigned] (STORM-2066) Fix scheduler status when in isolation and running with less slots than requested

[ https://issues.apache.org/jira/browse/STORM-2066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alessandro Bellina reassigned STORM-2066: - Assignee: Alessandro Bellina > Fix scheduler status when in isolat

[jira] [Assigned] (STORM-2064) Add storm name and function, access result and function to log-thrift-access

[ https://issues.apache.org/jira/browse/STORM-2064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alessandro Bellina reassigned STORM-2064: - Assignee: Alessandro Bellina > Add storm name and function, access res

[jira] [Created] (STORM-2064) Add storm name and function, access result and function to log-thrift-access

Alessandro Bellina created STORM-2064: - Summary: Add storm name and function, access result and function to log-thrift-access Key: STORM-2064 URL: https://issues.apache.org/jira/browse/STORM-2064

[jira] [Created] (STORM-2063) Add thread name in worker logs

Alessandro Bellina created STORM-2063: - Summary: Add thread name in worker logs Key: STORM-2063 URL: https://issues.apache.org/jira/browse/STORM-2063 Project: Apache Storm Issue Type

[jira] [Commented] (STORM-1949) Backpressure can cause spout to stop emitting and stall topology

[ https://issues.apache.org/jira/browse/STORM-1949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15430073#comment-15430073 ] Alessandro Bellina commented on STORM-1949: --- I replicated a halted topology using my own

[jira] [Assigned] (STORM-1949) Backpressure can cause spout to stop emitting and stall topology

[ https://issues.apache.org/jira/browse/STORM-1949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alessandro Bellina reassigned STORM-1949: - Assignee: Alessandro Bellina > Backpressure can cause spout to stop emitt

[jira] [Commented] (STORM-1949) Backpressure can cause spout to stop emitting and stall topology

[ https://issues.apache.org/jira/browse/STORM-1949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15429427#comment-15429427 ] Alessandro Bellina commented on STORM-1949: --- [~roshan_naik] I was going to run your example

Re: [Discussion] Stopping feature development for storm-core on 1.x-branch

Just a contributors point of view.. I think the idea to reclaim jiras that are assigned but without progress is a good one. After that is done, in order to not end up in the same place, I think after a task gets assigned it needs to be given a due date (something sane), and updated periodically

[jira] [Assigned] (STORM-2039) Backpressure refactoring in worker and executor

[ https://issues.apache.org/jira/browse/STORM-2039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alessandro Bellina reassigned STORM-2039: - Assignee: Alessandro Bellina > Backpressure refactoring in worker and execu

[jira] [Created] (STORM-2035) Surface supervisor configs to nimbus for serving to UI

Alessandro Bellina created STORM-2035: - Summary: Surface supervisor configs to nimbus for serving to UI Key: STORM-2035 URL: https://issues.apache.org/jira/browse/STORM-2035 Project: Apache Storm

[jira] [Created] (STORM-2034) Remove Show System Stats button and refactor UI accordingly

Alessandro Bellina created STORM-2034: - Summary: Remove Show System Stats button and refactor UI accordingly Key: STORM-2034 URL: https://issues.apache.org/jira/browse/STORM-2034 Project: Apache

[jira] [Created] (STORM-2024) Add local store autocomplete to the logger name input field as a convenience (dynamic log level settings)

Alessandro Bellina created STORM-2024: - Summary: Add local store autocomplete to the logger name input field as a convenience (dynamic log level settings) Key: STORM-2024 URL: https://issues.apache.org/jira

Re: Question about Storm UI

give it a try but it might be better to take a look at.  Btw, IMO, if we can show dashboards without dependencies that would be amazing, and having some dependencies which are easy to install and maintain would be still nice. Thanks,Jungtaek Lim (HeartSaVioR) 2016년 8월 1일 (월) 오전 1:43, Alessandro B

Re: Question about Storm UI

HeartSaVIoR This is different than STORM-1994. By the way added some screenshots there to clarify. I agree it would be good to reorganize the statistics shown in the UI. Perhaps having two parts to this, one goes to a dashboard like Grafana, while the simpler metrics (snapshots, or

[jira] [Comment Edited] (STORM-1994) Add table with per-topology & worker resource usage and components in (new) supervisor and topology pages

[ https://issues.apache.org/jira/browse/STORM-1994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15401199#comment-15401199 ] Alessandro Bellina edited comment on STORM-1994 at 7/31/16 4:01 PM: I

[jira] [Updated] (STORM-1994) Add table with per-topology & worker resource usage and components in (new) supervisor and topology pages

[ https://issues.apache.org/jira/browse/STORM-1994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alessandro Bellina updated STORM-1994: -- Attachment: topology_page_worker_table.png > Add table with per-topology &

[jira] [Updated] (STORM-1994) Add table with per-topology & worker resource usage and components in (new) supervisor and topology pages

[ https://issues.apache.org/jira/browse/STORM-1994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alessandro Bellina updated STORM-1994: -- Attachment: supervisor_page_worker_table.png > Add table with per-topology &

[jira] [Updated] (STORM-1994) Add table with per-topology & worker resource usage and components in (new) supervisor and topology pages

[ https://issues.apache.org/jira/browse/STORM-1994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alessandro Bellina updated STORM-1994: -- Attachment: (was: screenshot-1.png) > Add table with per-topology & worker r

[jira] [Commented] (STORM-1994) Add table with per-topology & worker resource usage and components in (new) supervisor and topology pages

[ https://issues.apache.org/jira/browse/STORM-1994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15401199#comment-15401199 ] Alessandro Bellina commented on STORM-1994: --- I added a screenshot of the new supervisor page

[jira] [Updated] (STORM-1994) Add table with per-topology & worker resource usage and components in (new) supervisor and topology pages

[ https://issues.apache.org/jira/browse/STORM-1994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alessandro Bellina updated STORM-1994: -- Attachment: screenshot-1.png > Add table with per-topology & worker resourc

[jira] [Updated] (STORM-1994) Add table with per-topology & worker resource usage and components in (new) supervisor and topology pages

[ https://issues.apache.org/jira/browse/STORM-1994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alessandro Bellina updated STORM-1994: -- Attachment: (was: supervisor-page.png) > Add table with per-topology &

[jira] [Updated] (STORM-1994) Add table with per-topology & worker resource usage and components in (new) supervisor and topology pages

[ https://issues.apache.org/jira/browse/STORM-1994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alessandro Bellina updated STORM-1994: -- Attachment: supervisor-page.png > Add table with per-topology & worker resourc

[jira] [Created] (STORM-1995) downloadChunk in nimbus.clj should close the input stream

Alessandro Bellina created STORM-1995: - Summary: downloadChunk in nimbus.clj should close the input stream Key: STORM-1995 URL: https://issues.apache.org/jira/browse/STORM-1995 Project: Apache

[jira] [Created] (STORM-1994) Add table with per-topology & worker resource usage and components in (new) supervisor and topology pages

Alessandro Bellina created STORM-1994: - Summary: Add table with per-topology & worker resource usage and components in (new) supervisor and topology pages Key: STORM-1994 URL: https://issues.apache.org/

[jira] [Comment Edited] (STORM-1889) Datatables error message displayed when viewing UI

[ https://issues.apache.org/jira/browse/STORM-1889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15387030#comment-15387030 ] Alessandro Bellina edited comment on STORM-1889 at 7/21/16 2:32 AM

[jira] [Commented] (STORM-1889) Datatables error message displayed when viewing UI

[ https://issues.apache.org/jira/browse/STORM-1889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15387030#comment-15387030 ] Alessandro Bellina commented on STORM-1889: --- The caching issue is being addressed in a PR I put

[jira] [Assigned] (STORM-1942) Extra closing div tag in topology.html

[ https://issues.apache.org/jira/browse/STORM-1942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alessandro Bellina reassigned STORM-1942: - Assignee: Alessandro Bellina > Extra closing div tag in topology.h

[jira] [Assigned] (STORM-1890) Employ cache-busting method to ensure newly deployed UI forces browsers to refetch scripts, templates, and CSS

[ https://issues.apache.org/jira/browse/STORM-1890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alessandro Bellina reassigned STORM-1890: - Assignee: Alessandro Bellina > Employ cache-busting method to ensure ne

[jira] [Commented] (STORM-1890) Employ cache-busting method to ensure newly deployed UI forces browsers to refetch scripts, templates, and CSS

[ https://issues.apache.org/jira/browse/STORM-1890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15359583#comment-15359583 ] Alessandro Bellina commented on STORM-1890: --- See: https://github.com/apache/storm/pull/1536

[jira] [Created] (STORM-1942) Extra closing div tag in topology.html

Alessandro Bellina created STORM-1942: - Summary: Extra closing div tag in topology.html Key: STORM-1942 URL: https://issues.apache.org/jira/browse/STORM-1942 Project: Apache Storm Issue

[jira] [Commented] (STORM-1890) Employ cache-busting method to ensure newly deployed UI forces browsers to refetch scripts, templates, and CSS

[ https://issues.apache.org/jira/browse/STORM-1890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15320848#comment-15320848 ] Alessandro Bellina commented on STORM-1890: --- There is a flag in jquery (cache:false) but it's

[jira] [Updated] (STORM-1890) Employ cache-busting method to ensure newly deployed UI forces browsers to refetch scripts, templates, and CSS

[ https://issues.apache.org/jira/browse/STORM-1890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alessandro Bellina updated STORM-1890: -- Description: Currently we don't employ cache busting techniques in the Storm UI while

[jira] [Updated] (STORM-1890) Employ cache-busting method to ensure newly deployed UI forces browsers to refetch scripts, templates, and CSS

[ https://issues.apache.org/jira/browse/STORM-1890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alessandro Bellina updated STORM-1890: -- Description: Currently we don't employ cache busting techniques in the Storm UI while

[jira] [Updated] (STORM-1890) Employ cache-busting method to ensure newly deployed UI forces browsers to refetch scripts, templates, and CSS

[ https://issues.apache.org/jira/browse/STORM-1890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alessandro Bellina updated STORM-1890: -- Description: Currently we don't employ cache busting techniques in the Storm UI while

[jira] [Updated] (STORM-1890) Employ cache-busting method to ensure newly deployed UI forces browsers to refetch scripts, templates, and CSS

[ https://issues.apache.org/jira/browse/STORM-1890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alessandro Bellina updated STORM-1890: -- Description: Currently we don't employ cache busting techniques in the Storm UI while

[jira] [Updated] (STORM-1890) Employ cache-busting method to ensure newly deployed UI forces browsers to refetch scripts, templates, and CSS

[ https://issues.apache.org/jira/browse/STORM-1890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alessandro Bellina updated STORM-1890: -- Description: Currently we don't employ cache busting techniques in the Storm UI while

[jira] [Updated] (STORM-1890) Employ cache-busting method to ensure newly deployed UI forces browsers to refetch scripts, templates, and CSS

[ https://issues.apache.org/jira/browse/STORM-1890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alessandro Bellina updated STORM-1890: -- Description: Currently we don't employ cache busting techniques in the Storm UI while

[jira] [Updated] (STORM-1890) Employ cache-busting method to ensure newly deployed UI forces browsers to refetch scripts, templates, and CSS

[ https://issues.apache.org/jira/browse/STORM-1890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alessandro Bellina updated STORM-1890: -- Description: Currently we don't employ cache busting techniques in the Storm UI while

[jira] [Updated] (STORM-1890) Employ cache-busting method to ensure newly deployed UI forces browsers to refetch scripts, templates, and CSS

[ https://issues.apache.org/jira/browse/STORM-1890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alessandro Bellina updated STORM-1890: -- Description: Currently we don't employ cache busting techniques in the Storm UI while

[jira] [Updated] (STORM-1890) Employ cache-busting method to ensure newly deployed UI forces browsers to refetch scripts, templates, and CSS

[ https://issues.apache.org/jira/browse/STORM-1890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alessandro Bellina updated STORM-1890: -- Description: Currently we don't employ cache busting techniques in the Storm UI while

[jira] [Updated] (STORM-1890) Employ cache-busting method to ensure newly deployed UI forces browsers to refetch scripts, templates, and CSS

[ https://issues.apache.org/jira/browse/STORM-1890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alessandro Bellina updated STORM-1890: -- Description: Currently we don't employ cache busting techniques in the Storm UI while

[jira] [Updated] (STORM-1890) Employ cache-busting method to ensure newly deployed UI forces browsers to refetch scripts, templates, and CSS

[ https://issues.apache.org/jira/browse/STORM-1890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alessandro Bellina updated STORM-1890: -- Description: Currently we don't employ cache busting techniques in the Storm UI while

[jira] [Updated] (STORM-1890) Employ cache-busting method to ensure newly deployed UI forces browsers to refetch scripts, templates, and CSS

[ https://issues.apache.org/jira/browse/STORM-1890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alessandro Bellina updated STORM-1890: -- Description: Currently we don't employ cache busting techniques in the Storm UI while

[jira] [Created] (STORM-1890) Employ cache-busting method to ensure newly deployed UI forces browsers to refetch scripts, templates, and CSS

Alessandro Bellina created STORM-1890: - Summary: Employ cache-busting method to ensure newly deployed UI forces browsers to refetch scripts, templates, and CSS Key: STORM-1890 URL: https://issues.apache.org

[jira] [Created] (STORM-1648) DRPCSpout should attempt reconnect if on fail it cannot reach client

Alessandro Bellina created STORM-1648: - Summary: DRPCSpout should attempt reconnect if on fail it cannot reach client Key: STORM-1648 URL: https://issues.apache.org/jira/browse/STORM-1648 Project

[jira] [Created] (STORM-1641) Inconsistency when creating backpressure znode subtree

Alessandro Bellina created STORM-1641: - Summary: Inconsistency when creating backpressure znode subtree Key: STORM-1641 URL: https://issues.apache.org/jira/browse/STORM-1641 Project: Apache Storm

[jira] [Commented] (STORM-1231) port backtype.storm.scheduler.EvenScheduler to java

[ https://issues.apache.org/jira/browse/STORM-1231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15191400#comment-15191400 ] Alessandro Bellina commented on STORM-1231: --- Xin, are you currently working on this, or could I

[jira] [Created] (STORM-1614) Clean backpressure zk node in do-cleanup

Alessandro Bellina created STORM-1614: - Summary: Clean backpressure zk node in do-cleanup Key: STORM-1614 URL: https://issues.apache.org/jira/browse/STORM-1614 Project: Apache Storm

[jira] [Created] (STORM-1594) org.apache.storm.tuple.Fields can throw NPE if given invalid field in selector

Alessandro Bellina created STORM-1594: - Summary: org.apache.storm.tuple.Fields can throw NPE if given invalid field in selector Key: STORM-1594 URL: https://issues.apache.org/jira/browse/STORM-1594

[jira] [Assigned] (STORM-1228) port backtype.storm.fields-test to java

[ https://issues.apache.org/jira/browse/STORM-1228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alessandro Bellina reassigned STORM-1228: - Assignee: Alessandro Bellina (was: Jark Wu) > port backtype.storm.fields-t

[jira] [Commented] (STORM-1228) port backtype.storm.fields-test to java

[ https://issues.apache.org/jira/browse/STORM-1228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15167108#comment-15167108 ] Alessandro Bellina commented on STORM-1228: --- Hi Jark, I am. I have the clojure->java translat

[jira] [Assigned] (STORM-1228) port backtype.storm.fields-test to java

[ https://issues.apache.org/jira/browse/STORM-1228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alessandro Bellina reassigned STORM-1228: - Assignee: Alessandro Bellina > port backtype.storm.fields-test to j

[jira] [Assigned] (STORM-1255) port backtype.storm.utils-test to java

[ https://issues.apache.org/jira/browse/STORM-1255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alessandro Bellina reassigned STORM-1255: - Assignee: Alessandro Bellina > port backtype.storm.utils-test to j