Hi,
Sounds like you didn't stop the node. Use ignite.close() or Ignition.stop()
to achieve this.
Let us know if it helps.
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/How-to-exit-from-Client-JVM-while-using-Apache-Ignite-as-Data-Grid-tp3919p3954.html
According to the trace you provided earlier, a different constructor was used
to create the IgniteContext (the one that takes URL to XML file or the one
that takes only SparkContext). Can you please double check you code?
Probably you do this somewhere else?
If you have a small example that
Hi,
Your node has less than 1GB of heap memory (see the line below). Please
allocate proper amount of heap to the server nodes, as Alexey suggested.
^-- Heap [used=528MB, free=42.03%, comm=911MB]
In addition, if you're going to have more than 10 GB of data per node, I
would recommend to use
Hi!
Are you sure that your JVM is started with arguments like this: -Xms50g
-Xmx50g ?
By default ignite.sh starts node with 1Gb of heap.
You may configure $JVM_OPTS variable with you JVM settings or start like
this "ignite.sh -J-Xms50g -Xmx50g"
On Wed, Apr 6, 2016 at 8:27 AM, F7753
Hi,Client programme is my java code/app from where I am trying to access the
ignite cache.Its just a java programme which should be finished after doing its
work and jvm should got shutdown.Regards,Vij
Sent from Yahoo Mail on Android
On Tue, 5 Apr, 2016 at 2:10 pm, Denis
Thanks a lot to let me know that. I think I'd use some time to refer to the
ignite doc more carefully.
And I created another topic about the GC OOM in my cluster:
http://apache-ignite-users.70518.x6.nabble.com/How-to-end-up-the-GC-overhead-problem-in-the-IgniteRDD-tc3945.html
--
View this
Is there some configuration I can use to monitor the GC behavior in the
ignite?
It is curious that a OOM happens on a node with more than 100GB RAM.
--
View this message in context:
Hi agura,
I refer to the source code of IgniteContext.scala, and notified that the
ignite method will do "Ignition.start()" in a try-catch block.
And the code I use is listed in this topic:
There is nothing more different from the code I show in the 6th comments in
this topic, only the initialization of igniteContext, I also list the way I
create it in the above comnents:
--
val
I run a spark streaming app in a ignite cluster overlap with a spark
cluster(the server node of the ignite is also the worker node of the spark),
the monitor page shows that only one task can success, then after a while an
OOM error will be throwed
Following up on this...
Sorry for the vague description of the problem, but we are experiencing
objects "going null" (as if they were garbage collected?) in our clustered
singleton.
We have an instance variable of an object that is initialized in the service
init() method. We have confirmed that
Hi,
You should not call Ignition.start(). Ignite instance will be started
during creation of IgniteContext.
Could you please provide code snippet that creates IgniteContext or minimal
reproducer example if possible?
On Sat, Apr 2, 2016 at 8:42 AM, F7753 wrote:
> What
akriti91 wrote
> could you tell me if there is a way to download these JARs separately?
All JARs are included in binary build under 'libs' folder. It can be
downloaded here: https://ignite.apache.org/download.cgi#binaries
-Val
--
View this message in context:
Ohh..missed that..sorry...thanks for the clarification.
On Tue, Apr 5, 2016 at 7:09 AM, Pavel Tupitsyn
wrote:
> Please see my reply above. Yes, you can set IGNITE_H2_DEBUG_CONSOLE
> environment
> variable to open the console from .NET.
>
> On Tue, Apr 5, 2016 at 1:32
I found that GC was the main problem in my circumstance, each of my node
throws the GC exception:
Exception in thread "shmem-worker-#175%null%" java.lang.OutOfMemoryError: GC
overhead
Please see my reply above. Yes, you can set IGNITE_H2_DEBUG_CONSOLE environment
variable to open the console from .NET.
On Tue, Apr 5, 2016 at 1:32 PM, Murthy Kakarlamudi wrote:
> Hi Pavel...Yes the solution you suggested is working. Thanks so much for
> your help.
>
>
Hi Tolga,
Probably you can use SqlQuery as is by getting a list of keys that have
to be updated with"SELECT _key FROM cache2 WHERE ..." where "_key" is
Ignite specific keyword saying that entries key has to be included into
the result set.
However since SqlQueries are broadcasted to every
Hi,
Please elaborate on what you mean under "But my client program is not
getting exiting, it keeps on running."
How do you stop the client and your application? Why do you expect that it
should be stopped?
If you start a client node it will start internally pools of non daemon
Threads that
Hi Prabuddha,
Cache.get() operation returns copy of an object stored in a cache by
default. If you set CacheConfiguration.setCopyOnRead to false then a copy
won't be created but you mustn't modify returned object directly because it
can effect consistency.
In any case the objects returned by
Satya, zip file downloaded fine, I'll investigate it and get to you later.
Regarding [Serializable]: cached objects in Ignite are serialized and sent
over the network.
So your entities should be set up for serialization, one way or another,
see details:
Hi vijayendra,
I think you run one client node () wihout at last one server node. In that case client node
be waiting for server node until it (server node) will not by added.
When you start another node in server mode (), client will continue to work.
If it not help you, please provide
It looks like the XML file you are using is not valid. Can you share the
config with us?
22 matches
Mail list logo