Re: JDBC Thin Client with Transactions

Hi, I guess 2 scenario behaves considers transactional boundaries because of this feature implemented for DML: https://apacheignite-sql.readme.io/docs/how-ignite-sql-works#section-concurrent-modifications

Fwd: ignite 2.3.0 docker image contains 2.2.0 files.

Nick, Vovan, Have we really upgraded docker and the other images to 2.3? — Denis > Begin forwarded message: > > From: bjason > Subject: ignite 2.3.0 docker image contains 2.2.0 files. > Date: November 2, 2017 at 3:37:34 PM PDT > To: user@ignite.apache.org > Reply-To:

Re: Ignite/Cassandra failing to use supplied value for where clause

Hi Andrey, I tried taking pieces from your example and I still couldn't make it work. First, I removed the annotations out of the POJOs and physically mapped the information in the persistence settings. Still got the error with "my_id". Second, I tried adding the QueryEntity xml config you

Re: How to query to local partition cache data

My answer of question describes below code. Q. How can I query only the data held by Ignite data nodes? A. First, Ignite AffinityFunction is used to send the desired data to one node with partition 1. And, if you are guaranteed to be assigned to 1 partition, use the code below. Use Ignite

ignite 2.3.0 docker image contains 2.2.0 files.

ignite 2.3.0 docker image contains 2.2.0 files. Please check. $ docker pull apacheignite/ignite:2.3.0 2.3.0: Pulling from apacheignite/ignite 3e17c6eae66c: Pull complete 74d44b20f851: Pull complete a156217f3fa4: Pull complete 4a1ed13b6faa: Pull complete 77980e5d0a6d: Pull complete 5458607a81d3:

Re: Trouble with v 2.3.0 on AIX

Vladimir, right now I have no idea what is happening. Maybe Community will help. The stack trace goes deep into Big-Endian code that I cannot even troubleshoot since I have no Big-Endian platform available. Gathering logs might be helpful: I would stop all the nodes, clean

write behind performance impacting main thread. Write behind buffer is never full

I have looked at http://apache-ignite-users.70518.x6.nabble.com/Ignite-Write-Behind-performance-td5385.html which seems similar, but does not answer my question. I am using write behind caching with a single server it has 16 cores and 32 G of memory. My write behind config is

Deadlock detected while accessing caches

Hi, I have a Ignite 2.0 cluster of 8 servers and 8 clients. It has 6 caches which are transactional and partitioned. I use pessimistic transactions with a timeout of 60 seconds. Under performance testing, I found a deadlock message in the log. I have reviewed the code and there is no cyclic

Re: Ignite web console and we agent are running not able to see clusters

Have you input the node uri in the default.properties? or pass it as an argument when u run ignite-web-agent.sh? Thanks, Sherry -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

ignite web agent still has "monitoring" tab?

Hi I am new to Ignite web agent. I deployed the web console on the server and I dont find "monitoring" tab at the top. I would like to know whether this has been canceled? Another question is, for the web

Quick question on Atomic Mode

Hi, I'm in atomic mode and I do a put operation on my cache and a power fail happens in the middle of the put process... does Ignite use the WAL to rollback a partial write? How does it guarantee that the atomic put is an put successfully or do-nothing operation? Thanks,

Re: Using event to reconnect spring created cache client to server

Hi, I don't really understand, what do you mean. At first, a client will try to reconnect to the cluster with the same id and without EVT_CLIENT_NODE_RECONNECTED event. Only if it does not succeed with this, it starts to connect to the cluster with a new id and generates this event. What do you

Re: Unable to query Ignite 2.3 table using 2.2 JDBC thin client

Hello! Unfortunately, it seems that metadata queries are not compatible between 2.1/2.2 and 2.3. The richness of available JDBC metadata was considerably increased in 2.3, and new type value was assigned to metadata responses. Hence, 2.2 client can send metadata request to 2.3, but it is unable

Re: Ignite Cluster Disconnects After Idle Time

Hi, Could you share logs from all nodes? Do you have a firewall configured? Evgenii 2017-11-02 18:44 GMT+03:00 Ramzinator : > Hi all, > > I'm facing hanging issues with my ignite cluster after I leave it idle for > 20 mins. > > The scenario is as follows: > > I have 3

Re: Node failed to startup due to deadlock

Thanks Alexey. Do you have specific information on which operation? Like I said, the only in thread ignite operation we do is ignite Message. How are you seeing issues with cache operations? Are you saying reads are also a problem cause we do reads in ignite thread. Writes are in our own thread.

Re: Node failed to startup due to deadlock

Hi Rajeev, All Ignite callbacks are processed in (=called from) internal Ignite thread pools. The generic rule here is to avoid direct Ignite calls from such callbacks. So, it is better to do all your things in separate threads (use ExecutorService for instance). You should pass all work to your

Re: implement shared RDD in spark streaming in scala

Hi, You can look at my example prepared for Ignite and Spark streaming use cases: https://github.com/dmagda/IgniteSparkIoT The data is being streamed into Ignite through a shared RDD and being queried using Ignite SQL. If you know the keys in advance then you can use Spark native RDDs APIs.

Re: Benchmark results questions

Hi Dmitry, Thanks for you results. I'll try to increase the number of clients as well to see if the throughput can increase. Can you also test the sql query throughput? In my result, it seems with more servers the sql query throughput goes down dramatically. Is there a valid explanation for this

Ignite Cluster Disconnects After Idle Time

Hi all, I'm facing hanging issues with my ignite cluster after I leave it idle for 20 mins. The scenario is as follows: I have 3 ignite nodes in one cluster running, each on a container in docker. The cluster is up, nodes have discovered each other and all is stable. I leave the cluster idle

Using event to reconnect spring created cache client to server

