You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@storm.apache.org by Abdelkader Lattab <al...@qf.org.qa> on 2015/11/10 12:09:56 UTC
storm redis issue
Folks
Could not get the spout shown in the below link to run, with storm 0.9.5. The method Nexttuple() is not called maybe blocked. Obviously I need help
https://github.com/sorenmacbeth/storm-redis-pubsub/blob/master/src/jvm/yieldbot/storm/RedisPubSubTopology.java
CONFIDENTIALITY NOTICE:
This email and any attachments transmitted with it are confidential and intended for the use of individual or entity to which it is addressed. If you have received this email in error, please delete it immediately and inform the sender. Unless you are the intended recipient, you may not use, disclose, copy or distribute this email or any attachments included. The contents of the emails including any attachments may be subjected to copyrights law, In such case the contents may not be copied, adapted, distributed or transmitted without the consent of the copyright owner.
RE: storm redis issue
Posted by Abdelkader Lattab <al...@qf.org.qa>.
Thank you Robby for the message.
Now I got the Spout working!
My topology ( test only) consists of only One Spout reading from Redis queue and one Bolt. The Bolt sometimes receives the tuples and sometime does not !!!! any tips
________________________________________
From: Bobby Evans [evans@yahoo-inc.com.INVALID]
Sent: Tuesday, November 10, 2015 5:19 PM
To: dev@storm.apache.org; dev@storm.incubator.apache.org
Subject: Re: storm redis issue
Not really sure. There isn't much information to go on. The topology example you sent runs in local mode, so you should be able to setup a debugger and walk through the code to see what is happening.
- Bobby
On Tuesday, November 10, 2015 8:03 AM, Abdelkader Lattab <al...@qf.org.qa> wrote:
Folks
Could not get the spout shown in the below link to run, with storm 0.9.5. The method Nexttuple() is not called maybe blocked. Obviously I need help
https://github.com/sorenmacbeth/storm-redis-pubsub/blob/master/src/jvm/yieldbot/storm/RedisPubSubTopology.java
CONFIDENTIALITY NOTICE:
This email and any attachments transmitted with it are confidential and intended for the use of individual or entity to which it is addressed. If you have received this email in error, please delete it immediately and inform the sender. Unless you are the intended recipient, you may not use, disclose, copy or distribute this email or any attachments included. The contents of the emails including any attachments may be subjected to copyrights law, In such case the contents may not be copied, adapted, distributed or transmitted without the consent of the copyright owner.
CONFIDENTIALITY NOTICE:
This email and any attachments transmitted with it are confidential and intended for the use of individual or entity to which it is addressed. If you have received this email in error, please delete it immediately and inform the sender. Unless you are the intended recipient, you may not use, disclose, copy or distribute this email or any attachments included. The contents of the emails including any attachments may be subjected to copyrights law, In such case the contents may not be copied, adapted, distributed or transmitted without the consent of the copyright owner.
Re: storm redis issue
Posted by Bobby Evans <ev...@yahoo-inc.com.INVALID>.
Not really sure. There isn't much information to go on. The topology example you sent runs in local mode, so you should be able to setup a debugger and walk through the code to see what is happening.
- Bobby
On Tuesday, November 10, 2015 8:03 AM, Abdelkader Lattab <al...@qf.org.qa> wrote:
Folks
Could not get the spout shown in the below link to run, with storm 0.9.5. The method Nexttuple() is not called maybe blocked. Obviously I need help
https://github.com/sorenmacbeth/storm-redis-pubsub/blob/master/src/jvm/yieldbot/storm/RedisPubSubTopology.java
CONFIDENTIALITY NOTICE:
This email and any attachments transmitted with it are confidential and intended for the use of individual or entity to which it is addressed. If you have received this email in error, please delete it immediately and inform the sender. Unless you are the intended recipient, you may not use, disclose, copy or distribute this email or any attachments included. The contents of the emails including any attachments may be subjected to copyrights law, In such case the contents may not be copied, adapted, distributed or transmitted without the consent of the copyright owner.