Updating the same entry multiple time in Ignite transaction

Hi, Can I update the same entry multiple time inside ignite transaction? Or Can I update an entry and then remove the same entry in ignite transaction? Thanks, Prasad

Re: Updating the same entry multiple time in Ignite transaction

Hi, Sure, multiple actions with same query within same transaction should work. Please, let us know if you observe unexpected behavior. Any reproducer will be appreciated. On Tue, Jun 5, 2018 at 10:36 AM, Prasad Bhalerao < prasadbhalerao1...@gmail.com> wrote: > Hi, > > Can I update the same en

Ignite 2.5 | Can't restore memory - critical part of WAL archive is missing with walMode=NONE

Hi, I'm testing v2.5 vs v2.4 for persisted dataregion with *walModel = NONE* and while performance seems better I failed to restart the cluster after what I think is a proper shutdown (using top -deactivate then kill -k from visor). When I try to reactivate the cluster (using top -activate f

Ignite Optimistic Transactions

Hi, https://apacheignite.readme.io/v2.5/docs/transactions#section-optimistic-transactions As per above link: *SERIALIZABLE - Stores an entry version upon first read access. Ignite will fail a transaction at the commit stage if the Ignite engine detects that at least one of the entries used as pa

Re: Updating the same entry multiple time in Ignite transaction

