Re: Crashes when running storm 2.1 topologies on multiple workers

Ideally you want to use multiple instances of a bolt/spout over doing internal multithreading. if you must use internal threading, you will need to do your own synchronization as well. In general these distributed systems are designed to relieve users from doing their own MT and

Recordings of Storm 2.0 talks at the Bay Area Hadoop Meetup last week.

1- Raising the performance bar for stream processing with Apache Storm 2.0 - Roshan Naik, (Uber) Discussion of performance improvements as well as the new 2.0 architecture for messaging subsystem, threading model & back pressure.  https://www.youtube.com/watch?v=QsPzAtZXIk4 2- Apache S

Storm 2.0 talks at Bay Area Hadoop meetup

If you are in the San Francisco Bay Area, please join us at the Bay Area Hadoop meetup tomorrow (Oct 29th 2019) featuring these talks on  Storm 2.0 : 1 - Raising the performance bar for stream processing with Apache Storm 2.0 - Roshan Naik (Uber),   The effort to rearchitect Storm's core

Re: Steps for Updating Storm Website

://github.com/apache/storm/blob/master/DEVELOPER.md#contribute-documentation . Essentially, it comes down to updating the github: https://git-wip-us.apache.org/repos/asf?p=storm-site.git;a=summary -Kishor On Mon, Sep 30, 2019 at 6:34 PM Roshan Naik wrote: > Taylor,Could you please share the st

Steps for Updating Storm Website

Taylor,    Could you please share the steps for updating the Storm website?  -roshan

Re: Location for 2.0 blogs

to the release posts, or maybe we could add another button next to news for blog posts? Den søn. 22. sep. 2019 kl. 12.32 skrev Roshan Naik : > I see that we have never published any blogs previouslyanywhere on the > Apache Storm website.So wondering where would be a good location to p

Location for 2.0 blogs

I see that we have never published any blogs previouslyanywhere on the Apache Storm website.So wondering where would be a good location to publish the (overdue) 2.0 perf blog that I am close to completing. I guess that might dictate the format (html / wiki) the final version needs to be in.

Re: [ANNOUNCE] New Committer/PMC Member Aaron Gresch

Welcome Aaron, congratulations. On Saturday, August 10, 2019, 06:56:39 PM PDT, Kishorkumar Patil wrote: Congratulations Aaron! On Sat, Aug 10, 2019 at 8:14 PM Derek Dagit wrote: > Welcome, Aaron! > > On Sat, Aug 10, 2019 at 08:18:40AM -0500, Ethan Li wrote: > > > > Congratulations,

Re: [DISCUSS] Create a checklist for testing new Storm release

+1  that does look like a nice list.  On Thursday, August 1, 2019, 09:30:24 AM PDT, Ethan Li wrote: Right. I found this http://www.apache.org/dev/release-distribution.html#sigs-and-sums In the new release, we should

Re: [Discuss] ARM CI for Storm

Thanks for volunteering.  Sent from Yahoo Mail for iPhone On Wednesday, June 26, 2019, 7:08 PM, Yikun Jiang wrote: Yes, we will definitely help to fix ARM test failures in PRs, and the OpenLab CI will tell us which PR perhaps has ARM compatible problem, if it's an easy fix problem, I think

Re: [VOTE] Release Apache Storm 1.2.3 (rc2)

Friendly reminder on this one. Roshan Sent from Yahoo Mail for iPhone On Saturday, June 15, 2019, 9:15 AM, P. Taylor Goetz wrote: This vote is now closed and passes with 3 binding +1 votes and 1 non-binding +1 vote. I will release the artifacts and create a release announcement. -Taylor

Re: Storm 2.0 Maven Artifacts

Does this mean that the artifacts were not been pushed to the mvn repo ? Or do we just need to wait for the artifacts to show up there .. and if so how long ?  -roshan On Monday, June 3, 2019, 9:33:44 AM PDT, Stig Rohde Døssing wrote:  No, I think you are right. It doesn't look like

