RE: Java to .NET interop

2017-10-26 Thread Gordon Reid (Nine Mile)
Hi Pavel, Thanks for the quick reply. I have not explicitly tried to only deploy the service classes without the entity classes into the java classpath on the .NET side. Our entity and service classes are packaged into the same jar. I won’t investigate this further, as its just as much of an

Ignite Events Remote Filter

2017-10-26 Thread rajivgandhi
Hi, We wish to listen to remote events with a remote filter and local listener: https://apacheignite.readme.io/docs/events#section-remote-events Our requirement is to entertain only those events on local listener which are allowed by remote filter. This is the API we are trying to use:

cache closed or destroyed issue

2017-10-26 Thread Pradeep Badiger
Hi, We are facing an issue with Ignite cache where it throws an IllegalArgumentException with Cache closed or destroyed. I have two java applications that start the ignite cache in an embedded mode. The cache instances form a cache cluster with the help of zookeeper plugin for discovery. The

Re: Custom SecurityCredentialsProvider and SecurityCredentials

2017-10-26 Thread vkulichenko
Hi Frank, Sorry for late response. SecurityCredentialsProvider is not used in Ignite code because Ignite doesn't provide any implementations of SecurityProcessor out of the box. If you want to make your cluster secure, you need to implement it and configure as a part of your own custom plugin.

Re: Ignite 2.3 - replicated cache lost data after restart cluster nodes with persistence enabled

2017-10-26 Thread Denis Magda
Dmitriy, I don’t see why a result of a simple query such as “select count(*) from t;” should be different if a rebalancing is in progress or after a cluster restart. Ignite’s SQL engine claims that its fault-tolerant and returns a consistent result set all the times unless a partition loss

Re: Ignite 2.3 - replicated cache lost data after restart cluster nodes with persistence enabled

2017-10-26 Thread Dmitry Pavlov
Hi Denis It seems to me that this is not a bug for my scenario, because the data was not loaded within the same transaction using transactional cache. In this case it is ok that cache data is rebalanced according to partition update counters,isn't it? I suppose in this case the data was not lost

Re: Ignite in embeded mode in Spark running in dynamic mode

2017-10-26 Thread vkulichenko
Ranjit, You can use it with Yarn or without Yarn. The point is that Ignite cluster is independent from Spark cluster, i.e. runs in separate processes. -Val -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: ComputeGrid API in C++

2017-10-26 Thread asingh
Ignite node = Ignition::Start("node1"); The first argument to Start() needs to be an xml file. Are there any specific properties that need to be set in the xml for this case? If I call Start(cfg, "node1"), it just launches node1 within the same process as the application. In the below diagram,

Re: Grid freezing