Hi, I tried this with simple code and it works fine. But in my application when I do similar thing I get following exception when I do commit. I am getting transaction as follows. IgniteTransactions igniteTx = getServiceContext().getGridService().getTransaction(); try (Transaction transact

How to execute an sql on a specific remote server?

Hi, I am trying to execute the following select query using the native java client on a cluster of 2 nodes. String query = "select * from Person"; List> results = superCache.query(new SqlFieldsQuery(query)).getAll(); Now, is any there way to execute the same query on only one specific remote nod

Re: Updating the same entry multiple time in Ignite transaction

Hi, It is ok, Optimistic transaction failed on commit with TransactionOptimisticException due to write\read conflict. See javadoc [1] and documentation [2] for details. Javadoc says: * However, in {@link TransactionConcurrency#OPTIMISTIC} mode, if some transactions cannot be serially isolated *

Re: How to execute an sql on a specific remote server?

Hi, What are you trying to achieve? What is cache mode? For REPLICATED cache, your query will be sent to and executed on one random node. 1. You can sent a compute job [1] to certain node (via ignite.compute(ignite.cluster().forNode(...)).execute(task)) or affinity job [2] (ignite.compute().aff

Re: Updating the same entry multiple time in Ignite transaction

> Hi, > > In my case only one transaction is in progress. In this transaction I > update few entries in cache and then re-read these entries and updates it > again in some other method. > When I read the entry after first update operations, transaction entry > read version(IgniteTxEntry-entryReadVe

Re: Ignite Optimistic Transactions

Hi, 1. The explanation looks confusing. In other words, Ignite remembers entry version in transaction context at first read access. 2. If another transaction has commited just before the current transaction, then current transaction will fails with TransactionOptimisticException as Ignite can't r

Re: Updating the same entry multiple time in Ignite transaction

Hi, We'll check this case. Please, share a reproducer if possible. On Tue, Jun 5, 2018 at 3:53 PM, Prasad Bhalerao < prasadbhalerao1...@gmail.com> wrote: > Hi, > > In my case only one transaction is in progress. In this transaction I > update few entries in cache and then re-read these entries a

Re: Ignite 2.5 | Can't restore memory - critical part of WAL archive is missing with walMode=NONE

Hi, I can't reproduce the issue. Is it possible grid configuration was changed between runs? Is it possible to share a reproducer? On Tue, Jun 5, 2018 at 12:05 PM, Emmanuel Marchand < emmanuel.march...@exensa.com> wrote: > Hi, > > I'm testing v2.5 vs v2.4 for persisted dataregion with *walModel

Re: Updating the same entry multiple time in Ignite transaction

Hi, I observed one more behavior. I am using executor service to execute the tasks. When I submit a task to remove entries from cache, I get transaction optimistic exception. But instead of submitting the task, if I just call task.run() method it works fine. Thanks, Prasad On Tue, Jun 5, 2018 a

Re: Updating the same entry multiple time in Ignite transaction

Hi, Do you mean you put entry in one thread and delete in another? If so, it is ok. Seems, you have scenario like this one: 1. Put-thread remembers entry version at first read and applies update operation only when commit() method has been called. 2. Delete-thread starts separate implicit optimis

support for Scala Collection as key?

Thanks a lot for the wonderful development on Ignite. I am wondering if there is any plan to support Scala Collection (e.g. Vector) as key? There is support for common Java Collection, see here: https://github.com/apache/ignite/blob/d4ae653d8018e88847425111321e653bd558a973/modules/core/src/main/j

Re: Ignite 2.5 | Can't restore memory - critical part of WAL archive is missing with walMode=NONE

Hi, I'm not sure I can provide a reproducer, but here is some informations : * configuration file attached * 2 server nodes, 1 client (+ visor) * I'm streaming enough data to trigger a checkpoint with a reason 'too many dirty pages' o [INFO][db-checkpoint-thread-#69][GridCacheDatabase

Re: support for Scala Collection as key?

Hi, Ignite doesn't rely on BinaryObject hashcode or equals method, it use internal comparison logic instead. So, it is ok BinaryObject.equals() return true if compared with same object only. As Ignite have no hooks for scala collections, they will be handled as regular user objects. Let us know i

Re: Ignite 2.5 | Can't restore memory - critical part of WAL archive is missing with walMode=NONE

Hi, I've make a simple test and still can't reproduce this. Would you please take a look if I missed smth? Is it possible you have more than one region and\or cache? On Tue, Jun 5, 2018 at 5:41 PM, Emmanuel Marchand < emmanuel.march...@exensa.com> wrote: > Hi, > > I'm not sure I can provide a

Re: Doubts regarding using externalizable in model classes

Hi, It is a duplicate of StackOverflow question [1]. Please, find an answer on SO via link provided. [1] https://stackoverflow.com/questions/50697634/using-externalizable-in-apache-ignite On Tue, Jun 5, 2018 at 8:30 AM, the_palakkaran wrote: > I have 3 doubts, > > 1. My model classes are exter

RE: ClassCastException When Using CacheEntryProcessor in StreamVisitor

Hello, Can anyone see this email? From: Cong Guo Sent: 2018年6月1日 13:11 To: 'user@ignite.apache.org' Subject: ClassCastException When Using CacheEntryProcessor in StreamVisitor Hi, I want to use IgniteDataStreamer to handle data updates. Is it possible to use CacheEntryProcessor in StreamVisit

Re: support for Scala Collection as key?

Got it. I thought IgniteCache converts key to BinaryObject and then compares them, and therefore gave the example. However, if I put key k1 with a value into IgniteCache, and retrieve the value using k2, I won't be able to find the entry. Do you know what's the process behind this process? -- S

Re: Affinity colocation and sql queries

Hello! 1) Yes! 2) "almost all the time" is not a very strong constraint here. You might need to enable distributed joins to get such (partially-collocated) queries to perform. Your query might still benefit from collocation if query planner realizes that all keys are located on the same node. 3)

Re: support for Scala Collection as key?

Hi, Most likely, Scala Vector can't be used as a key as-is due to it's implementation [1]. I'm not sure, if k1 and k2 scala objects have same internal structure to Ignite can serialize them to same binary representation. [1] https://stackoverflow.com/questions/20612729/how-does-scalas-vector-wor

Re: ClassCastException When Using CacheEntryProcessor in StreamVisitor

Hello, Can you please share the full stacktrace so we can see where the original ClassCastException is initiated? If it is not printed on a client, it should be printed on one of the server nodes. Thanks! вт, 5 июн. 2018 г. в 18:35, Cong Guo : > Hello, > > > > Can anyone see this email? > > > >

Re: Ignite client mvn artifact's purpose?

Hi, Answered on SO, please take a look [1]. [1] https://stackoverflow.com/questions/50691453/ignite-client-mvn-artifacts-purpose On Sun, Jun 3, 2018 at 2:26 PM, mlekshma wrote: > Hi Folks, > > I notice there is a mvn artifact with artifact id "ignite-clients". What is > its purpose? > > https:

RE: Affinity colocation and sql queries

Thanks Ilya, Denis. Regards, De : ilya.kasnacheev Envoyé : mardi 5 juin 2018 18:15:45 À : user@ignite.apache.org Objet : Re: Affinity colocation and sql queries Hello! 1) Yes! 2) "almost all the time" is not a very strong constraint here. You might need to en

Ignite on Graal VM

