Re: how to deploy storm-0.9.2-incubating to my own maven repos?

2014-06-11 Thread Haralds Ulmanis
Hi, If I remember right - you need to disable this plugin (comment out or
delete lines):
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-release-plugin/artifactId
configuration
autoVersionSubmodulestrue/autoVersionSubmodules
tagNameFormatv@{project.version}/tagNameFormat
/configuration
/plugin



On 11 June 2014 03:07, 鞠大升 dashen...@gmail.com wrote:

 In DEVELOPER.md,I found how to build the code and create a storm
 distribution:

 mvn clean install -DskipTests=true

 cd storm-dist/binary  mvn package

 But how  to deploy storm-0.9.2-incubating to my own maven repos?

 I have changed the pom.xml, distributionManagement section to my own maven
 repos, but when run mvn deploy, failed with:

 --

 Downloading:
 https://repository.apache.org/content/repositories/snapshots/org/apache/storm/storm/0.9.2-incubating-SNAPSHOT/maven-metadata.xml

 Downloaded:
 https://repository.apache.org/content/repositories/snapshots/org/apache/storm/storm/0.9.2-incubating-SNAPSHOT/maven-metadata.xml
 (2 KB at 0.2 KB/sec)

 Uploading:
 https://repository.apache.org/content/repositories/snapshots/org/apache/storm/storm/0.9.2-incubating-SNAPSHOT/storm-0.9.2-incubating-20140611.020306-2.pom
 --



 --
 dashengju
 +86 13810875910
 dashen...@gmail.com



Re: [VOTE] Storm Logo Contest - Final Round

2014-06-11 Thread B Kersbergen
#6 - 5 pts.