Re: [Discuss] New release managers

Yes, having the release process documented will help a great deal to let anyone to step in as release manager.  Roshan  Sent from Yahoo Mail for iPhone

Re: [VOTE] Release Apache Storm 1.2.3 (rc2)

+1- verified binary distribution- setup local cluster - ran some perf topos with two workers and acking enabled- basic checking of the UI -roshan On Saturday, May 11, 2019, 1:21:26 PM EDT, Alexandre Vermeerbergen wrote: Oh and I forgot to mention that all my tests are made using

Re: Storm 2.0 blogs ?

Taylor,    Somewhere in the release notes it would be good to mention the following: - Compatibility: 2.0 is backward compatible with 1.x, but they need to recompile the topo jars.  - Dependency changes: Like Alexandre, others are likely to discover the hard way that storm-core is something

Re: [RESULT] [VOTE] Release Apache Storm 2.0.0 RC7

Ooops... just missed it...  my +1 as well Just finished verifying the foll:- spun up local cluster with binary dist- checked single a 2 worker modes. with and without ackers in each mode- ran SimplifiedWordCountTopo- did some quick perf verifications with ConstSpoutNullBolt- basic checking of

Re: [VOTE] Release Apache Storm 2.0.0 RC7

Yes, you need to rebuild your topology jars against 2.0.  If you have some settings to tweak perf with 1.x,  refer to https://github.com/apache/storm/blob/master/docs/Performance.md for the 2.x configs. On Tuesday, April 30, 2019, 2:41:49 PM PDT, Alexandre Vermeerbergen wrote:

Re: [RESULT] [VOTE] Release Apache Storm 1.2.3 (rc1)

Taylor,    Could you share your plans for the 1.2.3 rc  ?-roshan On Thursday, April 11, 2019, 10:20:50 PM PDT, gita gita wrote: Sorry for constant nagging, Any update on the release. On Thu, Mar 7, 2019 at 12:22 PM Roshan Naik wrote: > It appears more likely that both relea

Re: [VOTE] Release Apache Storm 2.0.0 RC5

? On Wednesday, March 27, 2019, 4:39:33 PM PDT, Roshan Naik wrote:  Will there be another RC or this one is good to continue with ? Sent from Yahoo Mail for iPhone On Wednesday, March 27, 2019, 9:41 AM, Derek Dagit wrote: * Downloaded source ZIP, `mvn clean install`, all passed

Re: [VOTE] Release Apache Storm 2.0.0 RC5

 Will there be another RC or this one is good to continue with ? Sent from Yahoo Mail for iPhone On Wednesday, March 27, 2019, 9:41 AM, Derek Dagit wrote: * Downloaded source ZIP, `mvn clean install`, all passed * Verified signatures and checksums * Packaged my build and ran a single-tenant

Re: [RESULT] [VOTE] Release Apache Storm 1.2.3 (rc1)

for the update. Any approximate timelines for the release? I see last release happened on May 17, 2018, any possibility of releasing 1.2.3 earlier if this is being blocked by 2.0 release? On Thu, Feb 28, 2019 at 4:29 AM Roshan Naik wrote: >  Gita,    Sorry for the late response. Due to some impt iss

Re: [RESULT] [VOTE] Release Apache Storm 1.2.3 (rc1)

Gita,    Sorry for the late response. Due to some impt issues being discovered just prior to the release was going to be published, the release was held off. Fixes are in and another RC should be out expected soon. RC typically takes about a week or two to get approved and published.-roshan

Re: [VOTE] Release Apache Storm 2.0.0 (rc4)

, 2019 at 8:22 AM Govind Menon wrote: > +1 for continuing with the RC > > On Tue, 29 Jan 2019 at 16:49, Arun Mahadevan wrote: > > > Agree with continuing with the RC if this is not a blocker. > > > > On Tue, 29 Jan 2019 at 12:29, Roshan Naik > > > wro

