Thanks for your time and help , i solved it by update my RAM to be 8 GB
instead of 4 GB
On Tue, Apr 19, 2016 at 2:41 AM, sam mohel wrote:
> I want to take your opinion , Should i increase RAM of my laptop , is that
> a good solution for GC OOM ?
>
> Thanks
>
> On Sat, Apr 16, 2016 at 11:36 PM,
@Vijay: Memory is static. It is not per-bolt, it is just loading some large
datasets. Refactoring is certainly an option but will require plenty of code
changes and will also cause a lot of data to be transferred over wire.
@John That is correct. But, the scenario is a bit different. I have
mongoManager is serialized and sent to your spout. If it's not something
that's easily serializable (e.g. a database connection) then you will need
to initialize it in spout prepare() instead of the constructor.
On Thu, Apr 21, 2016 at 7:34 AM, Navin Ipe
wrote:
> Thanks John, but that's odd...i
Thanks John, but that's odd...in the code I shared, there's a reference to
mongoManager being used in the Spout (the MongoSpout internally stores a
reference to mongoManager). If there are no object references shared
between executors, then when the topology I created is submitted to Storm,
would S
That's interesting. When I match the number of executors to the number of
workers, I always get exactly one executor per worker, at least with versions
0.9.4-0.9.6.
--John
Sent from my iPhone
> On Apr 21, 2016, at 12:19 AM, Vijay Patil wrote:
>
> If your topology is the only topology runnin
Netty is used for communication between workers and then the LMAX disruptor
queue is used to route messages between Netty and the individual executors such
as the MongoSpout and KafkaBolt. AFAIK, there are not direct object references
shared between executors because all executors communicate vi
That is possible, as long as the default scheduler is allowed to deploy
topologies to **all** servers (ie, your special servers are available to
default scheduler, too).
(At least I think no, maybe it is even possible to exclude your special
servers -- see comment below.)
For this, you can instan
Hi,
As Matthias says, you need to implement your own scheduler and use some
metadata in the storm.yaml file. This link is a good starting point:
https://dcvan24.wordpress.com/2015/04/07/metadata-aware-custom-scheduler-in-storm/
What I haven't been able to do yet it is to mix a customized schedule
For this, you need to provide a custom scheduler. Just search the
Internet for example how to do this.
Keep in mind, that a custom scheduler will not easily allow you to
**move** topologies after they are deployed... But you can control to
which servers you want to deploy a topology.
-Matthias
Hi all.
Do someone have working way to move topologies between servers or up
topology on specific server? Is it possible?
--
С уважением Дудин Андрей
@Deepak: In the first email of this thread I had shown the code I was
trying to use. MongoDatabaseManager is serialized and I've even tried using
it as an empty class but it didn't work, which is why I asked on the
mailing list. Since it's a tiny piece of code, you could also try it out on
your sys
11 matches
Mail list logo