Github user arunmahadevan commented on the pull request:
https://github.com/apache/storm/pull/1217#issuecomment-203792662
1 . The tooltip takes some time to show up, whereas the tooltip on other
elements like the title elements under Topology summary shows up immediately. I
played aro
[
https://issues.apache.org/jira/browse/STORM-1632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15219500#comment-15219500
]
ASF GitHub Bot commented on STORM-1632:
---
Github user arunmahadevan commented on the
[
https://issues.apache.org/jira/browse/STORM-855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15219609#comment-15219609
]
ASF GitHub Bot commented on STORM-855:
--
Github user mjsax commented on the pull reques
Github user mjsax commented on the pull request:
https://github.com/apache/storm/pull/694#issuecomment-203830224
Closing this (also closing the JIRA) as Bobby's work
(https://github.com/apache/storm/pull/765) got merged and I don't have time to
work on this right now.
---
If your p
Github user mjsax closed the pull request at:
https://github.com/apache/storm/pull/694
---
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 enable
[
https://issues.apache.org/jira/browse/STORM-855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15219610#comment-15219610
]
ASF GitHub Bot commented on STORM-855:
--
Github user mjsax closed the pull request at:
[
https://issues.apache.org/jira/browse/STORM-855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax closed STORM-855.
-
Resolution: Unresolved
https://github.com/apache/storm/pull/765 got merged with does this somewhat
Github user HeartSaVioR commented on the pull request:
https://github.com/apache/storm/pull/1272#issuecomment-203836195
@arunmahadevan
I've just done with performance test, and the result is a bit different
what I expected.
![eventlogger-performance-test-storm-1662-graph
[
https://issues.apache.org/jira/browse/STORM-1662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15219624#comment-15219624
]
ASF GitHub Bot commented on STORM-1662:
---
Github user HeartSaVioR commented on the pu
Github user HeartSaVioR commented on the pull request:
https://github.com/apache/storm/pull/1272#issuecomment-203841803
In result, sorry I changed my vote to +0 for now.
I think we should make the test result stable before taking any actions.
- test several times and take a
[
https://issues.apache.org/jira/browse/STORM-1662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15219633#comment-15219633
]
ASF GitHub Bot commented on STORM-1662:
---
Github user HeartSaVioR commented on the pu
[
https://issues.apache.org/jira/browse/STORM-1632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jungtaek Lim updated STORM-1632:
Assignee: Roshan Naik (was: Jungtaek Lim)
> Disable event logging by default
>
[
https://issues.apache.org/jira/browse/STORM-1669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jungtaek Lim updated STORM-1669:
Assignee: Xin Wang (was: Jungtaek Lim)
> Fix SolrUpdateBolt flush bug
> ---
Github user HeartSaVioR commented on the pull request:
https://github.com/apache/storm/pull/1270#issuecomment-203850400
+1
---
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
[
https://issues.apache.org/jira/browse/STORM-1652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15219652#comment-15219652
]
ASF GitHub Bot commented on STORM-1652:
---
Github user HeartSaVioR commented on the pu
Github user asfgit closed the pull request at:
https://github.com/apache/storm/pull/1270
---
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 enab
[
https://issues.apache.org/jira/browse/STORM-1652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15219659#comment-15219659
]
ASF GitHub Bot commented on STORM-1652:
---
Github user asfgit closed the pull request
[
https://issues.apache.org/jira/browse/STORM-1652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jungtaek Lim resolved STORM-1652.
-
Resolution: Fixed
Fix Version/s: 1.0.0
Thanks [~satish.duggana], I merged into master and 1
Github user zhuoliu commented on a diff in the pull request:
https://github.com/apache/storm/pull/1280#discussion_r58066223
--- Diff: storm-core/src/clj/org/apache/storm/daemon/supervisor.clj ---
@@ -296,11 +293,15 @@
(worker-launcher-and-wait conf user ["signal" pid "9
[
https://issues.apache.org/jira/browse/STORM-1667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15219957#comment-15219957
]
ASF GitHub Bot commented on STORM-1667:
---
Github user zhuoliu commented on a diff in
Github user nicom commented on the pull request:
https://github.com/apache/storm/pull/639#issuecomment-203982738
@caofangkun
Sorry for commenting on such an old pull request, but we recently also
encountered the problem this patch is trying to address.
> Does have an
[
https://issues.apache.org/jira/browse/STORM-946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15220008#comment-15220008
]
ASF GitHub Bot commented on STORM-946:
--
Github user nicom commented on the pull reques
Github user satishd commented on a diff in the pull request:
https://github.com/apache/storm/pull/1280#discussion_r58077961
--- Diff: storm-core/src/clj/org/apache/storm/daemon/supervisor.clj ---
@@ -296,11 +293,15 @@
(worker-launcher-and-wait conf user ["signal" pid "9
[
https://issues.apache.org/jira/browse/STORM-1667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15220069#comment-15220069
]
ASF GitHub Bot commented on STORM-1667:
---
Github user satishd commented on a diff in
Github user zhuoliu commented on a diff in the pull request:
https://github.com/apache/storm/pull/1280#discussion_r58081089
--- Diff: storm-core/src/clj/org/apache/storm/daemon/supervisor.clj ---
@@ -296,11 +293,15 @@
(worker-launcher-and-wait conf user ["signal" pid "9
[
https://issues.apache.org/jira/browse/STORM-1667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15220099#comment-15220099
]
ASF GitHub Bot commented on STORM-1667:
---
Github user zhuoliu commented on a diff in
Github user satishd commented on the pull request:
https://github.com/apache/storm/pull/1280#issuecomment-204034110
+1 LGTM
---
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
enable
Github user ptgoetz commented on the pull request:
https://github.com/apache/storm/pull/1281#issuecomment-204034904
+1
---
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
[
https://issues.apache.org/jira/browse/STORM-1667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15220261#comment-15220261
]
ASF GitHub Bot commented on STORM-1667:
---
Github user satishd commented on the pull r
[
https://issues.apache.org/jira/browse/STORM-1668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15220264#comment-15220264
]
ASF GitHub Bot commented on STORM-1668:
---
Github user ptgoetz commented on the pull r
Github user ptgoetz commented on the pull request:
https://github.com/apache/storm/pull/1284#issuecomment-204039770
+1
---
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
[
https://issues.apache.org/jira/browse/STORM-1669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15220275#comment-15220275
]
ASF GitHub Bot commented on STORM-1669:
---
Github user ptgoetz commented on the pull r
Satish Duggana created STORM-1670:
-
Summary: LocalState#get(String) can throw FileNotFoundException
which results in not removing worker heartbeats.
Key: STORM-1670
URL: https://issues.apache.org/jira/browse/STORM
[
https://issues.apache.org/jira/browse/STORM-1535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Priyank Shah reassigned STORM-1535:
---
Assignee: Priyank Shah (was: Dan Bahir)
> Storm-HDFS - When using keytab Kerberos ticket is
[
https://issues.apache.org/jira/browse/STORM-1670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Satish Duggana reassigned STORM-1670:
-
Assignee: Satish Duggana
> LocalState#get(String) can throw FileNotFoundException which r
Github user revans2 commented on the pull request:
https://github.com/apache/storm/pull/639#issuecomment-204058115
@nicom
Please file a JIRA at https://issues.apache.org/jira under the STORM
project describing what you described here. We ran into a similar issue, but I
woul
[
https://issues.apache.org/jira/browse/STORM-946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15220347#comment-15220347
]
ASF GitHub Bot commented on STORM-946:
--
Github user revans2 commented on the pull requ
Zhuo Liu created STORM-1671:
---
Summary: Enable logviewer to delete directory with no yaml file
Key: STORM-1671
URL: https://issues.apache.org/jira/browse/STORM-1671
Project: Apache Storm
Issue Type
[
https://issues.apache.org/jira/browse/STORM-1663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15220372#comment-15220372
]
ASF GitHub Bot commented on STORM-1663:
---
Github user asfgit closed the pull request
[
https://issues.apache.org/jira/browse/STORM-1663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Joseph Evans resolved STORM-1663.
Resolution: Fixed
Fix Version/s: 2.0.0
> Clicking on an active topology from
Github user asfgit closed the pull request at:
https://github.com/apache/storm/pull/1279
---
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 enab
[
https://issues.apache.org/jira/browse/STORM-1665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Joseph Evans resolved STORM-1665.
Resolution: Fixed
Went in with STORM-1663
> Worker cannot instantiate kryo
> -
[
https://issues.apache.org/jira/browse/STORM-1666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Joseph Evans resolved STORM-1666.
Resolution: Fixed
Assignee: Robert Joseph Evans
Fix Version/s: 2.0.0
[
https://issues.apache.org/jira/browse/STORM-1671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15220393#comment-15220393
]
ASF GitHub Bot commented on STORM-1671:
---
GitHub user zhuoliu opened a pull request:
GitHub user zhuoliu opened a pull request:
https://github.com/apache/storm/pull/1285
[STORM-1671] Enable logviewer to delete a dir without yaml
For those old and dead worker directories, in some weird case, there is no
yaml file in it. We should enable logviewer to delete them.
Github user zhuoliu commented on the pull request:
https://github.com/apache/storm/pull/1285#issuecomment-204066326
Will also cherry-pick this patch to 1.x.
---
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
[
https://issues.apache.org/jira/browse/STORM-1671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15220396#comment-15220396
]
ASF GitHub Bot commented on STORM-1671:
---
Github user zhuoliu commented on the pull r
Github user asfgit closed the pull request at:
https://github.com/apache/storm/pull/1131
---
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 enab
[
https://issues.apache.org/jira/browse/STORM-822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15220469#comment-15220469
]
ASF GitHub Bot commented on STORM-822:
--
Github user asfgit closed the pull request at:
Github user revans2 commented on the pull request:
https://github.com/apache/storm/pull/1131#issuecomment-204081001
@hmcl I merged this into master, but when I tried to backport it to 1.x
there was a merge conflict. It was very minor, pom.xml needed a version
update, and remove the s
[
https://issues.apache.org/jira/browse/STORM-822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15220473#comment-15220473
]
ASF GitHub Bot commented on STORM-822:
--
Github user revans2 commented on the pull requ
Github user revans2 commented on the pull request:
https://github.com/apache/storm/pull/1257#issuecomment-204081963
Still +1
---
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
enabl
[
https://issues.apache.org/jira/browse/STORM-1279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15220474#comment-15220474
]
ASF GitHub Bot commented on STORM-1279:
---
Github user revans2 commented on the pull r
[
https://issues.apache.org/jira/browse/STORM-822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Joseph Evans updated STORM-822:
--
Fix Version/s: 2.0.0
> As a storm developer I’d like to use the new kafka consumer API (0
Robert Joseph Evans created STORM-1672:
--
Summary: Stats not get class cast exception
Key: STORM-1672
URL: https://issues.apache.org/jira/browse/STORM-1672
Project: Apache Storm
Issue Typ
Github user asfgit closed the pull request at:
https://github.com/apache/storm/pull/1273
---
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 enab
[
https://issues.apache.org/jira/browse/STORM-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15220523#comment-15220523
]
ASF GitHub Bot commented on STORM-1649:
---
Github user asfgit closed the pull request
Github user revans2 commented on the pull request:
https://github.com/apache/storm/pull/1257#issuecomment-204088810
I just ran into another bug
https://issues.apache.org/jira/browse/STORM-1672 that is preventing me from
manually testing some of the changes for the supervisor. I will
[
https://issues.apache.org/jira/browse/STORM-1279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15220525#comment-15220525
]
ASF GitHub Bot commented on STORM-1279:
---
Github user revans2 commented on the pull r
Github user knusbaum commented on the pull request:
https://github.com/apache/storm/pull/1273#issuecomment-204093716
@satishd @ptgoetz
Fine, but I think we need to stop putting stuff into 1.x real soon. This is
not a bug fix, it's an optimization. Continuing to add stuff to 1.x is
[
https://issues.apache.org/jira/browse/STORM-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15220548#comment-15220548
]
ASF GitHub Bot commented on STORM-1649:
---
Github user knusbaum commented on the pull
Github user asfgit closed the pull request at:
https://github.com/apache/storm/pull/1249
---
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 enab
[
https://issues.apache.org/jira/browse/STORM-1271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15220571#comment-15220571
]
ASF GitHub Bot commented on STORM-1271:
---
Github user asfgit closed the pull request
Github user roshannaik commented on the pull request:
https://github.com/apache/storm/pull/1217#issuecomment-204101205
1. I spent sometime trying to see if the tooltip can show up faster. But
there is a catch-22 there. The Bootstrap based tooltip mechanism allows it, but
the Bootstrap
[
https://issues.apache.org/jira/browse/STORM-1271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Joseph Evans resolved STORM-1271.
Resolution: Fixed
Fix Version/s: 2.0.0
Thanks [~abhishek.agarwal],
I merged
[
https://issues.apache.org/jira/browse/STORM-1632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15220573#comment-15220573
]
ASF GitHub Bot commented on STORM-1632:
---
Github user roshannaik commented on the pul
[
https://issues.apache.org/jira/browse/STORM-1229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
P. Taylor Goetz updated STORM-1229:
---
Removed from 1.0 Release epic
> port backtype.storm.metric.testing to java
>
Github user ptgoetz commented on the pull request:
https://github.com/apache/storm/pull/1273#issuecomment-204110947
@satishd I need to revert the merge because of compilation issues.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
[
https://issues.apache.org/jira/browse/STORM-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15220611#comment-15220611
]
ASF GitHub Bot commented on STORM-1649:
---
Github user ptgoetz commented on the pull r
GitHub user revans2 opened a pull request:
https://github.com/apache/storm/pull/1286
STORM-1672: Stats getting class cast exception
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/revans2/incubator-storm STORM-1672
Alternatively
[
https://issues.apache.org/jira/browse/STORM-1672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15220642#comment-15220642
]
ASF GitHub Bot commented on STORM-1672:
---
GitHub user revans2 opened a pull request:
Github user revans2 commented on the pull request:
https://github.com/apache/storm/pull/1262#issuecomment-204124801
+1 looks good to me.
---
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 f
Unless there are any objections, I intend to cut a release candidate once
STORM-1632, STORM-1668, and STORM-1669 have been merged (pull requests are
still in the 24 hr. review window).
If you have any concerns, please let me know.
-Taylor
> On Mar 30, 2016, at 4:59 PM, P. Taylor Goetz wrote:
[
https://issues.apache.org/jira/browse/STORM-515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15220658#comment-15220658
]
ASF GitHub Bot commented on STORM-515:
--
Github user revans2 commented on the pull requ
Github user ptgoetz commented on the pull request:
https://github.com/apache/storm/pull/1273#issuecomment-204126364
Reverted in master. @satishd can you take a look and re-open the pull
request with a fix.
Unfortunately this likely won't make the cutoff for the 1.0 release, bu
[
https://issues.apache.org/jira/browse/STORM-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15220662#comment-15220662
]
ASF GitHub Bot commented on STORM-1649:
---
Github user ptgoetz commented on the pull r
Github user kishorvpatil commented on the pull request:
https://github.com/apache/storm/pull/1286#issuecomment-204127228
LGTM. +1
---
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
[
https://issues.apache.org/jira/browse/STORM-1672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15220663#comment-15220663
]
ASF GitHub Bot commented on STORM-1672:
---
Github user kishorvpatil commented on the p
Github user knusbaum commented on the pull request:
https://github.com/apache/storm/pull/1286#issuecomment-204127745
+1
---
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 an
[
https://issues.apache.org/jira/browse/STORM-1672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15220664#comment-15220664
]
ASF GitHub Bot commented on STORM-1672:
---
Github user knusbaum commented on the pull
Github user knusbaum commented on a diff in the pull request:
https://github.com/apache/storm/pull/1262#discussion_r58131243
--- Diff:
examples/storm-starter/src/clj/org/apache/storm/starter/clj/bolts.clj ---
@@ -0,0 +1,75 @@
+;; Licensed to the Apache Software Foundation (ASF)
[
https://issues.apache.org/jira/browse/STORM-515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15220702#comment-15220702
]
ASF GitHub Bot commented on STORM-515:
--
Github user knusbaum commented on a diff in th
Github user knusbaum commented on a diff in the pull request:
https://github.com/apache/storm/pull/1262#discussion_r58132657
--- Diff:
examples/storm-starter/test/clj/org/apache/storm/starter/clj/bolts_test.clj ---
@@ -0,0 +1,115 @@
+;; Licensed to the Apache Software Foundatio
[
https://issues.apache.org/jira/browse/STORM-515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15220712#comment-15220712
]
ASF GitHub Bot commented on STORM-515:
--
Github user knusbaum commented on a diff in th
Github user knusbaum commented on the pull request:
https://github.com/apache/storm/pull/1262#issuecomment-204148932
Looks good for the most part.
---
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 h
[
https://issues.apache.org/jira/browse/STORM-515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15220733#comment-15220733
]
ASF GitHub Bot commented on STORM-515:
--
Github user knusbaum commented on the pull req
Github user revans2 commented on a diff in the pull request:
https://github.com/apache/storm/pull/1257#discussion_r58137861
--- Diff:
storm-core/src/jvm/org/apache/storm/daemon/supervisor/timer/RunProfilerActions.java
---
@@ -0,0 +1,214 @@
+/**
+ * Licensed to the Apache S
[
https://issues.apache.org/jira/browse/STORM-1279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15220769#comment-15220769
]
ASF GitHub Bot commented on STORM-1279:
---
Github user revans2 commented on a diff in
Github user revans2 commented on a diff in the pull request:
https://github.com/apache/storm/pull/1257#discussion_r58140035
--- Diff:
storm-core/src/jvm/org/apache/storm/daemon/supervisor/timer/RunProfilerActions.java
---
@@ -0,0 +1,214 @@
+/**
+ * Licensed to the Apache S
[
https://issues.apache.org/jira/browse/STORM-1279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15220803#comment-15220803
]
ASF GitHub Bot commented on STORM-1279:
---
Github user revans2 commented on a diff in
Github user revans2 commented on a diff in the pull request:
https://github.com/apache/storm/pull/1257#discussion_r58142341
--- Diff:
storm-core/src/jvm/org/apache/storm/daemon/supervisor/timer/RunProfilerActions.java
---
@@ -0,0 +1,214 @@
+/**
+ * Licensed to the Apache S
[
https://issues.apache.org/jira/browse/STORM-1279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15220831#comment-15220831
]
ASF GitHub Bot commented on STORM-1279:
---
Github user revans2 commented on a diff in
[
https://issues.apache.org/jira/browse/STORM-1279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15220842#comment-15220842
]
ASF GitHub Bot commented on STORM-1279:
---
Github user revans2 commented on the pull r
Github user revans2 commented on the pull request:
https://github.com/apache/storm/pull/1257#issuecomment-204167455
Found a few more bugs with manual testing. I would like to do some more
with other profiling options that are not on by default but this should fix the
default jstack/h
GitHub user moesol opened a pull request:
https://github.com/apache/storm/pull/1287
Addresses network flood from KafkaSpout to kafka server.
* Allows minBytes in fetch request to be configured
from KafkaConfig.fetchMinBytes.
* Defaults new configuration KafkaConfig.fetchMin
Github user HeartSaVioR commented on the pull request:
https://github.com/apache/storm/pull/1282#issuecomment-204179169
+1
---
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
[
https://issues.apache.org/jira/browse/STORM-1668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15220882#comment-15220882
]
ASF GitHub Bot commented on STORM-1668:
---
Github user HeartSaVioR commented on the pu
[
https://issues.apache.org/jira/browse/STORM-1668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15220883#comment-15220883
]
ASF GitHub Bot commented on STORM-1668:
---
Github user HeartSaVioR commented on the pu
Github user HeartSaVioR commented on the pull request:
https://github.com/apache/storm/pull/1281#issuecomment-204179234
+1
---
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
Github user HeartSaVioR commented on the pull request:
https://github.com/apache/storm/pull/1280#issuecomment-204181100
+1 Great finding.
---
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
1 - 100 of 184 matches
Mail list logo