Re: [VOTE] Release Apache Storm 2.0.0 (rc4)

Correct me if I am wrong, this seems to be a bug with a workaround but not an exploitable security hole. ? if this is not a security hole, and the workaround is realistic then we should go ahead with the current RC IMO.-roshan On Tuesday, January 29, 2019, 10:26:53 AM PST, Kishorkumar Patil

Re: Storm 2.0 blogs ?

have dropped Druid support, so 13 should be only Kinesis. > > > > Which format should the blurbs be written in? (Markdown?) > > > > Den ons. 23. jan. 2019 kl. 08.57 skrev Roshan Naik > > : > > > >> Like Taylor’s suggestion of collectively contributing sm

Re: Storm 2.0 blogs ?

Like Taylor’s suggestion of collectively contributing small blurbs on features for the Release announcement. Thats the first thing people look on hearing a release announcement. The jira list is not very understandable at first glance. Based on suggestions so far and a quick scan of the jiras

Storm 2.0 blogs ?

Now that  2.0 has all the votes it needs to move forward, maybe a good time to think of some blogs to go with this long awaited release.   Some potential topics that come to mind are: 1- Overview of new features and major changes since 1.x2- Re-architecture (messaging, threading, back

Re: [NOTICE] Migration of storm repos to gitbox is done

Thanks Ethan.  Sent from Yahoo Mail for iPhone On Sunday, January 20, 2019, 7:33 PM, Ethan Li wrote: Hi Team, The migration to https://gitbox.apache.org/ is done (https://issues.apache.org/jira/browse/INFRA-17705 ). Thanks, - Ethan

Re: [VOTE] Release Apache Storm 2.0.0 (rc4)

mp, restart worker : OK   - log search : OK I don't think perf. degrade is a blocker for this release, since we are still providing far better performance then 1.x. As Roshan is planning to address this, that could be fixed in 2.0.x hopefully. Thanks, Jungtaek Lim (heartSaVioR) 2019년 1월 19일 (토) 오전 5:

Re: [VOTE] Release Apache Storm 2.0.0 (rc4)

Was verifying the performance on 2.0 and noticed that the inter worker messaging has fallen off a cliff With ConstSpoutNullBoltTopo (producer batch size=1k, ackers=0, workers=2) it was ~3.2mill/sec down  and now its down to  ~1.6mill/sec. Something has impacted this recently. Will try to

Re: New Storm Committer and PMC Member

Congratulations Govind. Roshan Sent from Yahoo Mail for iPhone On Wednesday, January 9, 2019, 10:47 AM, Ethan Li wrote: Congratulations! Govind. Well deserved! Ethan > On Jan 9, 2019, at 12:40 PM, Hugo Louro wrote: > > Congratulations Govind. Very well deserved. Thank you for all your >

Re: Storm 2.0.0 release?

;>>>> Thanks, >>>>> >>>>> Bobby >>>>> >>>>> On Thu, Dec 13, 2018 at 1:07 PM Stig Rohde Døssing < >>>> stigdoess...@gmail.com >>>>>> >>>>> wrote: >>>>> >>>

Re: Storm 2.0.0 release?

Sounds like -  https://github.com/apache/storm/pull/2913 (STORM-3290) is merged -  https://github.com/apache/storm/pull/2908 (STORM-3276) is nearly complete and may need some small tweaks. -  https://github.com/apache/storm/pull/2907  (STORM-2990, STORM-3279) appears ready to be committed ?

Re: [VOTE] Release Apache Storm 2.0.0 (rc3)

external/storm-autocreds  appears to have grown a lot. In 1.2.2:   93mb,  113 filesIn 2.0.0 :  173mb,  204 files. fyi: let me know if the formatting in my prev mail is messed up ... i can resend. -roshan On Sunday, October 21, 2018, 5:54:36 PM PDT, Roshan Naik wrote: The 2.0

Re: [VOTE] Release Apache Storm 2.0.0 (rc3)

The 2.0 compressed tar.gz is ~270 MB in comparison to 1.2.2 jar which stands at ~160MB. Seems like a big jump and wanted to make sure there is no unintended bloat occurring. Listing of files larger than 5MB in both (ordered by size):  23M  =>  apache-storm-1.2.2/lib/storm-core-1.2.2.jar 21M  => 

Re: Hadoop Contributor Meetup

I can do a talk on the rework of threading,  messaging and backpressure  for 2.0  Roshan Sent from Yahoo Mail for iPhone On Friday, September 21, 2018, 8:37 AM, Bobby Evans wrote: There is a Hadoop Contributor Meetup at Oath/Yahoo on Monday in Sunnyvale CA

Re: Is the powered-by file in the Storm repository necessary?

Having it in the site is sufficient IMO as well.  On Saturday, September 15, 2018, 4:16:05 AM PDT, Stig Rohde Døssing wrote: Hi, We have a powered-by.md file in the Storm repository's /docs directory. There's also a powered-by file in the storm-site repo root, as well as in each

Re: Regarding releasing Apache Storm 2.0.0

Happy to see consensus in moving fwd with 2.0 soon.  I will try to get a minor patch (STORM-3205) within 24 hours ... as it seems like it has potential to deliver a decent perf boost and energy savings. One thing I am hoping we can address before releasing Storm 2 is... to fix the naming of the

Re: Question regarding Storm

Perhaps you can try some things depending on how feasible they it is for your case: 1- Try to design and deploy your topology to maximize communication within a worker process instead fo across worker processes. 2- Alternatively you can spin up multiple single worker instances of you toplo3-

Re: New Committer/PMC Member: Ethan Li

Congratulations Ethan.  Sent from Yahoo Mail for iPhone On Monday, April 16, 2018, 9:23 AM, Bobby Evans wrote: Please Join with me in welcoming Ethan Li as the newest Apache Storm committer and PMC member. Great work!

Re: New Committer/PMC Member: Roshan Naik

; > > Congratulations! Roshan> > > >> > > > Ethan Li> > > >> > > > > On Apr 5, 2018, at 21:40, Jungtaek Lim <ka...@gmail.com> wrote:> > > > >> > > > > Congrats Roshan!> > > > >> > > >

Re: [DISCUSS] Plan on Storm 2.0.0

Would be good to callout which of issues listed in Storm 2.0 epic are considered “blockers” vs “very desirable” vs “good to have” -roshan On 2/19/18, 3:29 PM, "Jungtaek Lim" wrote: Hi devs, We've just released Storm 1.2.1 (not officially announced but vote

Re: [DISCUSS] Decouple Storm core and connectors

il.com> wrote: I think we all agree that releasing connectors as part of a Storm release hinders the frequency of the release cycle for both Storm proper, as well as connectors. If that’s the case, then the question is how to proceed. -Taylor > On Jan 31, 2018,

Re: [DISCUSS] Decouple Storm core and connectors

One thought is to … - do a frequent separate release - *and also* include the latest stuff along with each Storm release. -roshan On 1/31/18, 10:43 AM, "generalbas@gmail.com on behalf of Stig Rohde Døssing" wrote: Hugo,

Re: Request for holding off commits to storm-client module

If you want to hold off commits just before you submit a pull request, and you expect to submit it in several days, I'm also OK to wait for that. I just would like to ensure that holding doesn't stay longer. Thanks, Jungtaek Lim (HeartSaVioR) 2017년 7월 24일 (월) 오전 7

Request for holding off commits to storm-client module

Storm Devs, My PR for STORM-2306 (messaging subsystem redesign) is almost ready. Not surprisingly, this PR brings extensive modifications in storm-client module and touches lightly on some others. Just finished manually rebasing my local changes (to ~90 files) from an old version of master

Re: Few observations related to KafkaSpout implementation (1.1.0)

There is a set of simple topologies in storm-perf for such benchmarking… we have one there that measures perf of the old KafkaSpout : https://github.com/apache/storm/blob/1.x-branch/examples/storm-perf/src/main/java/org/apache/storm/perf/KafkaSpoutNullBoltTopo.java We don’t have one yet for the

Re: [Discussion]: Storm Improvemement Proposal (SIP) to discuss changes

is really required for any enhancement which is not really big. On Sat, Jun 10, 2017 at 5:13 AM, Roshan Naik <ros...@hortonworks.com> wrote: If I am looking at the Kafka site correctly, I see that Kafka has a total of 167 KIPs so far. So I assume that min

Re: [Discussion]: Storm Improvemement Proposal (SIP) to discuss changes

If I am looking at the Kafka site correctly, I see that Kafka has a total of 167 KIPs so far. So I assume that minor new features would not be parrt of the SIP ? Unlike Kafka, since Storm has a number of connectors (that keep growing), I am speculating the SIP process might get somewhat

Re: [DISCUSS] Storm 2.0 Roadmap

ics V2 sooner since > we > >> lost metrics even when doing normal operation like restarting worker, > >> rebalancing, and so on. Eventually we need to fight with dynamic > scaling, > >> and then metrics will be broken often. > >>

Re: [DISCUSS] Code Style

- Personally not a big fan of _ for members either from the readability standpoint. Also much of the existing code doesn’t follow this. - Personally I find it is easier to write/read one-liner if/else without the curlys. Always wondered about the rationale behind that. Would suggest any such a

Recording - Storm & Kafka Meetup on April 20th 2017

Louro (Hortonworks) - [20m] – Rethinking the Storm 2.0 Worker - Roshan Naik (Hortonworks) - [57m] – Storm in Retail Context: Catalog data processing using Kafka, Storm & Microservices - Karthik Deivasigamani (WalMart Labs) - [1h: 54m:45sec] – Schema Regi

STORM-2423 for 1.1.0

All, Found a critical issue with JoinBolt that would like to get a fix into 1.1.0. https://issues.apache.org/jira/browse/STORM-2423 -roshan

Re: Too many threads per bolt instance (as seen with jconsole images)

at gets me 20 threads/bolt. And I am not creating any new threads inside my bolts. On Thu, Mar 16, 2017 at 6:12 PM, Roshan Naik <ros...@hortonworks.com> wrote: > I assume you mean ..3 thds per spout/bolt is on the high side ? > Currently there is an executor thd,

Re: Too many threads per bolt instance (as seen with jconsole images)

tal threads/node). Some of these would be essential for the worker's book-keeping but still it seems we can get a lot of performance boost if we can somehow reduce these threads and the associated context switching between them. On Thu, Mar 16, 2017 at 12:53 PM,