Hello all, am having a issue with reconnection to a spring created ignite cluster, both instances are wrapped in spring boot 1.5.8.RELEASE and Ignite 1.9 Server: @Autowired ApplicationContext context; @Bean public Ignite igniteClient() throws IgniteCheckedException { IgniteConfiguration

Re: How to query to local partition cache data

Below is the best way to do a query based on local data I want. Is this part right? When we do affinityCall, we specify partition 1 and the query is also set to 1. SqlFieldsQuery query = new SqlFieldsQuery ("select sum (count) from data group by id") setPartitions (1); Even if we have a backup,

Re: How to query to local partition cache data

Hi, Thanks for kind of reply. But, I test each query option. setLocal - In my opinion, it seemed that all the nodes were performing on the query. What I wanted to do was that the node responsible for the affinityRun key query only the data. However, as described above, it seemed to load all

Re: Trouble with v 2.3.0 on AIX

No single and simple configuration is available. But notging special: default or slightly changed memory policy, replicated and partitioned caches (mostly atomic), write-through persistence, tcp-discovery, continous queries, services -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Re: Some concern regards the DataRegionConfiguration of the 2.3

Apache Ignite has no data migration/archiving tool but Ignite supports plugins and Ignite native persistence exposes org.apache.ignite.internal.processors.cache.persistence.snapshot.IgniteCacheSnapshotManager that you could use to implement your own tool. There are commercial solutions available,

Re: Re: Some concern regards the DataRegionConfiguration of the 2.3

Got thanks Alexey! Regards Aaron aa...@tophold.com From: Alexey Kukushkin Date: 2017-11-02 17:43 To: user Subject: Re: Some concern regards the DataRegionConfiguration of the 2.3 Hi, When you said "old memory configuration" did you mean using cacheStoreFactory? Ignite has two persistence

Re: Some concern regards the DataRegionConfiguration of the 2.3

Hi, When you said "old memory configuration" did you mean using cacheStoreFactory? Ignite has two persistence options: native and 3rd-party persistence and having cacheStoreFactory configured means you use the latter one. Unlike Ignite native persistence, the 3rd party persistence is slower in

Re: Code deployment throught UriDeploumentSpi

Hello! You can see it here: https://github.com/apache/ignite/pull/2955/files Without fix, testTaskWithServiceRemoteFirst() will fail but testTaskWithServiceLocalFirst() will complete successfully, making it a workaround. But I guess your workaround is just as good as long as it works. -- Ilya

Re: Ignite-cassandra module issue

Hi Tobias, Thank you for explaining how to reproduce it, I'll try your instruction. I spend several days trying to reproduce the issue, but I thought that the reason of this is too high load and I didn't stop client during testing. I'll check your instruction and try to fix the issue. Thanks,

Trouble with v 2.3.0 on AIX

Hi, Just upgraded from Ignite 2.1.0 to v.2.3.0. And now our several nodes cannot start on AIX 7. The error: ERROR 2017-11-02 11:59:01.331 [grid-nio-worker-tcp-comm-1-#22] org.apache.ignite.internal.util.nio.GridDirectParser: Failed to read message [msg=GridIoMessage [plc=0, topic=null,

Re: Ignite Nodes not connecting to cluster in docker swam mode

Hi, Initially I was trying with auto discovery in swarm mode. But as mentioned in post https://stackoverflow.com/questions/35039612/multicast-with-docker-swarm-and-overlay-network Multicast is

Re: Ignite 2.3 still not support group_concat

Hi James, Nice catch! Yes, it's not supported yet. Looks like it was mistakenly added to the documentation in version 2.3. Just suggested deleting this page from the doc. It should be removed soon. Regards, Evgenii 2017-11-02 4:53 GMT+03:00 james wu : > The new ignite 2.3

Re: Benchmark results questions

Hi Ray, I wasn't able to run benchmarks quickly, but I've got following results for atomic put throughput (numbers are a bit lower that could be, because of profiling): Throughput Cluster 264930 1c4s 513775 2c4s 968475 4c4s 281425 1c8s 530597

RE: Where is release notes for 2.3

Thanks, it’s OK! earlier notes weren’t generated http://apache-ignite-developers.2346864.n4.nabble.com/RESULT-VOTE-Apache-Ignite-2-3-0-Release-RC2-td23841.html#a23879 *From:* Evgenii Zhuravlev [mailto:e.zhuravlev...@gmail.com] *Sent:* Thursday, November 2, 2017 10:52 AM *To:*

Re: Where is release notes for 2.3

Hi, Just checked the link you provided and everything works fine. Which error code do you get? Could you check this link again? Regards, Evgenii 2017-11-01 20:28 GMT+03:00 Timofey Fedyanin : > Hi! > > URL from downloads page is bad (https://ignite.apache.org/ >

Re: JDBC Thin Client with Transactions

Hi Denis, I tested the transactional nature using SqlFieldsQuery and cache.get()/cache.put() in PESSIMISTIC & REPEATABLE_READ mode. case 1: update using SqlFieldsQuery in one transaction and read using SqlFieldsQuery in another transaction on the same record and we didn't commit any of the

Some concern regards the DataRegionConfiguration of the 2.3

hi All, We are upgrading to the 2.3, so as recommend we should use the DataRegionConfiguration instead of the old memory configuration. if we set the persistenceEnabled to true; but meaning-while the cache we set the cacheStoreFactory. should we only keep one of them? otherwise they will

Questions regarding Ignite as hdfs cache

Hello, I am evaluating Ignite to be able to use it as a hdfs cache to speedup my hive queries. I am using hive with tez. Below are my cluster and Ignite configurations, *Cluster: * 4 data nodes with 32gb RAM each, 1 edge node 4 ignite servers, one for each data node. Ignite servers were started