ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From mdolgonos <michael.dolgo...@citi.com>
Subject Re: Putting a multi-level object into Ignite cache hangs on put()
Date Thu, 29 Jun 2017 13:04:38 GMT
The node log is:
[17:36:21] ver. 2.0.0#20170430-sha1:d4eef3c6
[17:36:21] 2017 Copyright(C) Apache Software Foundation
[17:36:21]
[17:36:21] Ignite documentation: http://ignite.apache.org
[17:36:21]
[17:36:21] Quiet mode.
[17:36:21]   ^-- Logging to file
'I:\Projects\Architecture\Ignite\apache-ignite-fabric-2.0.0-bin\work\log\ignite-0197cf7
0.0.log'
[17:36:21]   ^-- To see **FULL** console log here add -DIGNITE_QUIET=false
or "-v" to ignite.{sh|bat}
[17:36:21]
[17:36:21] OS: Windows 7 6.1 amd64
[17:36:21] VM information: Java(TM) SE Runtime Environment 1.8.0_131-b11
Oracle Corporation Java HotSpot(TM) 64-Bit Serv
er VM 25.131-b11
[17:36:22] Configured plugins:
[17:36:22]   ^-- None
[17:36:22]
[17:36:22] Message queue limit is set to 0 which may lead to potential OOMEs
when running cache operations in FULL_ASYNC
 or PRIMARY_SYNC modes due to message queues growth on sender and receiver
sides.
[17:36:22] Security status [authentication=off, tls/ssl=off]
[17:36:27] Performance suggestions for grid 'RentdGrid' (fix if possible)
[17:36:27] To disable, set -DIGNITE_PERFORMANCE_SUGGESTIONS_DISABLED=true
[17:36:27]   ^-- Enable G1 Garbage Collector (add '-XX:+UseG1GC' to JVM
options)
[17:36:27]   ^-- Set max direct memory size if getting 'OOME: Direct buffer
memory' (add '-XX:MaxDirectMemorySize=<size>
[g|G|m|M|k|K]' to JVM options)
[17:36:27]   ^-- Disable processing of calls to System.gc() (add
'-XX:+DisableExplicitGC' to JVM options)
[17:36:27] Refer to this page for more performance suggestions:
https://apacheignite.readme.io/docs/jvm-and-system-tunin
g
[17:36:27]
[17:36:27] To start Console Management & Monitoring run
ignitevisorcmd.{sh|bat}
[17:36:27]
[17:36:27] Ignite node started OK (id=0197cf70, instance name=RentdGrid)
[17:36:27] Topology snapshot [ver=266, servers=1, clients=0, CPUs=4,
heap=1.0GB]
[17:36:47] Topology snapshot [ver=267, servers=1, clients=1, CPUs=4,
heap=3.7GB]
[17:37:05] Topology snapshot [ver=268, servers=1, clients=0, CPUs=4,
heap=1.0GB]
[09:03:05] Topology snapshot [ver=269, servers=1, clients=1, CPUs=4,
heap=3.7GB]

The client log is:
[09:02:58] ver. 2.0.0#20170430-sha1:d4eef3c6
[09:02:58] 2017 Copyright(C) Apache Software Foundation
[09:02:58] 
[09:02:58] Ignite documentation: http://ignite.apache.org
[09:02:58] 
[09:02:58] Quiet mode.
[09:02:58]   ^-- Logging to file
'I:\Projects\Architecture\Ignite\apache-ignite-fabric-2.0.0-bin\work\log\ignite-d2ae7a8a.0.log'
[09:02:58]   ^-- To see **FULL** console log here add -DIGNITE_QUIET=false
or "-v" to ignite.{sh|bat}
[09:02:58] 
[09:02:58] OS: Windows 7 6.1 amd64
[09:02:58] VM information: Java(TM) SE Runtime Environment 1.8.0_131-b11
Oracle Corporation Java HotSpot(TM) 64-Bit Server VM 25.131-b11
[09:02:58] Initial heap size is 192MB (should be no less than 512MB, use
-Xms512m -Xmx512m).
[09:02:58] Configured plugins:
[09:02:58]   ^-- None
[09:02:58] 
[09:02:59] Message queue limit is set to 0 which may lead to potential OOMEs
when running cache operations in FULL_ASYNC or PRIMARY_SYNC modes due to
message queues growth on sender and receiver sides.
[09:02:59] Security status [authentication=off, tls/ssl=off]
[09:02:59] REST protocols do not start on client node. To start the
protocols on client node set '-DIGNITE_REST_START_ON_CLIENT=true' system
property.
[09:03:06] Performance suggestions for grid 'RentdGrid' (fix if possible)
[09:03:06] To disable, set -DIGNITE_PERFORMANCE_SUGGESTIONS_DISABLED=true
[09:03:06]   ^-- Enable G1 Garbage Collector (add '-XX:+UseG1GC' to JVM
options)
[09:03:06]   ^-- Specify JVM heap max size (add '-Xmx<size>[g|G|m|M|k|K]' to
JVM options)
[09:03:06]   ^-- Set max direct memory size if getting 'OOME: Direct buffer
memory' (add '-XX:MaxDirectMemorySize=<size>[g|G|m|M|k|K]' to JVM options)
[09:03:06]   ^-- Disable processing of calls to System.gc() (add
'-XX:+DisableExplicitGC' to JVM options)
[09:03:06] Refer to this page for more performance suggestions:
https://apacheignite.readme.io/docs/jvm-and-system-tuning
[09:03:06] 
[09:03:06] To start Console Management & Monitoring run
ignitevisorcmd.{sh|bat}
[09:03:06] 
[09:03:06] Ignite node started OK (id=d2ae7a8a, instance name=RentdGrid)
[09:03:06] Topology snapshot [ver=269, servers=1, clients=1, CPUs=4,
heap=3.7GB]
Created Ignite cache: IgniteCacheProxy [delegate=GridDhtAtomicCache
[defRes=org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$1@ce5a68e,
near=null, super=GridDhtCacheAdapter
[multiTxHolder=java.lang.ThreadLocal@493dfb8e,
super=GridDistributedCacheAdapter [super=GridCacheAdapter
[locMxBean=org.apache.ignite.internal.processors.cache.CacheLocalMetricsMXBeanImpl@3954d008,
clusterMxBean=org.apache.ignite.internal.processors.cache.CacheClusterMetricsMXBeanImpl@2f94c4db,
aff=org.apache.ignite.internal.processors.cache.affinity.GridCacheAffinityImpl@593e824f,
igfsDataCache=false, mongoDataCache=false, mongoMetaCache=false,
igfsDataCacheSize=null,
asyncOpsSem=java.util.concurrent.Semaphore@72ccd81a[Permits = 500],
name=myInputFields1Cache, size=0]]]], opCtx=null]
adding id=0

And it hangs here



--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Putting-a-multi-level-object-into-Ignite-cache-hangs-on-put-tp14086p14163.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Mime
View raw message