Re: Too many threads per bolt instance (as seen with jconsole images)

Typically there are 3 threads per spout or bolt instance (unless the spout or bolt is spawning its own threads). There are the acker bolts, event loggers and system bolt running there too. Then there are several more per worker. See a summary of it in section 3.1 of this document

Re: Debugging on Storm Topologies

Submit your topology using LocalCluster in the topology’s main() method. Then you should be able to set breakpoints etc. -roshan On 3/14/17, 2:14 PM, "Vankadari, Chandra Sekhar (Contractor)" wrote: Hey, I want to set break points in my Storm

Re: [CANCELED] [VOTE] Release Apache Storm 1.1.0 (RC2)

> rare case. > > > > I would like to see the opposite approach, removing all connectors (or > > just keeping storm-kafka/storm-kafka-client and some more preferred > things) > > and its relevant examples from binary dist. > > > > What do you thi

Re: [CANCELED] [VOTE] Release Apache Storm 1.1.0 (RC2)

Looks like the formatting on my prev email got dropped. But observation is that storm-kafka-monitor and storm-druid are the biggest new contributors. -roshan On 3/1/17, 5:23 PM, "Roshan Naik" <ros...@hortonworks.com> wrote: Once all of the shaded examples are included the

Re: Storm 1.x-branch won't build in IntelliJ anymore

