[jira] [Commented] (STORM-1733) Logs from bin/storm are lost because stdout and stderr are not flushed

[ https://issues.apache.org/jira/browse/STORM-1733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15259658#comment-15259658 ] ASF GitHub Bot commented on STORM-1733: --- Github user dsKarthick commented on the pul

[GitHub] storm pull request: STORM-1733 Flush stdout and stderr before call...

Github user dsKarthick commented on the pull request: https://github.com/apache/storm/pull/1360#issuecomment-214988139 > Can you update the PR title to include the JIRA, i.e prefix it with [STORM-1733] Done. --- If your project is set up for it, you can reply to this email and ha

[GitHub] storm pull request: update the java version.

GitHub user ziyunhx opened a pull request: https://github.com/apache/storm/pull/1368 update the java version. Storm drops supporting JDK 1.6 in Apache Storm 0.10.0 and above. You can merge this pull request into a Git repository by running: $ git pull https://github.com/ziyunhx

[GitHub] storm pull request: update the java version.

GitHub user ziyunhx opened a pull request: https://github.com/apache/storm/pull/1367 update the java version. Storm drops supporting JDK 1.6 in Apache Storm 0.10.0 and above. You can merge this pull request into a Git repository by running: $ git pull https://github.com/ziyunhx

[GitHub] storm pull request: update the java version.

GitHub user ziyunhx opened a pull request: https://github.com/apache/storm/pull/1366 update the java version. Storm drops supporting JDK 1.6 in Apache Storm 0.10.0 and above. You can merge this pull request into a Git repository by running: $ git pull https://github.com/ziyunhx

[GitHub] storm pull request: remove the new features of JAVA 1.7.

Github user ziyunhx closed the pull request at: https://github.com/apache/storm/pull/1365 --- 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 ena

[GitHub] storm pull request: remove the new features of JAVA 1.7.

Github user ziyunhx commented on the pull request: https://github.com/apache/storm/pull/1365#issuecomment-214973467 okay --- 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 a

[GitHub] storm pull request: remove the new features of JAVA 1.7.

Github user HeartSaVioR commented on the pull request: https://github.com/apache/storm/pull/1365#issuecomment-214969524 I guess we missed updating the doc. Could you please file an issue, or craft pull request fixing on the doc directly? It should be applied to master, 1.x-branch, 0.1

[GitHub] storm pull request: remove the new features of JAVA 1.7.

Github user ziyunhx commented on the pull request: https://github.com/apache/storm/pull/1365#issuecomment-214969181 But the document of 2.0.0-SNAPSHOT is still support JAVA 6. http://storm.apache.org/releases/2.0.0-SNAPSHOT/Setting-up-a-Storm-cluster.html --- If your project is s

[GitHub] storm pull request: STORM-1731 (1.x) Avoid looking up debug / back...

Github user hustfxj commented on the pull request: https://github.com/apache/storm/pull/1362#issuecomment-214968261 it's amazing, +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 featu

[jira] [Commented] (STORM-1731) Avoid looking up debug / backpressure enable flags within critical path

[ https://issues.apache.org/jira/browse/STORM-1731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15259531#comment-15259531 ] ASF GitHub Bot commented on STORM-1731: --- Github user hustfxj commented on the pull r

[GitHub] storm pull request: Flush stdout and stderr before calling "os.exe...

Github user arunmahadevan commented on the pull request: https://github.com/apache/storm/pull/1360#issuecomment-214962026 > Not sure why you say this. In my case for example, I using runit to start storm components like nimbus, ui, etc and the problem is applicable to all the componen

[jira] [Commented] (STORM-1733) Logs from bin/storm are lost because stdout and stderr are not flushed

[ https://issues.apache.org/jira/browse/STORM-1733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15259484#comment-15259484 ] ASF GitHub Bot commented on STORM-1733: --- Github user arunmahadevan commented on the

[GitHub] storm pull request: remove the new features of JAVA 1.7.

Github user HeartSaVioR commented on the pull request: https://github.com/apache/storm/pull/1365#issuecomment-214960872 Sorry but it's intended. Storm drops supporting JDK 1.6 in Apache Storm 0.10.0 and above. --- If your project is set up for it, you can reply to this email and have

[GitHub] storm pull request: remove the new features of JAVA 1.7.

GitHub user ziyunhx opened a pull request: https://github.com/apache/storm/pull/1365 remove the new features of JAVA 1.7. ThreadLocalRandom,System.lineSeparator() and Integer.compare are JAVA 1.7 feature. Change these to support JAVA 1.6. You can merge this pull request into a Git

[jira] [Commented] (STORM-1731) Avoid looking up debug / backpressure enable flags within critical path

[ https://issues.apache.org/jira/browse/STORM-1731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15259472#comment-15259472 ] ASF GitHub Bot commented on STORM-1731: --- Github user unsleepy22 commented on the pul

[GitHub] storm pull request: STORM-1731 (1.x) Avoid looking up debug / back...

Github user unsleepy22 commented on the pull request: https://github.com/apache/storm/pull/1362#issuecomment-214960183 +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

Re: [VOTE] Release Apache Storm 0.10.1 (rc1)

Same as 1.0.1 release. I would like to get those two patches in for 0.10.1 release as well. Thanks, Harsha On Tue, Apr 26, 2016, at 05:27 PM, Jungtaek Lim wrote: > Same on 1.0.1 RC1, but only STORM-1731 > is affected to 0.10.1. > > Below is the r

[jira] [Commented] (STORM-1731) Avoid looking up debug / backpressure enable flags within critical path

[ https://issues.apache.org/jira/browse/STORM-1731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15259452#comment-15259452 ] ASF GitHub Bot commented on STORM-1731: --- Github user harshach commented on the pull

[jira] [Commented] (STORM-1731) Avoid looking up debug / backpressure enable flags within critical path

[ https://issues.apache.org/jira/browse/STORM-1731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15259453#comment-15259453 ] ASF GitHub Bot commented on STORM-1731: --- Github user harshach commented on the pull

[GitHub] storm pull request: STORM-1731 (1.x) Avoid looking up debug / back...

Github user harshach commented on the pull request: https://github.com/apache/storm/pull/1362#issuecomment-214956338 +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 a

[GitHub] storm pull request: STORM-1731 (0.10.x) Avoid looking up debug / b...

Github user harshach commented on the pull request: https://github.com/apache/storm/pull/1364#issuecomment-214956239 +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

答复: [VOTE] Release Apache Storm 1.0.1

Thank you for Jungtaek, I also hope we can do another candidate with these fixed in. -邮件原件- 发件人: Harsha [mailto:st...@harsha.io] 发送时间: 2016年4月27日 10:20 收件人: dev@storm.apache.org 主题: Re: [VOTE] Release Apache Storm 1.0.1 I am +1 on doing another release candidate with these fixes in. Nic

Re: [VOTE] Release Apache Storm 1.0.1

I agree, and the testing I've done on aws seems to confirm this. If there aren't any objections, I'll cancel the vote and cut a new release. Also a reminder that there is an open vote for 0.10.1. Community members (especially committers) should weigh in on that thread as well. -Taylor > On Apr

Re: [VOTE] Release Apache Storm 1.0.1

I am +1 on doing another release candidate with these fixes in. Nice work Jungtaek. Thanks, Harsha On Tue, Apr 26, 2016, at 05:23 PM, Jungtaek Lim wrote: > I've observed the points of performance hit (STORM-1729 > , STORM-1731 >

[jira] [Commented] (STORM-1731) Avoid looking up debug / backpressure enable flags within critical path

[ https://issues.apache.org/jira/browse/STORM-1731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15259402#comment-15259402 ] ASF GitHub Bot commented on STORM-1731: --- Github user roshannaik commented on the pul

[GitHub] storm pull request: STORM-1731 (1.x) Avoid looking up debug / back...

Github user roshannaik commented on the pull request: https://github.com/apache/storm/pull/1362#issuecomment-214948085 Ran the provided topology and a couple minor variations with this cumulative fix. Was able to measure a 50% boost in throughput (ACKs/sec) on the 1.x-branc

[jira] [Commented] (STORM-1358) Porting JStorm multi-thread mode of spout to Storm

[ https://issues.apache.org/jira/browse/STORM-1358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15259399#comment-15259399 ] Basti Liu commented on STORM-1358: -- If you have time, I think you can start this porting

[jira] [Commented] (STORM-1731) Avoid looking up debug / backpressure enable flags within critical path

[ https://issues.apache.org/jira/browse/STORM-1731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15259294#comment-15259294 ] ASF GitHub Bot commented on STORM-1731: --- GitHub user HeartSaVioR opened a pull reque

[GitHub] storm pull request: STORM-1731 (0.10.x) Avoid looking up debug / b...

GitHub user HeartSaVioR opened a pull request: https://github.com/apache/storm/pull/1364 STORM-1731 (0.10.x) Avoid looking up debug / backpressure enable flags within critical path * preload the value of flags and use that value * topology.debug Pull request for 1.x v

Re: [VOTE] Release Apache Storm 0.10.1 (rc1)

Same on 1.0.1 RC1, but only STORM-1731 is affected to 0.10.1. Below is the repetitive message from 1.0.1 RC1 for tracking archive later easier. I've observed the points of performance hit (STORM-1729

Re: [VOTE] Release Apache Storm 1.0.1

I've observed the points of performance hit (STORM-1729 , STORM-1731 ), and it seems huge. Since patches are small and straightforward, I would love to include this as 1.0.1 so that users maintainin

[jira] [Commented] (STORM-1731) Avoid looking up debug / backpressure enable flags within critical path

[ https://issues.apache.org/jira/browse/STORM-1731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15259242#comment-15259242 ] ASF GitHub Bot commented on STORM-1731: --- Github user HeartSaVioR commented on the pu

[GitHub] storm pull request: STORM-1731 Avoid looking up debug / backpressu...

Github user HeartSaVioR commented on the pull request: https://github.com/apache/storm/pull/1362#issuecomment-214926340 New observation here: Most of lines came from authentication feature introduced at 0.10.0. In other word, this performance hit is introduced at Apache Storm 0.10

[jira] [Commented] (STORM-1729) Get rid of reflections while recording stats

[ https://issues.apache.org/jira/browse/STORM-1729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15259232#comment-15259232 ] ASF GitHub Bot commented on STORM-1729: --- Github user HeartSaVioR commented on the pu

[GitHub] storm pull request: STORM-1729 Get rid of reflections while record...

Github user HeartSaVioR commented on the pull request: https://github.com/apache/storm/pull/1361#issuecomment-214925566 Please refer #816. I'm confused completely why this happens cause those lines are introduced at 16c33efac39edea7e2d77df319d0ee3fd407383a which fixes the reflection i

[VOTE] Release Apache Storm 0.10.1 (rc1)

***Please note the version! There is another VOTE open that could easily be confused with this one.*** This is a call to vote on releasing Apache Storm 0.10.1 (rc1) Full list of changes in this release: https://git-wip-us.apache.org/repos/asf?p=storm.git;a=blob_plain;f=CHANGELOG.md;hb=f0d3eae73

Re: [VOTE] Release Apache Storm 1.0.1

Two of the links were wrong, please use the following links: The source archive being voted upon can be found here: https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.0.1-rc1/apache-storm-1.0.1-src.tar.gz Other release files, signatures and digests can be found here: https://dist.apach

[jira] [Commented] (STORM-1733) Logs from bin/storm are lost because stdout and stderr are not flushed

[ https://issues.apache.org/jira/browse/STORM-1733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15258744#comment-15258744 ] ASF GitHub Bot commented on STORM-1733: --- Github user dsKarthick commented on the pul

[GitHub] storm pull request: Flush stdout and stderr before calling "os.exe...

Github user dsKarthick closed the pull request at: https://github.com/apache/storm/pull/1360 --- 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

[GitHub] storm pull request: Flush stdout and stderr before calling "os.exe...

Github user dsKarthick commented on the pull request: https://github.com/apache/storm/pull/1360#issuecomment-214857945 @arunmahadevan > Can you also raise a jira Sure. Raised [https://issues.apache.org/jira/browse/STORM-1733](STORM-1733) > When stdout is a terminal its

[GitHub] storm pull request: Flush stdout and stderr before calling "os.exe...

GitHub user dsKarthick reopened a pull request: https://github.com/apache/storm/pull/1360 Flush stdout and stderr before calling "os.execvp" to prevent log loss. bin/storm.py emits the following crucial information that is lost because we don't flush the stdout before exec. ```

[jira] [Updated] (STORM-1733) Logs from bin/storm are lost because stdout and stderr are not flushed

[ https://issues.apache.org/jira/browse/STORM-1733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthick Duraisamy Soundararaj updated STORM-1733: -- Description: bin/storm.py emits the following crucial informatio

[jira] [Updated] (STORM-1733) Logs from bin/storm are lost because stdout and stderr are not flushed

[ https://issues.apache.org/jira/browse/STORM-1733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthick Duraisamy Soundararaj updated STORM-1733: -- Description: bin/storm.py emits the following crucial informatio

[jira] [Updated] (STORM-1733) Logs from bin/storm are lost because stdout and stderr are not flushed

[ https://issues.apache.org/jira/browse/STORM-1733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthick Duraisamy Soundararaj updated STORM-1733: -- Description: bin/storm.py emits the following crucial informatio

[jira] [Created] (STORM-1733) Logs from bin/storm are lost because stdout and stderr are not flushed

Karthick Duraisamy Soundararaj created STORM-1733: - Summary: Logs from bin/storm are lost because stdout and stderr are not flushed Key: STORM-1733 URL: https://issues.apache.org/jira/browse/STORM-

[jira] [Commented] (STORM-1729) Get rid of reflections while recording stats

[ https://issues.apache.org/jira/browse/STORM-1729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15258490#comment-15258490 ] ASF GitHub Bot commented on STORM-1729: --- Github user HeartSaVioR commented on the pu

[GitHub] storm pull request: STORM-1729 Get rid of reflections while record...

Github user HeartSaVioR commented on the pull request: https://github.com/apache/storm/pull/1361#issuecomment-214816453 @unsleepy22 Let's move to #1362. I'll address the performance tests there. --- If your project is set up for it, you can reply to this email and have your reply appe

[jira] [Commented] (STORM-1731) Avoid looking up debug / backpressure enable flags within critical path

[ https://issues.apache.org/jira/browse/STORM-1731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15258485#comment-15258485 ] ASF GitHub Bot commented on STORM-1731: --- Github user HeartSaVioR commented on the pu

[GitHub] storm pull request: STORM-1731 Avoid looking up debug / backpressu...

Github user HeartSaVioR commented on the pull request: https://github.com/apache/storm/pull/1362#issuecomment-214815773 Attaching full numbers, [throughput-vs-latency-tests-20160427.txt](https://github.com/apache/storm/files/237120/throughput-vs-latency-tests-20160427.txt) --- I

[jira] [Commented] (STORM-1731) Avoid looking up debug / backpressure enable flags within critical path

[ https://issues.apache.org/jira/browse/STORM-1731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15258486#comment-15258486 ] ASF GitHub Bot commented on STORM-1731: --- Github user HeartSaVioR commented on the pu

[GitHub] storm pull request: STORM-1731 Avoid looking up debug / backpressu...

Github user HeartSaVioR commented on the pull request: https://github.com/apache/storm/pull/1362#issuecomment-214815353 I found at throughput 22,000 current 1.x-branch doesn't keep up the SLA at some moment. ``` uptime: 181 acked: 678,400 acked/sec: 22,613.33 failed:

[jira] [Closed] (STORM-638) UI should show up process-id of the Worker to which an Executor is assigned

[ https://issues.apache.org/jira/browse/STORM-638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] P. Taylor Goetz closed STORM-638. - Resolution: Won't Fix > UI should show up process-id of the Worker to which an Executor is assigne

[jira] [Resolved] (STORM-1645) nimbus.thrift.port command line argument leads to java.lang.ClassCastException: java.lang.Long cannot be cast to java.lang.Integer

[ https://issues.apache.org/jira/browse/STORM-1645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] P. Taylor Goetz resolved STORM-1645. Resolution: Fixed Merged to 0.10.x-branch. > nimbus.thrift.port command line argument leads

[jira] [Commented] (STORM-1358) Porting JStorm multi-thread mode of spout to Storm

[ https://issues.apache.org/jira/browse/STORM-1358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15258414#comment-15258414 ] Nisarg Shah commented on STORM-1358: Oh I see it now. So should I wait for Phase 1 to

[jira] [Commented] (STORM-1645) nimbus.thrift.port command line argument leads to java.lang.ClassCastException: java.lang.Long cannot be cast to java.lang.Integer

[ https://issues.apache.org/jira/browse/STORM-1645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15258413#comment-15258413 ] ASF GitHub Bot commented on STORM-1645: --- Github user asfgit closed the pull request

[GitHub] storm pull request: STORM-1645: convert nimbus.thrift.port to int ...

Github user asfgit closed the pull request at: https://github.com/apache/storm/pull/1301 --- 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

[jira] [Updated] (STORM-1732) Resources are deleted when worker dies

[ https://issues.apache.org/jira/browse/STORM-1732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] gareth smith updated STORM-1732: Description: *Lets say a worker has been started by the supervisor* 2016-04-26 16:11:48.716 [o.a.s.

[jira] [Updated] (STORM-1732) Resources are deleted when worker dies

[ https://issues.apache.org/jira/browse/STORM-1732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] gareth smith updated STORM-1732: Description: Lets say a worker has been started by the supervisor 2016-04-26 16:11:48.716 [o.a.s.d.

[VOTE] Release Apache Storm 1.0.1

This is a call to vote on releasing Apache Storm 1.0.1 (rc1) Full list of changes in this release: https://git-wip-us.apache.org/repos/asf?p=storm.git;a=blob_plain;f=CHANGELOG.md;hb=7520b9ae13c4a4fcd823e2d636e9b2cc1cbb7e6f The tag/commit to be voted upon is v1.0.1: https://git-wip-us.apache.org

[jira] [Created] (STORM-1732) Resources are deleted when worker dies

gareth smith created STORM-1732: --- Summary: Resources are deleted when worker dies Key: STORM-1732 URL: https://issues.apache.org/jira/browse/STORM-1732 Project: Apache Storm Issue Type: Bug

[jira] [Commented] (STORM-1731) Avoid looking up debug / backpressure enable flags within critical path

[ https://issues.apache.org/jira/browse/STORM-1731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15258267#comment-15258267 ] ASF GitHub Bot commented on STORM-1731: --- Github user HeartSaVioR commented on the pu

[GitHub] storm pull request: STORM-1731 Avoid looking up debug / backpressu...

Github user HeartSaVioR commented on the pull request: https://github.com/apache/storm/pull/1362#issuecomment-214781229 I've done performance comparison test with ThroughputVsLatency with one machine. * disruptor batching size is set to default (100 / timeout 1ms) thr

[jira] [Commented] (STORM-1729) Get rid of reflections while recording stats

[ https://issues.apache.org/jira/browse/STORM-1729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15257972#comment-15257972 ] ASF GitHub Bot commented on STORM-1729: --- Github user HeartSaVioR commented on the pu

[GitHub] storm pull request: STORM-1729 Get rid of reflections while record...

Github user HeartSaVioR commented on the pull request: https://github.com/apache/storm/pull/1361#issuecomment-214720406 And also ThroughputVsLatency topology in storm-starter. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as wel

[jira] [Commented] (STORM-1729) Get rid of reflections while recording stats

[ https://issues.apache.org/jira/browse/STORM-1729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15257931#comment-15257931 ] ASF GitHub Bot commented on STORM-1729: --- Github user HeartSaVioR commented on the pu

[GitHub] storm pull request: STORM-1729 Get rid of reflections while record...

Github user HeartSaVioR commented on the pull request: https://github.com/apache/storm/pull/1361#issuecomment-214712176 @unsleepy22 Yeah, I really want to, but in order to do that we need a stable machines and benchmark tests. We can give it a try with https://github.com/yahoo

[jira] [Commented] (STORM-1729) Get rid of reflections while recording stats

[ https://issues.apache.org/jira/browse/STORM-1729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15257928#comment-15257928 ] ASF GitHub Bot commented on STORM-1729: --- Github user unsleepy22 commented on the pul

[GitHub] storm pull request: STORM-1729 Get rid of reflections while record...

Github user unsleepy22 commented on the pull request: https://github.com/apache/storm/pull/1361#issuecomment-214711443 +1 BTW. can we have more performance tests in more cases so that we can see the overall performance change? --- If your project is set up for it, you can reply t

[jira] [Updated] (STORM-1729) Get rid of reflections while recording stats

[ https://issues.apache.org/jira/browse/STORM-1729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim updated STORM-1729: Priority: Critical (was: Major) > Get rid of reflections while recording stats > --

Broken links on WebPage

Hi, I just openend an PR for improve the WebPage: https://github.com/apache/storm/pull/1363 The link to "Daemon Metrics/Monitoring" does not work for 2.0-SNAPSHOT. Furthermore, "Daemon Metrics/Monitoring" and "Window users guide" does not work for 1.0.0. I guess we should apply this PR to 1.0.0,

[GitHub] storm pull request: minor: improved documenation layout

GitHub user mjsax opened a pull request: https://github.com/apache/storm/pull/1363 minor: improved documenation layout You can merge this pull request into a Git repository by running: $ git pull https://github.com/mjsax/storm docFix Alternatively you can review and apply the

[jira] [Commented] (STORM-1731) Avoid looking up debug / backpressure enable flags within critical path

[ https://issues.apache.org/jira/browse/STORM-1731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15257892#comment-15257892 ] ASF GitHub Bot commented on STORM-1731: --- GitHub user HeartSaVioR opened a pull reque

[GitHub] storm pull request: STORM-1731 Avoid looking up debug / backpressu...

GitHub user HeartSaVioR opened a pull request: https://github.com/apache/storm/pull/1362 STORM-1731 Avoid looking up debug / backpressure enable flags within critical path This pull request is on top of STORM-1729 (#1361) to avoid merge conflicts. Even though we set topolog

[jira] [Created] (STORM-1731) Avoid looking up debug / backpressure enable flags within critical path

Jungtaek Lim created STORM-1731: --- Summary: Avoid looking up debug / backpressure enable flags within critical path Key: STORM-1731 URL: https://issues.apache.org/jira/browse/STORM-1731 Project: Apache S

[jira] [Updated] (STORM-1730) LocalCluster#shutdown() does not terminate all storm threads/thread pools.

[ https://issues.apache.org/jira/browse/STORM-1730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fergus Byrne updated STORM-1730: Attachment: storm-shutdown-issue.zip Gradle test case > LocalCluster#shutdown() does not terminate

[jira] [Updated] (STORM-1730) LocalCluster#shutdown() does not terminate all storm threads/thread pools.

[ https://issues.apache.org/jira/browse/STORM-1730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fergus Byrne updated STORM-1730: Attachment: Thread Pool '47' remaining..png > LocalCluster#shutdown() does not terminate all storm t

[jira] [Created] (STORM-1730) LocalCluster#shutdown() does not terminate all storm threads/thread pools.

Fergus Byrne created STORM-1730: --- Summary: LocalCluster#shutdown() does not terminate all storm threads/thread pools. Key: STORM-1730 URL: https://issues.apache.org/jira/browse/STORM-1730 Project: Apach