2014-06-11 4:02 GMT+02:00 Corey Nolet cjno...@gmail.com:
 6 - 1pt
 9 - 4pt


 On Tue, Jun 10, 2014 at 8:34 PM, Nathan Leung ncle...@gmail.com wrote:

 #10 - 5


 On Tue, Jun 10, 2014 at 5:56 PM, Osman osmans...@gmail.com wrote:

 9 5

 On Jun 9, 2014 7:39 PM, P. Taylor Goetz ptgo...@gmail.com wrote:

 This is a call to vote on selecting the winning Storm logo from the 3
 finalists.

 The three candidates are:

  * [No. 6 - Alec
 Bartos](http://storm.incubator.apache.org/2014/04/23/logo-abartos.html)
  * [No. 9 - Jennifer
 Lee](http://storm.incubator.apache.org/2014/04/29/logo-jlee1.html)
  * [No. 10 - Jennifer
 Lee](http://storm.incubator.apache.org/2014/04/29/logo-jlee2.html)

 VOTING

 Each person can cast a single vote. A vote consists of 5 points that can
 be divided among multiple entries. To vote, list the entry number, followed
 by the number of points assigned. For example:

 #1 - 2 pts.
 #2 - 1 pt.
 #3 - 2 pts.

 Votes cast by PPMC members are considered binding, but voting is open to
 anyone. In the event of a tie vote from the PPMC, votes from the community
 will be used to break the tie.

 This vote will be open until Monday, June 16 11:59 PM UTC.

 - Taylor





Re: [VOTE] Storm Logo Contest - Final Round

2014-06-11 Thread Vinoth Kumar Kannan
#9 - 5 pts


On Wed, Jun 11, 2014 at 11:43 AM, B Kersbergen kersberg...@gmail.com
wrote:

 #6 - 5 pts.

 2014-06-11 4:02 GMT+02:00 Corey Nolet cjno...@gmail.com:
  6 - 1pt
  9 - 4pt
 
 
  On Tue, Jun 10, 2014 at 8:34 PM, Nathan Leung ncle...@gmail.com wrote:
 
  #10 - 5
 
 
  On Tue, Jun 10, 2014 at 5:56 PM, Osman osmans...@gmail.com wrote:
 
  9 5
 
  On Jun 9, 2014 7:39 PM, P. Taylor Goetz ptgo...@gmail.com wrote:
 
  This is a call to vote on selecting the winning Storm logo from the 3
  finalists.
 
  The three candidates are:
 
   * [No. 6 - Alec
  Bartos](
 http://storm.incubator.apache.org/2014/04/23/logo-abartos.html)
   * [No. 9 - Jennifer
  Lee](http://storm.incubator.apache.org/2014/04/29/logo-jlee1.html)
   * [No. 10 - Jennifer
  Lee](http://storm.incubator.apache.org/2014/04/29/logo-jlee2.html)
 
  VOTING
 
  Each person can cast a single vote. A vote consists of 5 points that
 can
  be divided among multiple entries. To vote, list the entry number,
 followed
  by the number of points assigned. For example:
 
  #1 - 2 pts.
  #2 - 1 pt.
  #3 - 2 pts.
 
  Votes cast by PPMC members are considered binding, but voting is open
 to
  anyone. In the event of a tie vote from the PPMC, votes from the
 community
  will be used to break the tie.
 
  This vote will be open until Monday, June 16 11:59 PM UTC.
 
  - Taylor
 
 
 




-- 
With Regards,
Vinoth Kumar K


Re: [VOTE] Storm Logo Contest - Final Round

2014-06-11 Thread prabeesh k
#6 - 2pt


On Wed, Jun 11, 2014 at 3:34 PM, Vinoth Kumar Kannan vinot...@gmail.com
wrote:

 #9 - 5 pts


 On Wed, Jun 11, 2014 at 11:43 AM, B Kersbergen kersberg...@gmail.com
 wrote:

 #6 - 5 pts.

 2014-06-11 4:02 GMT+02:00 Corey Nolet cjno...@gmail.com:
  6 - 1pt
  9 - 4pt
 
 
  On Tue, Jun 10, 2014 at 8:34 PM, Nathan Leung ncle...@gmail.com
 wrote:
 
  #10 - 5
 
 
  On Tue, Jun 10, 2014 at 5:56 PM, Osman osmans...@gmail.com wrote:
 
  9 5
 
  On Jun 9, 2014 7:39 PM, P. Taylor Goetz ptgo...@gmail.com wrote:
 
  This is a call to vote on selecting the winning Storm logo from the 3
  finalists.
 
  The three candidates are:
 
   * [No. 6 - Alec
  Bartos](
 http://storm.incubator.apache.org/2014/04/23/logo-abartos.html)
   * [No. 9 - Jennifer
  Lee](http://storm.incubator.apache.org/2014/04/29/logo-jlee1.html)
   * [No. 10 - Jennifer
  Lee](http://storm.incubator.apache.org/2014/04/29/logo-jlee2.html)
 
  VOTING
 
  Each person can cast a single vote. A vote consists of 5 points that
 can
  be divided among multiple entries. To vote, list the entry number,
 followed
  by the number of points assigned. For example:
 
  #1 - 2 pts.
  #2 - 1 pt.
  #3 - 2 pts.
 
  Votes cast by PPMC members are considered binding, but voting is
 open to
  anyone. In the event of a tie vote from the PPMC, votes from the
 community
  will be used to break the tie.
 
  This vote will be open until Monday, June 16 11:59 PM UTC.
 
  - Taylor
 
 
 




 --
 With Regards,
 Vinoth Kumar K



Impossible to create new topic on the google group

2014-06-11 Thread Benjamin SOULAS
Hello,

I just join the google group and the mailing list. I would like to create a
topic on the google group, but apparently, I can't, could you tell me why?

Thanks.

Benjamin.


RE: Impossible to create new topic on the google group

2014-06-11 Thread Jean-Sebastien Vachon
I believed this is due to the integration with Apache. They have to follow a 
certain standard which implies using a mailing-list…

From: Benjamin SOULAS [mailto:benjamin.soula...@gmail.com]
Sent: June-11-14 7:25 AM
To: user@storm.incubator.apache.org
Subject: Impossible to create new topic on the google group

Hello,

I just join the google group and the mailing list. I would like to create a 
topic on the google group, but apparently, I can't, could you tell me why?

Thanks.

Benjamin.

Aucun virus trouvé dans ce message.
Analyse effectuée par AVG - www.avg.frhttp://www.avg.fr
Version: 2014.0.4570 / Base de données virale: 3950/7571 - Date: 27/05/2014
La Base de données des virus a expiré.


Non-DRPC topologies and number of assigned workers

2014-06-11 Thread Nima Movafaghrad
Hi Community,

 

Wondering if a non-drpc topology can run in multiple workers or is it just 
gonna run within one?

 

Thanks,

Nima


Python - When spout dies, bolts keep receiving input on STDIN

2014-06-11 Thread Scot Kronenfeld
I am using Storm w/ my bolts and spouts written in Python.

When I am running in a test environment locally I have a problem where if
the spout dies, the bolts consume 100% CPU and gradually increase their
memory.  Here are the details:

My spout is reading from mongo.  Sometimes it loses its cursor (due to a
network hiccup or something) and it raises an exception and bails out.  I
can also reliably reproduce this problem by using kill -9 spout PID.

Using strace and then a debugger, I figured out that the bolts are stuck in
this tight loop in the readMsg function inside storm.py (which ships with
storm)

while True:
line = sys.stdin.readline()[:-1]
if line == end:
break
msg = msg + line + \n

The readline() call is a blocking call, but the bolt keeps getting blank
lines as input.

Note: the memory problem is because newlines keep getting appended.  Since
the input is used as JSON, it would probably be safe to just remove the
addition of the newline (I'm not 100% positive because that might not work
if there are newlines in an embedded string within the JSON).  But that
still doesn't fix the core issue.

I think the problem is that if the spout does not come down cleanly,
something in the Java keeps sending input to the bolts.  I'm about to dig
into the Java code but I don't know any Java so I figured it was worth a
quick message to the Storm list to see if this is a known problem.  Or even
if anyone has a pointer for where to look in the Java.  I haven't
previously looked at the Storm source - it's just been a black box to this
point for me.

Thanks,
scot


Re: Non-DRPC topologies and number of assigned workers

2014-06-11 Thread Michael Rose
A topology can run in as many workers as you assign at launch time, DRPC or
not.

Michael Rose (@Xorlev https://twitter.com/xorlev)
Senior Platform Engineer, FullContact http://www.fullcontact.com/
mich...@fullcontact.com


On Wed, Jun 11, 2014 at 1:08 PM, Nima Movafaghrad 
nima.movafagh...@oracle.com wrote:

 Hi Community,



 Wondering if a non-drpc topology can run in multiple workers or is it just
 gonna run within one?



 Thanks,

 Nima



Re: Getting Exception in kafka-storm

2014-06-11 Thread Michael G. Noll
Can you share your build depencies, notably the versions of Storm and
storm-kafka and their respective artifactId and groupId?   That is, the
snippets relevant to storm-core and storm-kafka from your pom.xml,
build.gradle, build.sbt, or similar build configuration file.  Also,
please add from which Maven repositories you are downloading storm-core
and storm-kafka, respectively.

Best,
Michael



On 06/11/2014 09:52 PM, Anis Nasir wrote:
 Dear all,
 
 
 I am getting below mentioned exception while running storm-kafka. Does
 anyone have seen this one before?
 
 
 7800 [Thread-27-words] ERROR backtype.storm.util - Async loop died!
 java.lang.NoSuchMethodError:
 com.netflix.curator.framework.api.CreateBuilder.creatingParentsIfNeeded()Lcom/netflix/curator/framework/api/ProtectACLCreateModePathAndBytesable;
 at storm.kafka.ZkState.writeBytes(ZkState.java:59)
 ~[storm-kafka-0.8-plus-0.5.0-SNAPSHOT.jar:na]
 at storm.kafka.ZkState.writeJSON(ZkState.java:53)
 ~[storm-kafka-0.8-plus-0.5.0-SNAPSHOT.jar:na]
 at storm.kafka.PartitionManager.commit(PartitionManager.java:188)
 ~[storm-kafka-0.8-plus-0.5.0-SNAPSHOT.jar:na]
 at storm.kafka.KafkaSpout.commit(KafkaSpout.java:169)
 ~[storm-kafka-0.8-plus-0.5.0-SNAPSHOT.jar:na]
 at storm.kafka.KafkaSpout.nextTuple(KafkaSpout.java:134)
 ~[storm-kafka-0.8-plus-0.5.0-SNAPSHOT.jar:na]
 at
 backtype.storm.daemon.executor$fn__3430$fn__3445$fn__3474.invoke(executor.clj:547)
 ~[storm-core-0.9.0.1.jar:na]
 at backtype.storm.util$async_loop$fn__444.invoke(util.clj:403)
 ~[storm-core-0.9.0.1.jar:na]
 at clojure.lang.AFn.run(AFn.java:24) ~[clojure-1.4.0.jar:na]
 at java.lang.Thread.run(Thread.java:701) ~[na:1.6.0_30]
 7800 [Thread-27-words] ERROR backtype.storm.daemon.executor - 
 java.lang.NoSuchMethodError:
 com.netflix.curator.framework.api.CreateBuilder.creatingParentsIfNeeded()Lcom/netflix/curator/framework/api/ProtectACLCreateModePathAndBytesable;
 at storm.kafka.ZkState.writeBytes(ZkState.java:59)
 ~[storm-kafka-0.8-plus-0.5.0-SNAPSHOT.jar:na]
 at storm.kafka.ZkState.writeJSON(ZkState.java:53)
 ~[storm-kafka-0.8-plus-0.5.0-SNAPSHOT.jar:na]
 at storm.kafka.PartitionManager.commit(PartitionManager.java:188)
 ~[storm-kafka-0.8-plus-0.5.0-SNAPSHOT.jar:na]
 at storm.kafka.KafkaSpout.commit(KafkaSpout.java:169)
 ~[storm-kafka-0.8-plus-0.5.0-SNAPSHOT.jar:na]
 at storm.kafka.KafkaSpout.nextTuple(KafkaSpout.java:134)
 ~[storm-kafka-0.8-plus-0.5.0-SNAPSHOT.jar:na]
 at
 backtype.storm.daemon.executor$fn__3430$fn__3445$fn__3474.invoke(executor.clj:547)
 ~[storm-core-0.9.0.1.jar:na]
 at backtype.storm.util$async_loop$fn__444.invoke(util.clj:403)
 ~[storm-core-0.9.0.1.jar:na]
 at clojure.lang.AFn.run(AFn.java:24) ~[clojure-1.4.0.jar:na]
 at java.lang.Thread.run(Thread.java:701) ~[na:1.6.0_30]
 
 Regards
 Anis



Re: Getting Exception in kafka-storm

2014-06-11 Thread János Háber
Anis: no, you using snapshot version of storm-kafka plugin plus the old
storm kafka plugin with storm 0.9.1...
I think storm-kafka 0.9.2-incubating-SNAPSHOT only compatible with
storm-core 0.9.2-incubating-SNAPSHOT

In the 0.9.2-incubating-SNAPSHOT old curator framework (1.0.1) will be
changed to more recent version...

as you see you using two version of storm-kafka. Remove the old one (the
0.4.0 version) and increase the storm-core version
to 0.9.2-incubating-SNAPSHOT...

maybe it's help...

b0c1

János Háber
Fine Solution Ltd



On Wed, Jun 11, 2014 at 11:03 PM, Anis Nasir aadi.a...@gmail.com wrote:

 Dear Michael,

 I am using storm0.9.0.1 with kafka 0.8.1.1 and below mentioned are the
 dependencies. I tried with both storm-kafka 0.9.2-incubating-SNAPSHOT and 
 storm-kafka-0.8-plus
 0.4.0. The zookeeper version is 3.3.6.

 dependency
   groupIdorg.apache.storm/groupId
   artifactIdstorm-core/artifactId
   version0.9.1-incubating/version
 /dependency

  dependency
  groupIdorg.apache.storm/groupId
  artifactIdstorm-kafka/artifactId
  version0.9.2-incubating-SNAPSHOT/version
 /dependency

   dependency
 groupIdnet.wurstmeister.storm/groupId
 artifactIdstorm-kafka-0.8-plus/artifactId
 version0.4.0/version
   /dependency

 Regards
 Anis



 On Wed, Jun 11, 2014 at 10:51 PM, Michael G. Noll 
 michael+st...@michael-noll.com wrote:

 Can you share your build depencies, notably the versions of Storm and
 storm-kafka and their respective artifactId and groupId?   That is, the
 snippets relevant to storm-core and storm-kafka from your pom.xml,
 build.gradle, build.sbt, or similar build configuration file.  Also,
 please add from which Maven repositories you are downloading storm-core
 and storm-kafka, respectively.

 Best,
 Michael



 On 06/11/2014 09:52 PM, Anis Nasir wrote:
  Dear all,
 
 
  I am getting below mentioned exception while running storm-kafka. Does
  anyone have seen this one before?
 
 
  7800 [Thread-27-words] ERROR backtype.storm.util - Async loop died!
  java.lang.NoSuchMethodError:
 
 com.netflix.curator.framework.api.CreateBuilder.creatingParentsIfNeeded()Lcom/netflix/curator/framework/api/ProtectACLCreateModePathAndBytesable;
  at storm.kafka.ZkState.writeBytes(ZkState.java:59)
  ~[storm-kafka-0.8-plus-0.5.0-SNAPSHOT.jar:na]
  at storm.kafka.ZkState.writeJSON(ZkState.java:53)
  ~[storm-kafka-0.8-plus-0.5.0-SNAPSHOT.jar:na]
  at storm.kafka.PartitionManager.commit(PartitionManager.java:188)
  ~[storm-kafka-0.8-plus-0.5.0-SNAPSHOT.jar:na]
  at storm.kafka.KafkaSpout.commit(KafkaSpout.java:169)
  ~[storm-kafka-0.8-plus-0.5.0-SNAPSHOT.jar:na]
  at storm.kafka.KafkaSpout.nextTuple(KafkaSpout.java:134)
  ~[storm-kafka-0.8-plus-0.5.0-SNAPSHOT.jar:na]
  at
 
 backtype.storm.daemon.executor$fn__3430$fn__3445$fn__3474.invoke(executor.clj:547)
  ~[storm-core-0.9.0.1.jar:na]
  at backtype.storm.util$async_loop$fn__444.invoke(util.clj:403)
  ~[storm-core-0.9.0.1.jar:na]
  at clojure.lang.AFn.run(AFn.java:24) ~[clojure-1.4.0.jar:na]
  at java.lang.Thread.run(Thread.java:701) ~[na:1.6.0_30]
  7800 [Thread-27-words] ERROR backtype.storm.daemon.executor -
  java.lang.NoSuchMethodError:
 
 com.netflix.curator.framework.api.CreateBuilder.creatingParentsIfNeeded()Lcom/netflix/curator/framework/api/ProtectACLCreateModePathAndBytesable;
  at storm.kafka.ZkState.writeBytes(ZkState.java:59)
  ~[storm-kafka-0.8-plus-0.5.0-SNAPSHOT.jar:na]
  at storm.kafka.ZkState.writeJSON(ZkState.java:53)
  ~[storm-kafka-0.8-plus-0.5.0-SNAPSHOT.jar:na]
  at storm.kafka.PartitionManager.commit(PartitionManager.java:188)
  ~[storm-kafka-0.8-plus-0.5.0-SNAPSHOT.jar:na]
  at storm.kafka.KafkaSpout.commit(KafkaSpout.java:169)
  ~[storm-kafka-0.8-plus-0.5.0-SNAPSHOT.jar:na]
  at storm.kafka.KafkaSpout.nextTuple(KafkaSpout.java:134)
  ~[storm-kafka-0.8-plus-0.5.0-SNAPSHOT.jar:na]
  at
 
 backtype.storm.daemon.executor$fn__3430$fn__3445$fn__3474.invoke(executor.clj:547)
  ~[storm-core-0.9.0.1.jar:na]
  at backtype.storm.util$async_loop$fn__444.invoke(util.clj:403)
  ~[storm-core-0.9.0.1.jar:na]
  at clojure.lang.AFn.run(AFn.java:24) ~[clojure-1.4.0.jar:na]
  at java.lang.Thread.run(Thread.java:701) ~[na:1.6.0_30]
 
  Regards
  Anis





Re: Getting Exception in kafka-storm

2014-06-11 Thread Anis Nasir
Regarding, 0.9.2-incubating-SNAPSHOT, it comes with the interface
ILocalCluster. I can not find any example using it.

Regards
Anis


On Wed, Jun 11, 2014 at 11:14 PM, Anis Nasir aadi.a...@gmail.com wrote:

 Dear Jonas,

 I am getting the same exception running this build

 https://github.com/wurstmeister/storm-kafka-0.8-plus-test



 Regards
 Anis


 On Wed, Jun 11, 2014 at 11:07 PM, János Háber janos.ha...@finesolution.hu
  wrote:

 Anis: no, you using snapshot version of storm-kafka plugin plus the old
 storm kafka plugin with storm 0.9.1...
 I think storm-kafka 0.9.2-incubating-SNAPSHOT only compatible with
 storm-core 0.9.2-incubating-SNAPSHOT

 In the 0.9.2-incubating-SNAPSHOT old curator framework (1.0.1) will be
 changed to more recent version...

 as you see you using two version of storm-kafka. Remove the old one (the
 0.4.0 version) and increase the storm-core version
 to 0.9.2-incubating-SNAPSHOT...

 maybe it's help...

 b0c1

 János Háber
 Fine Solution Ltd



 On Wed, Jun 11, 2014 at 11:03 PM, Anis Nasir aadi.a...@gmail.com wrote:

 Dear Michael,

 I am using storm0.9.0.1 with kafka 0.8.1.1 and below mentioned are the
 dependencies. I tried with both storm-kafka 0.9.2-incubating-SNAPSHOT
 and storm-kafka-0.8-plus 0.4.0. The zookeeper version is 3.3.6.

 dependency
   groupIdorg.apache.storm/groupId
   artifactIdstorm-core/artifactId
   version0.9.1-incubating/version
 /dependency

  dependency
  groupIdorg.apache.storm/groupId
  artifactIdstorm-kafka/artifactId
  version0.9.2-incubating-SNAPSHOT/version
 /dependency

   dependency
 groupIdnet.wurstmeister.storm/groupId
 artifactIdstorm-kafka-0.8-plus/artifactId
 version0.4.0/version
   /dependency

 Regards
 Anis



 On Wed, Jun 11, 2014 at 10:51 PM, Michael G. Noll 
 michael+st...@michael-noll.com wrote:

 Can you share your build depencies, notably the versions of Storm and
 storm-kafka and their respective artifactId and groupId?   That is, the
 snippets relevant to storm-core and storm-kafka from your pom.xml,
 build.gradle, build.sbt, or similar build configuration file.  Also,
 please add from which Maven repositories you are downloading storm-core
 and storm-kafka, respectively.

 Best,
 Michael



 On 06/11/2014 09:52 PM, Anis Nasir wrote:
  Dear all,
 
 
  I am getting below mentioned exception while running storm-kafka. Does
  anyone have seen this one before?
 
 
  7800 [Thread-27-words] ERROR backtype.storm.util - Async loop died!
  java.lang.NoSuchMethodError:
 
 com.netflix.curator.framework.api.CreateBuilder.creatingParentsIfNeeded()Lcom/netflix/curator/framework/api/ProtectACLCreateModePathAndBytesable;
  at storm.kafka.ZkState.writeBytes(ZkState.java:59)
  ~[storm-kafka-0.8-plus-0.5.0-SNAPSHOT.jar:na]
  at storm.kafka.ZkState.writeJSON(ZkState.java:53)
  ~[storm-kafka-0.8-plus-0.5.0-SNAPSHOT.jar:na]
  at storm.kafka.PartitionManager.commit(PartitionManager.java:188)
  ~[storm-kafka-0.8-plus-0.5.0-SNAPSHOT.jar:na]
  at storm.kafka.KafkaSpout.commit(KafkaSpout.java:169)
  ~[storm-kafka-0.8-plus-0.5.0-SNAPSHOT.jar:na]
  at storm.kafka.KafkaSpout.nextTuple(KafkaSpout.java:134)
  ~[storm-kafka-0.8-plus-0.5.0-SNAPSHOT.jar:na]
  at
 
 backtype.storm.daemon.executor$fn__3430$fn__3445$fn__3474.invoke(executor.clj:547)
  ~[storm-core-0.9.0.1.jar:na]
  at backtype.storm.util$async_loop$fn__444.invoke(util.clj:403)
  ~[storm-core-0.9.0.1.jar:na]
  at clojure.lang.AFn.run(AFn.java:24) ~[clojure-1.4.0.jar:na]
  at java.lang.Thread.run(Thread.java:701) ~[na:1.6.0_30]
  7800 [Thread-27-words] ERROR backtype.storm.daemon.executor -
  java.lang.NoSuchMethodError:
 
 com.netflix.curator.framework.api.CreateBuilder.creatingParentsIfNeeded()Lcom/netflix/curator/framework/api/ProtectACLCreateModePathAndBytesable;
  at storm.kafka.ZkState.writeBytes(ZkState.java:59)
  ~[storm-kafka-0.8-plus-0.5.0-SNAPSHOT.jar:na]
  at storm.kafka.ZkState.writeJSON(ZkState.java:53)
  ~[storm-kafka-0.8-plus-0.5.0-SNAPSHOT.jar:na]
  at storm.kafka.PartitionManager.commit(PartitionManager.java:188)
  ~[storm-kafka-0.8-plus-0.5.0-SNAPSHOT.jar:na]
  at storm.kafka.KafkaSpout.commit(KafkaSpout.java:169)
  ~[storm-kafka-0.8-plus-0.5.0-SNAPSHOT.jar:na]
  at storm.kafka.KafkaSpout.nextTuple(KafkaSpout.java:134)
  ~[storm-kafka-0.8-plus-0.5.0-SNAPSHOT.jar:na]
  at
 
 backtype.storm.daemon.executor$fn__3430$fn__3445$fn__3474.invoke(executor.clj:547)
  ~[storm-core-0.9.0.1.jar:na]
  at backtype.storm.util$async_loop$fn__444.invoke(util.clj:403)
  ~[storm-core-0.9.0.1.jar:na]
  at clojure.lang.AFn.run(AFn.java:24) ~[clojure-1.4.0.jar:na]
  at java.lang.Thread.run(Thread.java:701) ~[na:1.6.0_30]
 
  Regards
  Anis







using CachedMap in a trident state

2014-06-11 Thread Raphael Hsieh
I am imitating the MemCachedState class found here:
https://github.com/nathanmarz/trident-memcached/blob/master/src/jvm/trident/memcached/MemcachedState.java
.

I was wondering what the CachedMap is used for. I see that it creates a
cache layer between the final datastore in order to retrieve values much
quicker than accessing the datastore every time, however I am unsure about
a couple details.

Is this cache replicated among all hosts? When I do a 'multiGet' I expect
to retrieve data I had previously stored. If the cache is specific to each
host, I wouldn't necessarily get the same data I had most recently stored.

Also, how does this work with Opaque Transactional consistency? It seems
that in the MemCachedState example we serialize the data once we store it
to the external datastore, however the data in the cache is not serialized.
why is this?
Shouldn't the local cache have the same data as the external datastore ?

thanks
-- 
Raphael Hsieh


Re: [VOTE] Storm Logo Contest - Final Round

2014-06-11 Thread Eugene
#6 - 5pts


On Wed, Jun 11, 2014 at 6:13 AM, prabeesh k prabsma...@gmail.com wrote:

 #6 - 2pt


 On Wed, Jun 11, 2014 at 3:34 PM, Vinoth Kumar Kannan vinot...@gmail.com
 wrote:

 #9 - 5 pts


 On Wed, Jun 11, 2014 at 11:43 AM, B Kersbergen kersberg...@gmail.com
 wrote:

 #6 - 5 pts.

 2014-06-11 4:02 GMT+02:00 Corey Nolet cjno...@gmail.com:
  6 - 1pt
  9 - 4pt
 
 
  On Tue, Jun 10, 2014 at 8:34 PM, Nathan Leung ncle...@gmail.com
 wrote:
 
  #10 - 5
 
 
  On Tue, Jun 10, 2014 at 5:56 PM, Osman osmans...@gmail.com wrote:
 
  9 5
 
  On Jun 9, 2014 7:39 PM, P. Taylor Goetz ptgo...@gmail.com wrote:
 
  This is a call to vote on selecting the winning Storm logo from the
 3
  finalists.
 
  The three candidates are:
 
   * [No. 6 - Alec
  Bartos](
 http://storm.incubator.apache.org/2014/04/23/logo-abartos.html)
   * [No. 9 - Jennifer
  Lee](http://storm.incubator.apache.org/2014/04/29/logo-jlee1.html)
   * [No. 10 - Jennifer
  Lee](http://storm.incubator.apache.org/2014/04/29/logo-jlee2.html)
 
  VOTING
 
  Each person can cast a single vote. A vote consists of 5 points
 that can
  be divided among multiple entries. To vote, list the entry number,
 followed
  by the number of points assigned. For example:
 
  #1 - 2 pts.
  #2 - 1 pt.
  #3 - 2 pts.
 
  Votes cast by PPMC members are considered binding, but voting is
 open to
  anyone. In the event of a tie vote from the PPMC, votes from the
 community
  will be used to break the tie.
 
  This vote will be open until Monday, June 16 11:59 PM UTC.
 
  - Taylor
 
 
 




 --
 With Regards,
 Vinoth Kumar K





-- 
Eugene Dvorkin
Software Engineer
New York City Storm User Group - organizer
WebMD
email: edvor...@gmail.com
phone: 646-250-9649
eugenedvorkin.com
Connect with me on:
LinkedIn http://www.linkedin.com/in/eugenedvorkin Twitter
http://twitter.com/edvorkin


Re: Client is being closed, and does not take requests any more

2014-06-11 Thread Xing Yong
@Neelesh,thanks,i will make some try on 0.9.2.


2014-06-11 5:41 GMT+08:00 Neelesh neele...@gmail.com:

 Sean, Unfortunately, I did not retain the full log and upgraded to the
 master branch (0.9.2). That seems to have fixed the issue. Xing Yong, the
 setting you mentioned is already at 1ms. Not sure that would help. I
 saw that  Reconnecting... retry log messages went away with 0.9.2 ,
 without any configuration change

 thanks!


 On Mon, Jun 9, 2014 at 5:35 PM, Sean Zhong clock...@gmail.com wrote:

 Neelesh,

 Can you post full worker log on this?

 Sean

 On Tue, Jun 10, 2014 at 5:44 AM, Neelesh neele...@gmail.com wrote:

 Client is being closed, and does not take requests any more