2017-10-26 Thread smurphy
Here is an additional log message that suggests that rolling back the transaction is not working. I do not know why the isolation level in this log is marked as READ_COMMITTED. All transactions are configured to be Optimistic and Serializable..: 2017-10-26 10:49:12,524 ERROR [dna-scan-engine

Re: Node and cluster maintenance best practice

2017-10-26 Thread Denis Magda
Follow the same process if you have the persistence enabled. Deactivate the cluster, terminate the nodes and do the upgrade. If you want to upgrade nodes in a rolling upgrade fashion then look for features provided enterprise products built on top of Ignite. — Denis > On Oct 23, 2017, at 6:57

Re: Ignite 2.3 - replicated cache lost data after restart cluster nodes with persistence enabled

2017-10-26 Thread Denis Magda
+ dev list This scenario has to be handled automatically by Ignite. Seems like a bug. Please refer to the initial description of the issue. Alex G, please have a look: To reproduce: 1. create a replicated cache with multiple indexedtypes, with some indexes 2. Start first server node 3. Insert

Re: Ignite 2.0.0 GridUnsafe unmonitor

2017-10-26 Thread Denis Magda
+ dev list Igniters, that’s a relevant point below. Newcomers to Ignite tend to stumble on deadlocks simply because the keys are passed in an unordered HashMap. Propose to do the following: - update bulk operations Java doc. - print out a warning if a HashMap is used and its exceeds one

Re: Ignite 2.0.0 GridUnsafe unmonitor

2017-10-26 Thread Denis Magda
> Performance is definitely improving. However, the worry is whether or not > OffHeap will be cleaned up properly and whether memory leaks will be caused > by the cache meta information of the Ignite Java Heap. > > Do you have any other concerns? There is nothing I’m concerned about here. —

Re: Grid freezing

2017-10-26 Thread smurphy
One thing that I see in the logs looks to me like a NullPointerException on attempting to commit an optimistic/serializable transaction. My reading of this excpetion is that an optimistic lock conflict is correctly detected in prepare0 but that eventually the code incorrectly attempts to return

Re: Grid freezing

2017-10-26 Thread smurphy
log_1.txt log_2.txt log_3.txt I don't see any nodes shutting down until 9

Re: Near Cache Topoolgy change causes NearCache to always miss.

2017-10-26 Thread slava.koptilin
Hi Tim, I was able to reproduce the issue. I've created the following jira ticket in order to track this: https://issues.apache.org/jira/browse/IGNITE-6767 Thanks, S. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: ComputeGrid API in C++

2017-10-26 Thread Igor Sapego
Hi, You don't have to modify platforms/cpp/ignite/src/ignite.cpp. Why won't you modify your code, where you start the node? I mean, in *your application code* write something like this: Ignite node = Ignition::Start("node1"); IgniteBinding binding = node.GetBinding();

Re: ComputeGrid API in C++

2017-10-26 Thread asingh
Hi Igor Shouldn't be a problem, given that the source code is there. I just want to make sure that I am doing it the right way. Currently, I have modified the main() method in platforms/cpp/ignite/src/ignite.cpp and added these two lines: IgniteBinding binding = ignite.GetBinding();

Re: Grid freezing

2017-10-26 Thread smurphy
No - this is what the invocation looks like: DequeuePortionsCallable job = new DequeuePortionsCallable(ignitePortionDequeuer); DequeuedPortionResponse response = _ignite.compute().call(job); -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Failed to query ignite

2017-10-26 Thread Andrey Mashenkov
Hi, Thanks for reproducer. I've make some changes and run test against 2.1, 2.2 and 2.3 version. Test with affinity key fails on 2.1 and 2.2 versions and looks ok on 2.3 version. Seems, there was a bug in 2.1 and it is already fixed in 2.3. PFA repro. On Thu, Oct 26, 2017 at 10:39 AM, iostream

Re: Ignite Web Session Clustering

2017-10-26 Thread slava.koptilin
Hello! > our main project uses Jboss Seam 2.2.1.CR1, JSF 1.2_15, Facelets 1.1.14, > Richfaces > 3.3.3, Hibernate 3.3.2, c3p0 0.9.1.2, Spring 3.1.3 and Servlet 2.5 (maybe > we > can update the Servlet version, but not the others). Apache ignite has been officially tested with the following

Re: ComputeGrid API in C++

2017-10-26 Thread Igor Sapego
You need to have the same code on all C++ nodes to be able to execute it remotely. In other words, you need to register classes you want to invoke remotely on all three nodes. Is that a problem for you? Best Regards, Igor On Wed, Oct 25, 2017 at 6:35 PM, asingh wrote: >

Re: Java to .NET interop

2017-10-26 Thread Pavel Tupitsyn
Hi Gordon, Entity Java classes are not needed in .NET client classpath. Can you give an example when that does not work for you? As for services, unfortunately, there is a limitation on Java side, Service class should be available on all nodes [1] [2]. Thanks, Pavel [1]

Re: Retrieving keys very slow from a partitioned, no backup, no replicated cache

2017-10-26 Thread Alexey Popov
Hi Anand, >In regards to your comment on cache will not get updated using invoke. How >do I ensure that the new computed value gets stored in the cache. >The first goal is to iterate through the cache and update a specific data >field in the cache in the fastest way possible. >The second goal

Re: when client node connect to server node, server node throws NotSerializableException

2017-10-26 Thread Jeff Jiao
just in case you don't see my replies, I will put all of these in one msg. yes, PIgniteCacheStoreFactory implements javax.cache.configuration.Factory, and this factory extends Serializable. like I said " I already created my own factory to create the cache store to avoid Serialization

Re: Failed to query ignite

2017-10-26 Thread iostream
One more thing to add - when I remove "affinityKey" from ID, I am able to query successfully. The error occurs when I set "ID" as my affinityKey. Is it a known bug? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Cannot find schema for object with compact footer

2017-10-26 Thread zshamrock
Yes, I suppose so, as it fails in the integration test, which uses the ignite client, so the client node. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Grid freezing

2017-10-26 Thread Evgenii Zhuravlev
Is it possible that you run DequeuePortionsCallable with timeout? Evgenii 2017-10-26 6:40 GMT+03:00 smurphy : > I added a transaction timeout of 1 millis and a transation size of 100 > (transaction is Optimistic and Serializable)... > > I see no

Java to .NET interop

2017-10-26 Thread Gordon Reid (Nine Mile)
Hi Igniters, We are running Ignite 2.2.0, we have a .NET client (runs in ignite client mode) and Java servers. We call Ignite Services running on the Java side, from the .NET client. We also access our memory grid entities from the .NET client. Currently it seems we need to package our java

Re: when client node connect to server node, server node throws NotSerializableException

2017-10-26 Thread Jeff Jiao
ok I tried to comment out this part, the exception I saw on server node before doesn't appear this time... so it looks like Cache Factory/Store problem... but why...