Ignite Cache Memory Size Information

[Hemasundara Rao]

Hi ,
I am looking for cache memory size statics using Ignite C#.net API.
Can someone let me know how to get the stats of the cache like how large
(like how many MB/GB) is the cache in memory (both on and off heap)?

Currently, I can only get number of entries in the cache using the
cache.GetSize()

cache.GetMetrics() returns the Cache Metrics but doesn't have any
information about total size in gb/mb of the cache in memory.

Regards,
Hemasundara Rao Pottangi  | Senior Project Leader

[image: HotelHub-logo]
HotelHub LLP
Phone: +91 80 6741 8700
Cell: +91 99 4807 7054
Email: hemasundara@hotelhub.com
Website: www.hotelhub.com 
--

HotelHub LLP is a service provider working on behalf of Travel Centric
Technology Ltd, a company registered in the United Kingdom.
DISCLAIMER: This email message and all attachments are confidential and may
contain information that is Privileged, Confidential or exempt from
disclosure under applicable law. If you are not the intended recipient, you
are notified that any dissemination, distribution or copying of this email
is strictly prohibited. If you have received this email in error, please
notify us immediately by return email to
noti...@travelcentrictechnology.com and
destroy the original message. Opinions, conclusions and other information
in this message that do not relate to the official business of Travel
Centric Technology Ltd or HotelHub LLP, shall be understood to be neither
given nor endorsed by either company.

Create index got stuck and freeze whole cluster.

[Ray]

I'm using a five nodes Ignite 2.6 cluster.
When I try try to create index on table with10 million records using sql
"create index on table(a,b,c,d)", the whole cluster freezes and prints the
following log for 40 minutes.