clean install -DskipTests). Does workaround not work any more? Or do you see some spots which workaround doesn't work? - Jungtaek Lim (HeartSaVioR) On Wed, Mar 1, 2017 at 11:34 PM, Roshan Naik <ros...@hortonworks.com> wrote: > If we leave 1.x in this state

Re: [CANCELED] [VOTE] Release Apache Storm 1.1.0 (RC2)

largely due to > shaded examples, etc. But it’s something to keep an eye on. Our binary > releases shouldn’t have to be that big. > > -Taylor > > On Mar 1, 2017, at 12:09 PM, Roshan Naik <ros...@hortonworks.com ros...@hortonworks.com>>

Re: [CANCELED] [VOTE] Release Apache Storm 1.1.0 (RC2)

nks for bringing these up Roshan. Feel free to file JIRA tickets for these issues and assign the “Release Apache Storm 1.1.0” epic so they can be tracked for this release. -Taylor > On Mar 1, 2017, at 9:27 AM, Roshan Naik <ros...@hortonworks.com> wrote: > >

Re: [CANCELED] [VOTE] Release Apache Storm 1.1.0 (RC2)

Found these additional issues: 1- BUG: Even if topology.eventlogger.executors=0, the event_logger bolt is instantiated … previously observed to cause ~10% degradation in perf even with logging disabled. 2- Missing Jars: The storm-*-examples jars are missing in the binary distro (other than

Re: Storm 1.x-branch won't build in IntelliJ anymore

>address them at 2.1 or other minor versions. > >Any other opinions? > >- Jungtaek Lim (HeartSaVioR) > >2017년 3월 1일 (수) 오전 9:27, Roshan Naik <ros...@hortonworks.com>님이 작성: > >Lately (about a week and half maybe) it has not been possi

Storm 1.x-branch won't build in IntelliJ anymore

Lately (about a week and half maybe) it has not been possible to get the 1.x-branch to build inside IntelliJ. None of the modules are able to locate the LocalCluster class (which is a clojure class). Previously, every once in a while, I used to get this problem in the storm-starter module and

Re: [DISCUSS] Remove CHANGELOG file

Sounds like a good idea to me. -roshan On 2/23/17, 4:41 PM, "Jungtaek Lim" wrote: Hi devs, I guess we discussed about this before, but didn't move to actual work. I'd like to propose again removing CHANGELOG file in repository, and use JIRA issue's

Re: [Discuss] Storm hdfs spout improvements

On 2/13/17, 12:14 PM, "Sachin Pasalkar" wrote: >I have attached updated source code of HDFSSpout for more reference. I >have updated respective classes (not attached) Don¹t see any attachment. Answers are below. Better to do this discussion on a JIRA. On

Re: Storm benchmarks

http://hortonworks.com/blog/microbenchmarking-storm-1-0-performance/ -roshan On 11/4/16, 7:13 AM, "Paul Poulosky" wrote: >IEEE Xplore Document - Benchmarking Streaming Computation Engines: Storm, >Flink and Spark Streaming > > >| >| | >IEEE Xplore

Re: [DISCUSS] Feature Branch for Apache Beam Runner

Good idea. Will the Beam API be implemented to run on top Storm Core primitives ? -roshan On 9/15/16, 2:00 PM, "P. Taylor Goetz" wrote: >I¹ve been tinkering with implementing an Apache Beam runner on top of >Storm and would like to open it up so others in the community can

Re: Performance improvements in 1.0.0

Here is one effort on quantification the improvements Š http://hortonworks.com/blog/microbenchmarking-storm-1-0-performance/ -roshan On 9/6/16, 10:17 AM, "S G" wrote: >Hi, > >On the http://storm.apache.org/2016/04/12/storm100-released.html page, I >see a notice

Re: Details about the Storm Scheduler

AM To: "dev@storm.apache.org<mailto:dev@storm.apache.org>" <dev@storm.apache.org<mailto:dev@storm.apache.org>>, Bobby Evans <ev...@yahoo-inc.com<mailto:ev...@yahoo-inc.com>> Cc: Roshan Naik <ros...@hortonworks.com<mailto:ros...@hortonworks.com>>

[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=15433795#comment-15433795 ] Roshan Naik commented on STORM-1949: The amount of *additional* pressure this BP mechanism adds to ZK

Re: Details about the Storm Scheduler

On 8/22/16, 6:55 AM, "Bobby Evans" wrote: >Getting the CPU used for a worker is simple, but getting the CPU used for >individual components is not so simple/almost impossible for >multi-threaded bolts/spouts. The current scheduling assumes that the CPU >for all

[jira] [Updated] (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 ] Roshan Naik updated STORM-1949: --- Attachment: wordcounttopo.zip Attaching the wordcount topo that i used. > Backpressure can ca

[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=15423916#comment-15423916 ] Roshan Naik commented on STORM-1949: With BP disabled the topo ran fine. Dont think saw any NPE during

[jira] [Commented] (STORM-1910) One topology can't use hdfs spout to read from two locations

[ https://issues.apache.org/jira/browse/STORM-1910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15378435#comment-15378435 ] Roshan Naik commented on STORM-1910: [~ptgoetz] should this be marked for 1.0.2 as well ? >

Re: Request for reviewing

STORM-1910 -roshan On 7/14/16, 8:59 AM, "Jungtaek Lim" wrote: >We seems close to make all issues for 1.0.2 epic resolved soon. > >Epic link: https://issues.apache.org/jira/browse/STORM-1855 >All of open issues are in progress of reviewing. Most of them got +1 and >is

[jira] [Updated] (STORM-1956) Disable Backpressure by default

[ https://issues.apache.org/jira/browse/STORM-1956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roshan Naik updated STORM-1956: --- Priority: Blocker (was: Major) > Disable Backpressure by defa

[jira] [Updated] (STORM-1956) Disable Backpressure by default

[ https://issues.apache.org/jira/browse/STORM-1956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roshan Naik updated STORM-1956: --- Fix Version/s: 1.0.2 > Disable Backpressure by defa

[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=15368640#comment-15368640 ] Roshan Naik commented on STORM-1949: Have not worked out a concrete solution to avoiding ZK as yet

[jira] [Created] (STORM-1956) Disable Backpressure by default

Roshan Naik created STORM-1956: -- Summary: Disable Backpressure by default Key: STORM-1956 URL: https://issues.apache.org/jira/browse/STORM-1956 Project: Apache Storm Issue Type: Bug

[jira] [Comment Edited] (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=15368451#comment-15368451 ] Roshan Naik edited comment on STORM-1949 at 7/8/16 8:53 PM: [~revans2

[jira] [Comment Edited] (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=15368451#comment-15368451 ] Roshan Naik edited comment on STORM-1949 at 7/8/16 8:50 PM: [~revans2

[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=15368451#comment-15368451 ] Roshan Naik commented on STORM-1949: [~revans2] Not sure what you mean by "back on the write"

[jira] [Commented] (STORM-1910) One topology can't use hdfs spout to read from two locations

[ https://issues.apache.org/jira/browse/STORM-1910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15367096#comment-15367096 ] Roshan Naik commented on STORM-1910: WRT Pt# 2 in the description, we cannot check for valid HDFS path

[jira] [Created] (STORM-1949) Storm backpressure can cause spout to stop emitting and stall topology

Roshan Naik created STORM-1949: -- Summary: Storm backpressure can cause spout to stop emitting and stall topology Key: STORM-1949 URL: https://issues.apache.org/jira/browse/STORM-1949 Project: Apache

[jira] [Updated] (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 ] Roshan Naik updated STORM-1949: --- Summary: Backpressure can cause spout to stop emitting and stall topology (was: Storm backpressure

[jira] [Created] (STORM-1892) class org.apache.storm.hdfs.spout.TextFileReader should be public

Roshan Naik created STORM-1892: -- Summary: class org.apache.storm.hdfs.spout.TextFileReader should be public Key: STORM-1892 URL: https://issues.apache.org/jira/browse/STORM-1892 Project: Apache Storm

Re: STORM JIRA being spammed - CANNOT comment on JIRA (as a result of the counter spam measures)

Myself too. Thanks. -Roshan On 5/12/16, 1:14 PM, "Bobby Evans" wrote: >Sorry about that you should be added as a contributor now. Is there >anyone else that I should add as a contributor? >Also we have not been maintaining the commiters ACL very well either. >Are

[jira] [Commented] (STORM-1772) Create topologies for measuring performance

[ https://issues.apache.org/jira/browse/STORM-1772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15279190#comment-15279190 ] Roshan Naik commented on STORM-1772: Hi [~mauzhang], Yes thats it. I first observed that perf

[jira] [Created] (STORM-1772) Create topologies for measuring performance

Roshan Naik created STORM-1772: -- Summary: Create topologies for measuring performance Key: STORM-1772 URL: https://issues.apache.org/jira/browse/STORM-1772 Project: Apache Storm Issue Type: Bug

[jira] [Updated] (STORM-1772) Create topologies for measuring performance

[ https://issues.apache.org/jira/browse/STORM-1772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roshan Naik updated STORM-1772: --- Description: Would be very useful to have some simple reference topologies included with Storm

[jira] [Assigned] (STORM-1772) Create topologies for measuring performance

[ https://issues.apache.org/jira/browse/STORM-1772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roshan Naik reassigned STORM-1772: -- Assignee: Roshan Naik > Create topologies for measuring performa

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

This is missing HdfsSpout (STORM-1199) -roshan On 5/3/16, 3:39 PM, "Hugo Da Cruz Louro" wrote: >+1 (non binding) >- Found a very minor bug in the storm-solr test topology, for which there >is a very simple workaround and by NO means a blocker for the release. >-

Re: [jira] [Commented] (STORM-1757) Apache Beam Runner for Storm

Never mind my prev comment… got confused by looking at BEAM-216. -roshan On 5/3/16, 4:55 PM, "Roshan Naik" <ros...@hortonworks.com> wrote: >Shouldn¹t we have a BEAM runner in Storm project instead of Storm runner >in Beam project ? >-roshan > >On 5/3/16,

Re: [jira] [Commented] (STORM-1757) Apache Beam Runner for Storm

Shouldn¹t we have a BEAM runner in Storm project instead of Storm runner in Beam project ? -roshan On 5/3/16, 1:15 PM, "Hugo Louro (JIRA)" wrote: > >[ >https://issues.apache.org/jira/browse/STORM-1757?page=com.atlassian.jira.p

Re: Thought on complete latency

IMO, avoiding the time variation on machines makes total sense. But I feel that this is a tricky question. Couple more thoughts: 1) As per http://storm.apache.org/releases/current/Guaranteeing-message-processing.ht ml "Storm can detect when the tree of tuples is fully processed and can ack

[jira] [Updated] (STORM-1580) Secure hdfs spout failed

[ https://issues.apache.org/jira/browse/STORM-1580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roshan Naik updated STORM-1580: --- Attachment: HdfsSpoutTopology.java Sorry for the delayed update... kept getting pulled into other

[jira] [Updated] (STORM-1632) Disable event logging by default

[ https://issues.apache.org/jira/browse/STORM-1632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roshan Naik updated STORM-1632: --- Attachment: BasicTopology.java uploading topology code to validate perf hit. To use it: .. 1) Copy

[jira] [Commented] (STORM-1580) Secure hdfs spout failed

[ https://issues.apache.org/jira/browse/STORM-1580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15209389#comment-15209389 ] Roshan Naik commented on STORM-1580: [~ght] fyi.. I am beginning to take a look at this. > Sec

  1   2   >