Re: NullPointerException on startup

If this is the case then it should not happen. As you suspect that 'there’s a race condition where it tries to retrieve the topic partition from the map but it hasn’t been loaded yet' then if Kafka has been up for a long time, then there should not be such problem of loading. Have you modified the

Re: Testing serializers with multiple workers

Ohad, We found that we had to use localOrShuffle grouping in order to see activity in the same worker as the spout. -Chien From: Ohad Edelstein Sent: Friday, November 18, 2016 8:38:35 AM To: user@storm.apache.org Subject: Re: Testing

Re: Cant connect to remote cluster

Please use IRC for this. Mailing list is not for Instant Messaging. On Nov 18, 2016 2:21 PM, "Mostafa Gomaa" wrote: Also is nimbus by any chance hosted on AWS or Azure? On Nov 19, 2016 12:18 AM, "Ohad Edelstein" wrote: > Try add the zookeeper part to

Re: Cant connect to remote cluster

Try add the zookeeper part to the client storm.yaml I think that the request is searching for the zookeeper to pass the message and fails From: Al Hennessey > Reply-To: "user@storm.apache.org"

Re: Cant connect to remote cluster

Looks like it's a firewall settings issue. Try sudo ufw allow 6627 on your nimbus machine On Nov 19, 2016 12:17 AM, "Al Hennessey" wrote: > Yes i used the domain name for the nimbus seed > > On 18 Nov 2016, at 22:15, sam mohel wrote: > > Did you

Re: Cant connect to remote cluster

It could be a firewall issue, so check your firewall settings. Otherwise it's probably a network settings issue. I had this problem before and i fixed it by setting the hostname in /etc/hosts on the local and remote machines. On Nov 19, 2016 12:14 AM, "Al Hennessey"

Re: Cant connect to remote cluster

I tried to connect via telnet and this is what i got MacBook-Pro:~ Al$ telnet 130.211.53.188 6627 Trying 130.211.53.188... telnet: connect to address 130.211.53.188: Connection refused telnet: Unable to connect to remote host > On 18 Nov 2016, at 22:12, Ohad Edelstein wrote: >

Re: Cant connect to remote cluster

Yes i used the domain name for the nimbus seed > On 18 Nov 2016, at 22:15, sam mohel wrote: > > Did you try to use domain name in storm.yaml instead of IP address for nimbus > ? > > On Saturday, November 19, 2016, Al Hennessey

Re: Cant connect to remote cluster

Did you try to use domain name in storm.yaml instead of IP address for nimbus ? On Saturday, November 19, 2016, Al Hennessey wrote: > Hi, i thanks for the reply, i added the ip to my hosts file with a domain > name, but it still did not work and threw the same error >

Re: Cant connect to remote cluster

Yh i ran the same command from the nimbus machine and it worked fine > On 18 Nov 2016, at 22:12, Ohad Edelstein wrote: > > Did you try running the command, from the same machine? > > From: Al Hennessey > > Reply-To:

Re: Cant connect to remote cluster

Can you telnet the ip on 6627 from your local machine? On Nov 19, 2016 12:11 AM, "Al Hennessey" wrote: Hi, i thanks for the reply, i added the ip to my hosts file with a domain name, but it still did not work and threw the same error Just to let you know that i am on a

Re: Cant connect to remote cluster

Did you try running the command, from the same machine? From: Al Hennessey > Reply-To: "user@storm.apache.org" > Date: Saturday, 19 November 2016 at 0:10 To:

Re: Cant connect to remote cluster

Hi, i thanks for the reply, i added the ip to my hosts file with a domain name, but it still did not work and threw the same error Just to let you know that i am on a mac Thanks for the help > On 18 Nov 2016, at 22:01, sam mohel wrote: > > m new to storm but let's try that

Re: Cant connect to remote cluster

m new to storm but let's try that and I hope it will work Check the file which has definitions of IP It exists in this path /ets/hosts it should contains like127.0.x.x mydomain 1- Check that 130.211.53.188 has domain name or it already exists or 2-If you found it try to use the domain name

Cant connect to remote cluster

Hi, i am having an issue connecting to my remote clustered storm server, when i try running “storm list” i get this error Exception in thread "main" java.lang.RuntimeException: org.apache.storm.thrift.transport.TTransportException: java.net.UnknownHostException: nimbus-dev.c.epic-dev.internal

Re: NullPointerException on startup

The spout is initialized during topology submission, so how would you delay that? Kafka is already running for a long period of time. Thanks, Nick --- Sent from Boxer | http://getboxer.com On November 18, 2016 at 11:51:29 AM PST, Harsh Choudhary

Re: NullPointerException on startup

I think, you may want to start kafka and then give some time for its initialisation and then submit topology. On Sat, Nov 19, 2016 at 12:55 AM, Cuneo, Nicholas wrote: > The cause of the null pointer exception is IN kafka spout during an ACK > > > > My guess is there’s a race

Acking and Anchoring issues

I have following topology structure Kafka Spout Bolt A : Reads tuples from spout and extracts some info *_collector.**emit**(**tuple**,* *new** Values**(...**)**)**;* *_collector.ack(tuple)* *In case of exception / error * *_collector.fail(tuple)* Bolt B : Create files based on info

RE: NullPointerException on startup

The cause of the null pointer exception is IN kafka spout during an ACK My guess is there’s a race condition where it tries to retrieve the topic partition from the map but it hasn’t been loaded yet. Which results in a NULL entry during the GET. When the topology starts up it will immediately

Re: NullPointerException on startup

Hi This happens when there is some code in bolt or spout which throws Null Pointer Exception. I suggest you to use Debugger in your IDE, to find out where is this happening. You can try making a Local Cluster and runs it in IDE to figure it out easily. It never happens because of Storm, so do not

NullPointerException on startup

Hello, We are working with storm 1.0.2 and using Kafka client to subscribe to kafka topics to retrieve data. Randomly when our topologies are starting up we receive a null pointer exception which is killing the topology. We can't seem to identify why this happens, or what measures we can

Re: Testing serializers with multiple workers

Hello, We just finished setting up storm 1.0.1 with 3 supervisors and one nimbus machine. Total of 4 machines in aws. We see the following phanomenon: lets say spout on host2, host1 - using 100% cpu host3 - using 100% cpu host2 - idle (some message are being handled by it, not many) its not

Re: Testing serializers with multiple workers

Hit send too soon... that really is the option :-) On Fri, Nov 18, 2016 at 9:03 AM Aaron Niskodé-Dossett wrote: > topology.testing.always.try.serialize = true > > On Fri, Nov 18, 2016 at 8:57 AM Kristopher Kane > wrote: > > Does anyone have any

Re: Testing serializers with multiple workers

topology.testing.always.try.serialize = true On Fri, Nov 18, 2016 at 8:57 AM Kristopher Kane wrote: > Does anyone have any techniques for testing serializers that would only > surface when the serializer is uses in a multi-worker topology? > > Kris >

Testing serializers with multiple workers

Does anyone have any techniques for testing serializers that would only surface when the serializer is uses in a multi-worker topology? Kris

Trident Topology not fully executedt

Not understanding why SendKafka(BaseFunction) and Count(CombinerAggregator) are not executed. Anyone have any idea why? topologyTrident.newStream("lines", new RandomDataJsonSpout()) .each(new Fields("line"), new ExtractField(new Fields("id", "speed")), new Fields("id", "field")) .aggregate(new