Re: IGFS Secondary Filesystem Query Cached Blocks

2016-09-30 Thread vkulichenko
You should update the secondary file system through IGFS. This way primary and secondary file systems will be always consistent. -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/IGFS-Secondary-Filesystem-Query-Cached-Blocks-tp7989p8044.html Sent from the Apa

Re: Out of memory

2016-09-30 Thread javastuff....@gmail.com
Good to know about future change. I will try your suggestion regarding system property. I do not think I will have scenario where insertion and deletion of same key happens at the same time. BTW all of my cache are marked TRANSACTIONAL, just for the sack of having capability of explicit distribut

Re: Getting Error [grid-timeout-worker] when running join query on Single Ignite Node

2016-09-30 Thread Alexander Paschenko
Mainish, Your EXPLAIN query has EXPLAIN word twice (in the very beginning) and thus is not synctactically correct. 2016-09-30 15:26 GMT+03:00 Manish Mishra : > Thanks for reply. > @Taras I have set QuerySqlField(index=true) on the indexing fields. @Alex, > I've used the EXPLAIN with query I make

Delay in obtaining connection to Ignite server

2016-09-30 Thread Sri Ganesh V
Hi, We have 3 node (server) ignite cluster. Cache : Off-Heap Mode Heap Memory : 4GB (Each) We are trying to connect to the cluster. CODE : TcpDiscoverySpi spi = new TcpDiscoverySpi(); TcpDiscoveryVmI

Re: Getting Error [grid-timeout-worker] when running join query on Single Ignite Node

2016-09-30 Thread Manish Mishra
Thanks for reply. @Taras I have set QuerySqlField(index=true) on the indexing fields. @Alex, I've used the EXPLAIN with query I make to Gridgain Cache but I don't know how to verify if the indexes are invoked on not. Here is the output when I used explain with the Query: SELECT DISTINCT M1 __C0,

Re: Couchbase as persistent store

2016-09-30 Thread kvipin
Guys, read-through is working fine for me but write-through is not working. I'm not getting error/exception either. Following is my configuration file and relevant code blocks, *Sever node configuration file:* $ cat test-tool-server.xml http://www.springframework.org/schema/beans"; xmln

Re: Which ports does ignite cluster need to run normally?

2016-09-30 Thread Vladislav Pyatkov
Hi, For the joining nodes to cluster, Communication and Discovery SPI will be inough: TcpDiscoverySpi:47500~47600 TcpCommunicationSpi:47100~47200 by default. Others is optinal: time server port:31100~31200 If you use time synchronization between nodes. TCP server port:11211 for connect by int

Which ports does ignite cluster need to run normally?

2016-09-30 Thread Level D
Hi all, There is an active firewall in my system, and these following ports will be added to exceptions list. time server port??31100~31200 TCP server port??11211 Remote Management ??com.sun.management.jmxremote.port49128 TcpDiscoverySpi??47500~47600 TcpCommunicationSpi??47100~47200 shared