Re: Is it possible from ignitevisor to say which nodes are server nodes and which are client

2016-05-04 Thread zshamrock
Great! -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Is-it-possible-from-ignitevisor-to-say-which-nodes-are-server-nodes-and-which-are-client-tp4770p4779.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Is it possible from ignitevisor to say which nodes are server nodes and which are client

2016-05-04 Thread Vasiliy Sisko
Hello @zshamrock We already implemented this in that issue: https://issues.apache.org/jira/browse/IGNITE-1069. It is available current nightly build: https://ignite.apache.org/community/contribute.html#nightly-builds or will available in 1.6 version. -- View this message in context: http://a

Re: Error on Transactions with Write Behind

2016-05-04 Thread Alexey Goncharuk
I think it makes sense not to validate store configuration unless we know that the entry is enlisted as WRITE. I've created the issue: https://issues.apache.org/jira/browse/IGNITE-3086 2016-05-04 5:28 GMT-07:00 Denis Magda : > As Val already mentioned you can't mix write-through and write-behind

How to start and use ignite in Tomcat

2016-05-04 Thread minisoft_rm
Dear all, i searched a number of topics here. but still don't know how to start and use ignite (in client mode) from Tomcat you know, I launched the standalone ignite as server node. my code in tomcat web app like this:" this.ignite = Ignition.start(ClientConfigurationFactory.createConfigur

How rich is Spring support for Ignite configuration file

2016-05-04 Thread zshamrock
Does Spring configuration file used to configure ignite support property placeholders ${} and getting the properties from file by using , as well as expression language #{}? In general what is supported by "Ignite" Spring and what is not. -- View this message in context: http://apache-ignite-u

Re: Client Connection to Ignite takes time

2016-05-04 Thread vijayendra bhati
Few days back I also had the same query.From this forum only i got to know that 4 5 sec is usual time for a client node to start up.In future it would be reduced to 1 2 sec. Regards,Vij Sent from Yahoo Mail on Android On Wed, 4 May, 2016 at 6:19 pm, Denis Magda wrote: Hi Arthi, This is

Re: Cache metrics - cache hits and misses are 0, also isEmpty in inconsistent state with getSize

2016-05-04 Thread zshamrock
Adding TimeUnit.SECONDS.sleep(5); // just to be sure we gave enough time for metrics to be updated Does not make any difference. Just to mention. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Cache-metrics-cache-hits-and-misses-are-0-also-isEmpty-in-inconsis

How I can be sure that Near cache works and configured properly

2016-05-04 Thread zshamrock
How I can be sure that Near cache works and configured properly? I could not find anything related to the near cache neither in visor or vvm/mbeans. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/How-I-can-be-sure-that-Near-cache-works-and-configured-properly-tp

Is it possible from ignitevisor to say which nodes are server nodes and which are client

2016-05-04 Thread zshamrock
Is it possible from ignitevisor to say which nodes are server nodes and which are client? -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Is-it-possible-from-ignitevisor-to-say-which-nodes-ar

Cache metrics - cache hits and misses are 0, also isEmpty in inconsistent state with getSize

2016-05-04 Thread zshamrock
Another question from the Gitter chat. Why the cache.metrics().cacheHits is 0, even if I do call cache.get(key) and it returns a stored value from the cache? How it can be? metrics.size returns 1, but also metrics.isE

Ignite client near cache conflicts with server distributed cache

2016-05-04 Thread zshamrock
Based on the discussion in Gitter it was proposed to ask a question here. package experiments.ignite; import org.apache.ignite.Ignite; import org.apache.ignite.Ignition; import org.apache.ignite.configuration.CacheConfiguration; import org.apache.ignite.configuration.IgniteConfiguration; import o

Re: Unexpected performance issue with SQL query followed by error

2016-05-04 Thread Alexey Kuznetsov
Hi Jan, You could also see EXPLAIN in Web Console SQL screen. See Addons page on Ignite site: https://ignite.apache.org/addons.html On Wed, May 4, 2016 at 6:49 PM, Denis Magda wrote: > Hi Jan, > > I would suggest double-checking that the most selective indexes are chosen > by Ignite SQL engine

Re: Client Connection to Ignite takes time

2016-05-04 Thread Denis Magda
Hi Arthi, This is mostly depends on the speed of your network link and other resources like free CPU cycles. How fast is your network? However the size of the cluster also matters since "new node joining" message generated while the new client is joining the cluster has to travel around the whole

Re: Azure App Service compatible?

2016-05-04 Thread Denis Magda
Hi, Seems that in your case the multicast IP finder is used (default one) and most likely the multicast is disable in your network environment. I would suggest you using the static IP finder that allows to predefine a list of all Ignite nodes that must form a cluster [1]. In addition if you need

Re: Error on Transactions with Write Behind