2018-10-30T02:48:44,086][WARN
][exchange-worker-#162][GridDhtPartitionsExchangeFuture] Unable to await
partitions release latch within timeout: ServerLatch [permits=4,
pendingAcks=[20aa5929-3f26-4923-87a3-27b4f6d4f744,
ec5be25e-6601-468c-9f0e-7ab7c8caa9e9, 45819b05-a338-4bc4-b104-f0c7567fd49d,
cbb80db7-b342-4b97-ba61-97d57c194a1a], super=CompletableLatch [id=exchange,
topVer=AffinityTopologyVersion [topVer=202, minorTopVer=1]]]

I noticed one of the servers(log in server3.zip) is stuck in checkpoint
process, and this server acts as coordinator in PME.
In the log I see only 856610 pages needs to be flushed to disk, but the
checkpoint takes 32 minutes to finish.
While another node takes 7 minutes to finish writing 919060 pages to disk.
Also the disk usage on the slow checkpoint server is not 100%.

Here's the whole log file for 5 servers.
server1.zip
  
server2.zip
  
server3.zip
  
server4.zip
  
server5.zip
  




--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite locking when affinity is used.

[kotamrajuyashasvi]

Hi

Need help on the above issue.
Please let us know the possibilities for cause of the above Exception. 



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: how to do i hibernate configuration for Apache ignite database

[Malashree]

using Ignite as database for Hibernate.



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Cluster is not responsive after node segmentation and reconciliation

[Ariel Tubaltsev]

ok, thanks



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: cotinuousquery -> Requesting mapping from grid failed for [ platformId=1, typeId=1173251103]

[jcalahor]

i forgot to mention that my starting params is:
Apache.Ignite.exe
-Assembly=C:\apache_ignite\_net\ignite_shared\ignite_shared\bin\Debug\ignite_shared.dll





--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Configure Timeout for client in case server nodes are not up

[Evgenii Zhuravlev]

Hi,

connectionTimeout is related to different things. The timeout that you
searching for is joinTimeout. By default it's unlimited.

https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/spi/discovery/tcp/TcpDiscoverySpi.html#setJoinTimeout-long-

Evgenii

пн, 29 окт. 2018 г. в 14:18, p...@infoworks.io :

> Hey,
>
> What happens to a client node in case there are no other nodes running, i
> found a default value for connectionTimeout at 5000ms in
> TcpCommunicationSpi and think it should timeout but my client node kept on
> trying for a connection.
> should i be looking at some other property in TcpCommunicationSpi or if
> not via TcpCommunicationSpi is there a way we can configure a timeout?
>
> Regards,
> Prem
>

Re: Ouch! Argument is invalid: Cache name must not be null or empty.

[Evgenii Zhuravlev]

Hi,

Looks like you use JDBC client driver, which needs cache name to be
configured(https://apacheignite-sql.readme.io/docs/jdbc-client-driver). I'd
recommend using a thin JDBC driver instead - it doesn't need.(
https://apacheignite-sql.readme.io/docs/jdbc-driver)

Evgenii

пн, 29 окт. 2018 г. в 10:48, sv :

> Getting "Ouch! Argument is invalid: Cache name must not be null or empty."
> error when trying to execute SQL from within Zeppelin, using the Node
> Client
> type of connection (jdbc:ignite:cfg:[URL]).
>
> Zeppelin 0.8.0, Ignite 2.6 libs.  Cluster is 2.6.
>
> Almost seems like it wants a cache name, but I thought this bug was fixed
> in
> 2.6?  Perhaps something else is going on.
>
>
>
>
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Configure Timeout for client in case server nodes are not up

[prem]

Hey,

What happens to a client node in case there are no other nodes running, i found 
a default value for connectionTimeout at 5000ms in TcpCommunicationSpi and 
think it should timeout but my client node kept on trying for a connection.
should i be looking at some other property in TcpCommunicationSpi or if not via 
TcpCommunicationSpi is there a way we can configure a timeout?

Regards,
Prem

Re: Ignite partition redistribution when topology is changed.

[Ilya Kasnacheev]

Hello!

As far as I understand, assignPartitions() will be called as many times as
needed in order to always have the latest one.

It is assumed to be stateless anyway.

Considerations are the following, as per javadoc:

* Gets affinity nodes for a partition. In case of replicated cache, all returned
* nodes are updated in the same manner. In case of partitioned cache,
the returned
* list should contain only the primary and back up nodes with primary node being
* always first.
* 
* Note that partitioned affinity must obey the following contract:
given that node
* N is primary for some key K, if any other
node(s) leave
* grid and no node joins grid, node N will remain primary
for key K.

Regards,
-- 
Ilya Kasnacheev


пн, 29 окт. 2018 г. в 11:41, kotamrajuyashasvi :

> Hi
>
> I'm working on a custom affinity function.
> According to the documentation :
>
> https://apacheignite.readme.io/docs/affinity-collocation#section-affinity-function
> assignPartitions(...) method is called whenever cluster topology changes.
> So
> redistribution
> of partitions happens after this method is called. What would happen when
> cluster topology
> changes while the partition redistribution is still in progress. Does
> Ignite
> internally handle this
> case or should we handle it in our custom affinity function code.
>
> Also what are the important scenarios to consider regarding primary and
> backup partition redistribution
> while writing our own affinity function.
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Re: how to do i hibernate configuration for Apache ignite database

[Ilya Kasnacheev]

Hello!

Do you mean using Ignite as L2 cache for Hibernate, or using Ignite as
database for Hibernate?

Regards,
-- 
Ilya Kasnacheev


сб, 27 окт. 2018 г. в 8:28, Malashree :

> how to do i hibernate configuration for Apache ignite database using maven
> application
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Ignite partition redistribution when topology is changed.

[kotamrajuyashasvi]

Hi

I'm working on a custom affinity function.
According to the documentation :
https://apacheignite.readme.io/docs/affinity-collocation#section-affinity-function
assignPartitions(...) method is called whenever cluster topology changes. So
redistribution
of partitions happens after this method is called. What would happen when
cluster topology 
changes while the partition redistribution is still in progress. Does Ignite
internally handle this
case or should we handle it in our custom affinity function code.

Also what are the important scenarios to consider regarding primary and
backup partition redistribution 
while writing our own affinity function.



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: cotinuousquery -> Requesting mapping from grid failed for [ platformId=1, typeId=1173251103]

[Ilya Kasnacheev]

Hello!

This usually indicates that assembly with specified type is not loaded on a
node. When using Apache.Ignite.exe, make
sure to load assemblies with -assembly parameter. Alternatively, set
IgniteConfiguration.PeerAssemblyLoadingEnabled to true.

Should be pretty explanatory, shouldn't it?

To use remote C# filters, you need to:
- Start all Ignite nodes as .Net nodes (Apache.Ignite.exe or custom project)
- Include .dlls with filters code on all nodes OR enable
PeerAssemblyLoading.

Regards,
-- 
Ilya Kasnacheev


пт, 26 окт. 2018 г. в 18:10, jcalahor :

> i made the config changes, and now the filter was is not found, the filter
> was working earlier.
>
> C:\apache_ignite\platforms\dotnet\bin>Apache.Ignite.exe
> -Assembly=C:\apache_igni
> te\_net\ignite_shared\ignite_shared\bin\Debug\ignite_shared.dll
> Oct 26, 2018 10:02:49 AM
> org.springframework.beans.factory.xml.XmlBeanDefinition
> Reader loadBeanDefinitions
> INFO: Loading XML bean definitions from URL
> [file:/C:/apache_ignite/examples/con
> fig/example-ignite.xml]
> Oct 26, 2018 10:02:49 AM
> org.springframework.beans.factory.xml.XmlBeanDefinition
> Reader loadBeanDefinitions
> INFO: Loading XML bean definitions from URL
> [file:/C:/apache_ignite/examples/con
> fig/example-default.xml]
> Oct 26, 2018 10:02:49 AM
> org.springframework.context.support.AbstractApplication
> Context prepareRefresh
> INFO: Refreshing
> org.springframework.context.support.GenericApplicationContext@1
> 8ef96: startup date [Fri Oct 26 10:02:49 CDT 2018]; root of context
> hierarchy
> [10:02:50]__  
> [10:02:50]   /  _/ ___/ |/ /  _/_  __/ __/
> [10:02:50]  _/ // (7 7// /  / / / _/
> [10:02:50] /___/\___/_/|_/___/ /_/ /___/
> [10:02:50]
> [10:02:50] ver. 2.6.0#20180710-sha1:669feacc
> [10:02:50] 2018 Copyright(C) Apache Software Foundation
> [10:02:50]
> [10:02:50] Ignite documentation: http://ignite.apache.org
> [10:02:50]
> [10:02:50] Quiet mode.
> [10:02:50]   ^-- Logging to file
> 'C:\apache_ignite\work\log\ignite-117c9354.0.lo
> g'
> [10:02:50]   ^-- Logging by 'JavaLogger [quiet=true, config=null]'
> [10:02:50]   ^-- To see **FULL** console log here add -DIGNITE_QUIET=false
> or "-
> v" to ignite.{sh|bat}
> [10:02:50]
> [10:02:50] OS: Windows 7 6.1 amd64
> [10:02:50] VM information: Java(TM) SE Runtime Environment 1.8.0_101-b13
> Oracle
> Corporation Java HotSpot(TM) 64-Bit Server VM 25.101-b13
> [10:02:50] Initial heap size is 384MB (should be no less than 512MB, use
> -Xms512
> m -Xmx512m).
> [10:02:50] Configured plugins:
> [10:02:50]   ^-- None
> [10:02:50]
> [10:02:50] Configured failure handler: [hnd=StopNodeOrHaltFailureHandler
> [trySto
> p=false, timeout=0]]
> [10:02:50] Message queue limit is set to 0 which may lead to potential
> OOMEs
> whe
> n running cache operations in FULL_ASYNC or PRIMARY_SYNC modes due to
> message qu
> eues growth on sender and receiver sides.
> [10:02:50] Security status [authentication=off, tls/ssl=off]
> [10:03:16] Nodes started on local machine require more than 20% of physical
> RAM
> what can lead to significant slowdown due to swapping (please decrease JVM
> heap
> size, data region size or checkpoint buffer size) [required=20952MB,
> available=2
> 4573MB]
> [10:03:16] Performance suggestions for grid  (fix if possible)
> [10:03:16] To disable, set -DIGNITE_PERFORMANCE_SUGGESTIONS_DISABLED=true
> [10:03:16]   ^-- Disable grid events (remove 'includeEventTypes' from
> configurat
> ion)
> [10:03:16]   ^-- Enable G1 Garbage Collector (add '-XX:+UseG1GC' to JVM
> options)
>
> [10:03:16]   ^-- Specify JVM heap max size (add '-Xmx[g|G|m|M|k|K]'
> to
> JVM
>  options)
> [10:03:16]   ^-- Set max direct memory size if getting 'OOME: Direct buffer
> memo
> ry' (add '-XX:MaxDirectMemorySize=[g|G|m|M|k|K]' to JVM options)
> [10:03:16]   ^-- Disable processing of calls to System.gc() (add
> '-XX:+DisableEx
> plicitGC' to JVM options)
> [10:03:16] Refer to this page for more performance suggestions:
> https://apacheig
> nite.readme.io/docs/jvm-and-system-tuning
> [10:03:16]
> [10:03:16] To start Console Management & Monitoring run
> ignitevisorcmd.{sh|bat}
> [10:03:16]
> [10:03:16] Ignite node started OK (id=117c9354)
> [10:03:16] Topology snapshot [ver=2, servers=2, clients=0, CPUs=12,
> offheap=9.6G
> B, heap=11.0GB]
> [10:03:16]   ^-- Node [id=117C9354-D951-4AF0-9AA8-C3A4D68E3E0F,
> clusterState=ACT
> IVE]
> [10:03:16] Data Regions Configured:
> [10:03:16]   ^-- default [initSize=256.0 MiB, maxSize=4.8 GiB,
> persistenceEnable
> d=false]
> [10:03:56] Topology snapshot [ver=3, servers=2, clients=1, CPUs=12,
> offheap=9.6G
> B, heap=16.0GB]
> [10:03:56]   ^-- Node [id=117C9354-D951-4AF0-9AA8-C3A4D68E3E0F,
> clusterState=ACT
> IVE]
> [10:03:56] Data Regions Configured:
> [10:03:56]   ^-- default [initSize=256.0 MiB, maxSize=4.8 GiB,
> persistenceEnable
> d=false]
> [10:04:20,994][SEVERE][client-connector-#72][] Failure in Java callback
> class org.apache.ignite.IgniteException: Platform
> error:Apache.Ign

Ouch! Argument is invalid: Cache name must not be null or empty.

[sv]

Getting "Ouch! Argument is invalid: Cache name must not be null or empty." 
error when trying to execute SQL from within Zeppelin, using the Node Client
type of connection (jdbc:ignite:cfg:[URL]).

Zeppelin 0.8.0, Ignite 2.6 libs.  Cluster is 2.6.  

Almost seems like it wants a cache name, but I thought this bug was fixed in
2.6?  Perhaps something else is going on.   







--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Cache Metrics

[Ilya Kasnacheev]

Hello!

Yes, I assume that offHeapEntries == primaries + backups.

Regards,
-- 
Ilya Kasnacheev


пт, 26 окт. 2018 г. в 16:49, Akash Shinde :

> Hi,
>  I have captured below two ignite cache metrics.
>
> 1) igniteCache.metrics().getSize()
> 2)igniteCache  .metrics().getOffHeapEntriesCount()
>
> I started three nodes with distrusted load.
> When I started filling the cache I observed OffHeapEntries counts are
> approximately double
> of cache size.
>
> Why offHeapEntries count are approximately double?
> Is offHeapEntries includes primary count plus backup counts?
>
> Thanks,
> Akash
>
>