I also tried setting option for nimbus_uptime_secs
COMMAND:
sparse submit -o "nimbus_uptime_secs=5"
Still facing the same issue.
On Tue, Jul 12, 2016 at 3:57 PM, ram kumar wrote:
> Hi all,
>
> I am trying to run storm topology in production mode,
>
> project.clj
Hi all,
I am trying to run storm topology in production mode,
project.clj
(defproject meta "0.0.1-SNAPSHOT"
:source-paths ["topologies"]
:resource-paths ["_resources"]
:target-path "_build"
:min-lein-version "2.0.0"
:jvm-opts ["-client"]
:dependencies [[org.apache.storm/storm-core "0
Kafka and wait for response infinitely.
>
> - Jungtaek Lim (HeartSaVioR)
>
> 2016년 6월 23일 (목) 오후 7:25, cogumelosmaravilha 님이
> 작성:
>
>> Yes, but if you submit to Storm, it's ok, with or without an empty Kafka.
>>
>>
>> On 23-06-2016 10:40, ram kumar w
<
cogumelosmaravi...@sapo.pt> wrote:
> Hi,
>
> It happens to me to, but only when my kafka is empy.
> I'm using Petrel because the generated jar file is really small like 300k
> Petrel vs 16M Streamparse.
>
>
> On 23-06-2016 08:05, ram kumar wrote:
>
> H
Hi,
*Version:*
Storm : 0.10.0
Streamparse : 2.1.4
I am running a storm topology with a python streamparse "sparse run".
This topology stops executing in the middle and throw an exception
158031 [pool-37-thread-1] ERROR b.s.s.ShellSpout - Halting process:
> ShellSpout died.
> java.lan
nished submitting topology: data*
$
}}}
Then I produced message to Kafka broker
But, I can't see the logs for the topology "data"
in /home/ram/log/storm/streamparse
How will I check the submitted topology's logs
Thanks
On Thu, May 19, 2016 at 12:29 AM, cogumelosmaravilha <
cog
Hi,
I tried to submit a storm topology in production mode (streamparse)
$ *sparse submit*
Cleaning from prior builds...
Creating topology Uber-JAR...
Uber-JAR created:
/home/ram/PYTHON/test/_build/Data-0.0.1-SNAPSHOT-standalone.jar
Deploying "customer-metadata" topology...
Traceback (most recen