Has anybody tried Ignite on GraalVM 1.0 ? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

IgniteCache invoke CacheEntryProcessor, not throw EntryProcessorException

Hi Developers, I am not sure if I understand the IgniteCache invoke method API correctly here: https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/IgniteCache.html#invoke-K-org.apache.ignite.cache.CacheEntryProcessor-java.lang.Object...-

Re: support for Scala Collection as key?

Yeah, I believe k1 and k2's internal structure are different, and therefore causing the problem -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

RE: ClassCastException When Using CacheEntryProcessor in StreamVisitor

Hi, The stacktrace is as follows. Do I use the CacheEntryProcessor in the right way? May I have an example about how to use CacheEntryProcessor in StreamVisitor, please? Thank you! javax.cache.processor.EntryProcessorException: java.lang.ClassCastException: com.huawei.clusterexperiment.model.P

Ignite 2.5 nodes do not rejoin the cluster after restart

Hi I'm completely new to Ignite. I installed Ignite 2.5 and created a simple 3-node cluster (tried with 2 nodes too). I set a custom ConsistentID for each node (same as the hostname). I also enabled *persistence* (does it matter?). The cluster looks active and contains all 3 nodes. I print the ba

Re: Ignite on Graal VM

There was a discussion on the dev list regarding this: http://apache-ignite-developers.2346864.n4.nabble.com/Using-GraalVM-instead-of-standard-JVM-td30284.html I'm sure if anyone tried to run though, feel free to follow up there and ask. -Val -- Sent from: http://apache-ignite-users.70518.x6.n

Spark Ignite connection using Config file

Hi I am using Spark 2.3 and Ignite 2.4 . Trying to read data from Ignite using Spark Dataframe. Using examples/config/persistentstore/example-persistent-store.xml as OPTION_CONFIG_FILE parameter. But getting Cannot create inner bean 'org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi#76889e60' of

Re: Ignite 2.5 nodes do not rejoin the cluster after restart (works on 2.4)

I wiped Ignite 2.5 and tried 2.4. On a 2-node cluster I could restart each node back and forth without hindrance. I could even consider using 2.4 but it lacks the authentication feature and also the rpm is built with all contents world-writable which makes you wonder about the overall security of t

Re: Spark Ignite connection using Config file

after chaning config file to default with persistence parameter getting Caused by: java.lang.ClassNotFoundException: ignite.DefaultSource Exception in thread "main" java.lang.ClassNotFoundException: Failed to find data source: ignite. Please find packages at http://spark.apache.org/third-party-pr

Re: Session.removeAttribute is not working as expected

I've updated: https://github.com/daynok/ignite-webapp Made sure all dependencies where compiled against jdk8 (ignite, spring) and retested with - jdk8 - tomcat 7 - ignite 2.5 Still seeing the same issue... no idea why. In the git project I've included both ignite nodes. - Original Message

RE: Spark + Ignite standalone mode on Kubernetes cluster.

We are trying to integrate spark 2.2.0 with Ignite 2.4 on kubernetes, and getting the following exception. 2018-06-06 03:23:51 INFO GridDiscoveryManager:495 - Topology snapshot [ver=3, servers=2, clients=1, CPUs=12, offheap=3.1GB, heap=3.0GB] Exception in thread "main" java.lang.NoSuchMethodEr

RE: Spark Ignite connection using Config file

Hi Bhaskar, I see that you're using spark 2.3, which ignite does not support as of now. https://issues.apache.org/jira/browse/IGNITE-8534 -Original Message- From: bhaskar [mailto:bhaskar.thungathu...@gmail.com] Sent: Wednesday, June 06, 2018 7:26 AM To: user@ignite.apache.org Subject:

Re: [ANNOUNCE] Apache Ignite 2.5.0 Released

Hi While scaling from 100s to 1000s nodes have you by chance changed the way how nodes can be restarted, too, possibly without mentioning that in the docs? I happened to start my adventure with Ignite right after 2.5 was released and could not get this simple thing working properly (details in the

Re: Ignite 2.5 nodes do not rejoin the cluster after restart

I also tested an upgrade of the PoC 2-node cluster running Ignite 2.4 to 2.5. Both nodes shut down, upgraded, started on node1, started on node2, cluster looking healthy with both nodes ONLINE. Then I shut down one of the nodes with "kill -k -al" using batch ignitevisorcmd.sh. Trying to start it br