Hello,
I am using storm version 0.9.0.1.
My application depends on apache http-client version 4.3.2 - but storm
depends on http-client version 4.1.1.
What is the best way to override this dependency?
Thanks
Vinay
n on using the shade plugin to do package relocations can
> be found here:
>
>
> http://maven.apache.org/plugins/maven-shade-plugin/examples/class-relocation.html
>
> - Taylor
>
> On Feb 4, 2014, at 4:27 PM, Vinay Pothnis wrote:
>
> > Hello,
> >
> > I am using
he/incubator-storm/blob/master/storm-core/pom.xml#L220
>>>
>>> (You can ignore the clojure transformer in that config, unless you have
>>> non-AOT clojure code that uses the http-client library).
>>>
>>> More information on using the shade plugin to do
relocating some of their
>> dependencies [1] (not necessarily an endorsement, just an observation).
>>
>> I've CC'd dev@ since this is all related to the infamous issue #115,
>> which is now STORM-129 [2].
>>
>> - Taylor
>>
>> [1]
>> http
Hello,
I have a storm cluster of 3 nodes and a topology with 3 workers. I have
rabbit-mq from which I read messages and also post back to a queue.
I seem to get this exception when I am using more than 1 worker. When I
have just 1 worker, I do not get this exception. But when i change it to 3
wor
"topology.debug = true" - but the logs dont contain
any other useful information.
Any idea how to troubleshoot this?
Thanks!
Vinay
On Fri, Mar 21, 2014 at 3:07 PM, Vinay Pothnis wrote:
> Hello,
>
> I have a storm cluster of 3 nodes and a topology with 3 workers. I have
>
QConnection.java#75>into
> the tuple.
>
> Regards,
> Srinath.
>
>
>
> On Sat, Mar 22, 2014 at 4:56 AM, Vinay Pothnis wrote:
>
>> Hello,
>>
>> This seems to happen when the spout and the bolt are on different JVMs
>> (worker process) - whic
there which would
> need some other serializer (read custom serializer), for which have a look
> at kryo docs which are pretty good.
>
>
> -Samit
>
>
> On Sat, Mar 22, 2014 at 9:42 AM, Vinay Pothnis wrote:
>
>> Thank you Srinath,
>>
>> Will check that ou
vate
inner class. It was public before but in the latest versions of the library
this is private. So, I might not be able to write a custom serializer as
well.
Any pointers as to how to resolve this issue?
Thanks
Vinay
On Sun, Mar 23, 2014 at 8:26 AM, Vinay Pothnis wrote:
> Thank you Samit,
&g
ct and use that instead.
>
> -Samit
> On Tue, Mar 25, 2014 at 2:38 AM, Vinay Pothnis wrote:
>
>> com.rabbitmq.client.impl.LongStringHelper$ByteArrayLongString
>
>
>
>
ializers.add(Collections.singletonMap(
> "com.google.common.collect.RegularImmutableList", SerializableSerializer.
> class.getName()));
>
>
>
>
> On Tue, Mar 25, 2014 at 11:56 AM, Vinay Pothnis
> wrote:
>
>> Naresh,
>>
>> Cannot do that in code because the I cannot reference the private c
This change did not help much. I still got the exception. We got an updated
storm-rabbitmq library. So, trying out with the newer version. Will report
back how this goes.
On Tue, Mar 25, 2014 at 12:06 PM, Vinay Pothnis wrote:
> oh cool! Will give this a try. Thank you!
>
>
> On
Hello,
I have a storm cluster with 5 nodes and spouts reading from RabbitMQ
source. I am seeing a strange behaviour where some of the tuples are
failing and getting redelivered from RabbitMQ.
The logs on the individual storm nodes do not have any exceptions and no
obvious indicators. I believe I
.
Thanks
Vinay
On Fri, Jul 11, 2014 at 8:28 AM, Vinay Pothnis
wrote:
> Hello,
>
> I have a storm cluster with 5 nodes and spouts reading from RabbitMQ
> source. I am seeing a strange behaviour where some of the tuples are
> failing and getting redelivered from RabbitMQ.
>
[Storm Version: 0.9.2-incubating]
Hello,
I am trying to test failover scenarios with my storm cluster. The following
are the details of the cluster:
* 4 nodes
* Each node with 2 slots
* Topology with around 600 spouts and bolts
* Num. Workers for the topology = 4
I am running a test that genera
2] https://github.com/aphyr/jepsen
>
> On Aug 5, 2014, at 8:39 PM, Srinath C wrote:
>
> I have seen this behaviour too using 0.9.2-incubating.
> The failover works better when there is a redundant node available. Maybe
> 1 slot per node is the best approach.
> Eager to know if
onEvent(disruptor.clj:58)
~[storm-core-0.9.2-incubating.jar:0.9.2-incubating]*
* at
backtype.storm.utils.DisruptorQueue.consumeBatchToCursor(DisruptorQueue.java:125)
~[storm-core-0.9.2-incubating.jar:0.9.2-incubating]*
* ... 6 common frames omitted*
On Wed, Aug 6, 2014 at 9:02 AM, Vinay Poth
17 matches
Mail list logo