2016-05-04 Thread Denis Magda
As Val already mentioned you can't mix write-through and write-behind caches in a single transactions. However, in my understanding I don't see any reason why we can't mix these caches taking into account that the one will be used for 'read' operations only. Alex G. or Sam can you share your thou

Re: Persistent Cache

2016-05-04 Thread Kamal C
Thanks Denis! On Wed, May 4, 2016 at 5:55 PM, Denis Magda wrote: > Yes, it does. But it’s available as a part of paid enterprise version > delivered by GridGain. It’s not a part of Apache Ignite. > > — > Denis > > On May 4, 2016, at 3:12 PM, Kamal C wrote: > > Denis, > > Is Local Recoverable Ca

Re: Persistent Cache

2016-05-04 Thread Denis Magda
Yes, it does. But it’s available as a part of paid enterprise version delivered by GridGain. It’s not a part of Apache Ignite. — Denis > On May 4, 2016, at 3:12 PM, Kamal C wrote: > > Denis, > > Is Local Recoverable CacheStore applicable for all the cache modes? (Local, > Replicated and Part

Re: Persistent Cache

2016-05-04 Thread Kamal C
Denis, Is Local Recoverable CacheStore applicable for all the cache modes? (Local, Replicated and Partitioned) --Kamal On Wed, May 4, 2016 at 5:21 PM, Denis Magda wrote: > Hi Kamal, > > Ignite doesn’t have an implementation of the CacheStore that stores cache > data in files on disk. > You sho

Re: Unexpected performance issue with SQL query followed by error

2016-05-04 Thread Denis Magda
Hi Jan, I would suggest double-checking that the most selective indexes are chosen by Ignite SQL engine and there are no full scans during a SQL query execution. To fulfill this you can use "EXPLAIN" statement to see an execution plan of every query [1]. If a index is not optimally selected for a

Re: Persistent Cache

2016-05-04 Thread Denis Magda
Hi Kamal, Ignite doesn’t have an implementation of the CacheStore that stores cache data in files on disk. You should implement it on your own or use the one that is provided by other vendors (i.e. GridGain delivers Local Store [1] as a part of it enterprise product built on top of Ignite). [

Persistent Cache

2016-05-04 Thread Kamal C
Hi, I have a requirement in which state of the caches should be preserved during application restart. I've gone through the [1] link. But, I don't want to store my contents in the database. How to store the contents of cache in the disk ? [1] https://apacheignite.readme.io/docs/persistent-sto

Re: Stopping the node in order to prevent cluster wide instability.

2016-05-04 Thread Denis Magda
Hi, Please properly subscribe to the user list (this way we will not have to manually approve your emails). All you need to do is send an email to ì user-subscr...@ignite.apache.orgî and follow simple instructions in the reply. Upon your questions. Most likely the node, that was stopped, became

Re: HDFS Caching

2016-05-04 Thread Ivan Veselovsky
Hi, Barry, yes, permission security model is not currently supported in IGFS. The permission mode just propagated to IGFS and can be taken as a part of file meta information. But that does not restrict access to the file: anybody who can access cache can access file data. You can create feature-req

Re: Error starting c++ client node using 1.6

2016-05-04 Thread Vladimir Ozerov
Hi Murthy, The stack trace you provided shows that you still use old unpatched version. This could be observed by the line "at org.apache.ignite.Ignition.start(Ignition.java:322)". Patched version do not perform this call any more and goes directly to the "IgnitionEx.start()". You can see the fix

Re: Compute Grid API in C++/Scala

2016-05-04 Thread arthi
Hi Val, we use java API to start the servers, and C++ API to start the client. We have a custom config file for the setup. There are 6 nodes in the cluster. I have another issue elaborating this issue too - http://apache-ignite-users.70518.x6.nabble.com/Client-Connection-to-Ignite-takes-time-td4

Re: Ignite WRite Behind

2016-05-04 Thread Vladimir Ozerov
Hi, writeAll() method is only executed for entries located in the same cache. As you have only 1 entry per cache in transaction, this is expected behavior that writeAll() is not called. Normally, you should make your logic dependent on whether write() or writeAll() is called, because it is up to I

Re: Compute Grid API in C++/Scala

2016-05-04 Thread vkulichenko
Hi Arthi, How do you start server nodes? Are they plain Java nodes or C++ nodes (like shown in [1])? If the latter, you should be able to acquire local Ignite instance using Ignition.get() method within C++ code. Will this work for you? [1] https://apacheignite-cpp.readme.io/docs/getting-started-

Re: Unexpected performance issue with SQL query followed by error

2016-05-04 Thread jan.swaelens
^-- Non heap [used=263MB, free=13.34%, comm=273MB] ^-- Public thread pool [active=1, idle=15, qSize=0] ^-- System thread pool [active=0, idle=16, qSize=0] ^-- Outbound messages queue [size=0] INFO [20160504 08:51:56] - Metrics for local node (to disable set 'metricsLogFrequency&