Hi Michael,
I experimented a bit by making changes to my topology and now I'm
seeing consistent acking with little failures on the spout.
My topology had a spout S emitting tuples and two BaseRichBolts B1
(store tuple) and B2 (aggregate tuple) were receiving tuples from the
default stream
maybe you need scala-library.jar, it will work.
2014-04-16 5:37 GMT+08:00 M. Solaimani :
> Hi,
>
> I have copied those jar files in storm lib folder. That errors are gone
> but I have new error.
>
> java.lang.NoClassDefFoundError: scala/runtime/AbstractFunction1$mcLI$sp
> at java.lang.Clas
hi Harsha,
i have ruby 1.8.7，but i always build it skipping test and still get the
same error above when attach "mvn -X" output.
i have tried on different machines for centos and ubuntu. i'm very confused
with it.
2014-04-16 0:45 GMT+08:00 Harsha :
>
>
> Xing,
>
> Do you have ruby 1.9
David,
looks like that article is old. Follow these instructions for
running storm on windows.
[1]http://ptgoetz.github.io/blog/2013/12/18/running-apache-storm-on-win
dows/
-Harsha
On Tue, Apr 15, 2014, at 06:57 AM, David Novogrodsky wrote:
First, thanks for your help. This list is g
We are using Storm 0.9.0.1 with Netty and Trident topologies on a single
machine (nimbus, supervisor, and drpc running on the same machine). Supervisor
keeps dying and gets restarted after 7-8 seconds by Supervisord (the service
that restarts storm and zookeeper processes). Here is the error i
Hi,
I have copied those jar files in storm lib folder. That errors are gone but
I have new error.
java.lang.NoClassDefFoundError: scala/runtime/AbstractFunction1$mcLI$sp
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:800)
Xing,
Do you have ruby 1.9.3 and python installed. I was able to
build using java 1.6.0_37 on centos 6.5
but you need ruby and python for the build as multilang tests uses
them. If you still seeing issues with build please attach "mvn -X clean
package" output.
-Harsha
On Mon, Apr 14, 2
Hey Srinath,
Yep, our ackers don't seem overloaded at all, and the behavior you are
seeing sounds exactly like what we are seeing here.
On Tue, Apr 15, 2014 at 6:47 AM, Srinath C wrote:
> I have been seeing this behaviour on 0.9.0.1 running on (aws & non-vpc).
> All tuples get a fail() on the
Hey Oliver,
We're not seeing any errors in our logs after switching to the zmq
transport. The reason we tried the zmq transport was several users on the
mailing list seemed to have had some success with switching to it after
seeing intermittent issues with netty. We were seeing timeouts between
Hey 朱春来,
The processing time on the bolts seem reasonable, as does the overall
complete latency of the spout.
On Tue, Apr 15, 2014 at 2:37 AM, 朱春来 wrote:
> Hi Michael Chang,
>
>
>
> Did you ack or fail tuple in the bolt timely and please check the
> bolt processing speed of a tuple.
>
The documentation for trident aggregations mentions that aggregations are
done globally across all batches.
https://github.com/nathanmarz/storm/wiki/Trident-API-Overview#aggregation-operations
Is this incorrect ?
When the documentation says "all batches" it does mean all batches across
all worker
First, thanks for your help. This list is great!!
I am working on a Windows 7 system. I have been able to compile my test
Storm project. I am having some problem running the project locally, i.e.
not on a cluster.
When I try to run it locally, I get this error:
C:\Users\david.j.novogrodsky\Do
Hi Michael,
We've been seeing a similar issue, after upgrading from Storm 0.8.2 to
0.9.0.1. When we start our topology, it times out every batch of
events. We're using Trident, with nodes set up on AWS (see
http://mail-archives.apache.org/mod_mbox/incubator-storm-user/201404.mbox/%3CCAMij6%3Dc1drv
I have been seeing this behaviour on 0.9.0.1 running on (aws & non-vpc).
All tuples get a fail() on the spout and I'm not sure why. Even a simple
case of spoutA -> boltB is showing up this behaviour after a continuous
flow of tuples.
So far increasing ACKer count hasn't helped. All I could figure
Clone the git repo and just do a "mvn clean install" in the repository root
directory.
On Tue, Apr 15, 2014 at 2:04 PM, Xing Yong wrote:
> download the release source code
> https://github.com/apache/incubator-storm/releases and mvn package
>
> i have made some try on this.
>
> if you compile s
download the release source code
https://github.com/apache/incubator-storm/releases and mvn package
i have made some try on this.
if you compile successfully, please tell me :-)
2014-04-15 19:59 GMT+08:00 李家宏 :
> hi, all
>
> How to build a storm release from source code(>=0.9.1) with maven ?
>
hi, all
How to build a storm release from source code(>=0.9.1) with maven ?
Thansk
--
==
Gvain
Email: jh.li...@gmail.com
Hi Michael Chang,
Did you ack or fail tuple in the bolt timely and please check the
bolt processing speed of a tuple.
发件人: Michael Chang [mailto:m...@tellapart.com]
发送时间: 2014年4月15日 16:41
收件人: user@storm.incubator.apache.org
主题: Storm Topology Halts
user@storm.incubator.
user@storm.incubator.apache.orgHey all,
Issue:
We are having issues with stuck topologies. When submitted and started,
our topology will start processing for a while, then completely halt for
around topology.max.spout.pending seconds, after which it seems that all
the in-flight tuples are failed
Take a look at storm-starter project from Nathan (
https://github.com/nathanmarz/storm-starter)
It uses maven to build two different jar files: one with dependencies (so
you don't have to put these in the lib folder) and one without them (so you
will have to provide these in the lib folder).
Hope
20 matches
Mail list logo
