[jira] [Commented] (STORM-805) Supervisor crashes with 'org.apache.commons.io.FileExistsException: Destination already exists' error

[ https://issues.apache.org/jira/browse/STORM-805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14565740#comment-14565740 ] Jungtaek Lim commented on STORM-805: I can see that this commit adds missing part to 0.

Re: [VOTE] Release Apache Storm 0.9.5

- test passed : OK - extract source tar : OK - build via "mvn clean install” : OK - verify STORM-745 : OK - install binary version of storm 0.9.5 to Windows 7 : OK - use apache-storm-0.9.5.zip - run dev-zookeeper, nimbus, supervisor with default setting via

[jira] [Commented] (STORM-821) storm-jdbc create a connection provider interface to decouple from hikariCP being the only connection pool implementation that can be used.

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

[GitHub] storm pull request: STORM-821: Adding connection provider interfac...

Github user ptgoetz commented on the pull request: https://github.com/apache/storm/pull/556#issuecomment-106914408 Thanks @Parth-Brahmbhatt. I merged this into master and 0.10.x. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as

[jira] [Commented] (STORM-821) storm-jdbc create a connection provider interface to decouple from hikariCP being the only connection pool implementation that can be used.

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

[GitHub] storm pull request: STORM-821: Adding connection provider interfac...

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

[jira] [Commented] (STORM-737) Workers may try to send to closed connections

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

[GitHub] storm pull request: [STORM-737] Check task->node+port with read lo...

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

[jira] [Commented] (STORM-817) Kafka Wildcard Topic Support

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

[GitHub] storm pull request: STORM-817: Support for Kafka Wildcard topics

Github user sumitchawla commented on the pull request: https://github.com/apache/storm/pull/561#issuecomment-106882647 Can anybody please review this PR and provide feedback or comments? --- If your project is set up for it, you can reply to this email and have your reply appear on G

[jira] [Issue Comment Deleted] (STORM-817) Kafka Wildcard Topic Support

[ https://issues.apache.org/jira/browse/STORM-817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Chawla updated STORM-817: --- Comment: was deleted (was: Thanks [~kabhwan] .. Any idea what is typical time for this to get merged

[jira] [Commented] (STORM-167) proposal for storm topology online update

[ https://issues.apache.org/jira/browse/STORM-167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14565030#comment-14565030 ] Parth Brahmbhatt commented on STORM-167: Hey , I haven't had time to look into this

[VOTE] Release Apache Storm 0.9.5

This is a call to vote on releasing Apache Storm 0.9.5. 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=c9c47b36071c02488ee1e75eb3851e58191b7534 The tag/commit to be voted upon is v0.9.5: https://git-wip-us.apache.org/repo

[jira] [Created] (STORM-840) My supervisor crashes when I kill a topology

Damien DESMARETS created STORM-840: -- Summary: My supervisor crashes when I kill a topology Key: STORM-840 URL: https://issues.apache.org/jira/browse/STORM-840 Project: Apache Storm Issue Typ

[jira] [Commented] (STORM-805) Supervisor crashes with 'org.apache.commons.io.FileExistsException: Destination already exists' error

[ https://issues.apache.org/jira/browse/STORM-805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14564886#comment-14564886 ] P. Taylor Goetz commented on STORM-805: --- [~kabhwan] I was able to get the missing pie

[jira] [Commented] (STORM-790) Log "task id is null" instead of let worker died (NPE in consumeBatchToCursor)

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

[GitHub] storm pull request: STORM-790 Log "task is null" instead of let wo...

Github user ptgoetz commented on the pull request: https://github.com/apache/storm/pull/527#issuecomment-106824785 @HeartSaVioR This patch has been applied to 0.9.x and 0.10.x. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as we

Re: KafkaBolt with new Java Kafka Producer

We do have a team member working on that right now. I'm not totally sure of the time frame on getting it out to open source, but I would suspect a week or two more at the most.  - Bobby On Friday, May 29, 2015 7:56 AM, Ryan Persaud wrote: Hello Raghavendra, Thanks for your repl

[GitHub] storm pull request: [STORM-839] Deadlock hazard in backtype.storm....

Github user eshioji commented on the pull request: https://github.com/apache/storm/pull/566#issuecomment-106800904 Just as a heads up, I'm seeing STORM-763 as well (300 ERROR messages per second per machine) in our cluster. My initial gut feeling is that maybe reconnect isn't getting

[jira] [Commented] (STORM-839) Deadlock hazard in backtype.storm.messaging.netty.Client

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

[jira] [Commented] (STORM-839) Deadlock hazard in backtype.storm.messaging.netty.Client

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

[GitHub] storm pull request: [STORM-839] Deadlock hazard in backtype.storm....

Github user miguno commented on the pull request: https://github.com/apache/storm/pull/566#issuecomment-106795826 > My reasoning is as follows: > > * One has three option to deal with Netty's buffer filling up: > 1. Discard incoming new messages > 2. Block clien

Re: KafkaBolt with new Java Kafka Producer

Hello Raghavendra, Thanks for your reply and code sample. I see that you are using the List version of the send function in kafka.javaapi.producer to implement batching. My Scala is not so good, but it looks like the List version of send() is just iterating through the list and calling the same

[jira] [Commented] (STORM-839) Deadlock hazard in backtype.storm.messaging.netty.Client

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

[GitHub] storm pull request: [STORM-839] Deadlock hazard in backtype.storm....

Github user eshioji commented on the pull request: https://github.com/apache/storm/pull/566#issuecomment-106792295 @Hailei I see. > Block client thread until there is space (back pressure) is better.It can snap out of OOM. Agreed, but my understanding is that this ne

[GitHub] storm pull request: [STORM-839] Deadlock hazard in backtype.storm....

Github user Hailei commented on the pull request: https://github.com/apache/storm/pull/566#issuecomment-106778432 >we can remove the background flushing task and related synchronization altogether, removing the source of deadlock. We'd simply write and buffer onto the unbounded buffer

[jira] [Commented] (STORM-839) Deadlock hazard in backtype.storm.messaging.netty.Client

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

[jira] [Commented] (STORM-839) Deadlock hazard in backtype.storm.messaging.netty.Client

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

[GitHub] storm pull request: [STORM-839] Deadlock hazard in backtype.storm....

Github user eshioji commented on the pull request: https://github.com/apache/storm/pull/566#issuecomment-106768270 @Hailei Thanks for the comment. Could you review my reasoning in the [PR comment above](https://github.com/apache/storm/pull/566#issue-82369808)? --- If your project i

[GitHub] storm pull request: [STORM-839] Deadlock hazard in backtype.storm....

GitHub user eshioji opened a pull request: https://github.com/apache/storm/pull/566 [STORM-839] Deadlock hazard in backtype.storm.messaging.netty.Client (I accidentally did a PR against master with the same content, please ignore that one) This fixes the reported deadlock b

[jira] [Commented] (STORM-839) Deadlock hazard in backtype.storm.messaging.netty.Client

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

[GitHub] storm pull request: STORM-839

Github user eshioji closed the pull request at: https://github.com/apache/storm/pull/565 --- 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] [Commented] (STORM-839) Deadlock hazard in backtype.storm.messaging.netty.Client

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

[GitHub] storm pull request: STORM-839

Github user eshioji commented on the pull request: https://github.com/apache/storm/pull/565#issuecomment-106765335 Argh sorry I should have opened this against Storm v0.9.4, I worked off v0.9.4 tag. --- If your project is set up for it, you can reply to this email and have your reply

[jira] [Commented] (STORM-839) Deadlock hazard in backtype.storm.messaging.netty.Client

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

[jira] [Commented] (STORM-839) Deadlock hazard in backtype.storm.messaging.netty.Client

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

[GitHub] storm pull request: STORM-839

GitHub user eshioji opened a pull request: https://github.com/apache/storm/pull/565 STORM-839 This fixes the reported deadlock between `disruptor-worker-transfer-queue` thread and `client-worker` thread, which seem to have been introduced by STORM-329. After reviewing the

[jira] [Commented] (STORM-167) proposal for storm topology online update

[ https://issues.apache.org/jira/browse/STORM-167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14564443#comment-14564443 ] Roland Jungnickel commented on STORM-167: - Hi [~parth.brahmbhatt], Just wondering

[jira] [Commented] (STORM-790) Log "task id is null" instead of let worker died (NPE in consumeBatchToCursor)

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

[GitHub] storm pull request: STORM-790 Log "task is null" instead of let wo...

Github user HeartSaVioR commented on the pull request: https://github.com/apache/storm/pull/527#issuecomment-106741650 It seems to be merged to master well. Thanks for reviewing and merging! Btw, it is an active bug, so IMO it should be applied to 0.9.5 and 0.10.0, too. Di

[jira] [Commented] (STORM-805) Supervisor crashes with 'org.apache.commons.io.FileExistsException: Destination already exists' error

[ https://issues.apache.org/jira/browse/STORM-805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14564390#comment-14564390 ] Jungtaek Lim commented on STORM-805: [~harsha_ch] [~ptgoetz] There was an accident abo