Re: What is the most efficient way to scan all data partitions?

When running on AWS, I found that what the "disk" that you are writing to is the most critical issue for Ignite. EC2 instances with local SSDs have about 20x the write rate as a multiple 3 TB GP2 problems, and using actual disks (e.g., EBS) for Ignite Persistence storage is a non-starter.

Re: Backup and Restore of Ignite Persistence

Hi, Yes Ignite store the data into files. For every cache entity could exist some primiry node and optionally several backups node. It could be configured in CacheConfiguration. Read about it you can here: https://apacheignite.readme.io/v1.1/docs/primary-and-backup-copies For example you have

Re: What is the most efficient way to scan all data partitions?

Hi, It's normal that writing to disk is causing the degradation. You can do several optimizations to speed up writting to disk: https://apacheignite.readme.io/docs/durable-memory-tuning https://apacheignite.readme.io/docs/performance-tips However you can try to test your example with next

Re: Ignite web console query

There won't be an option to disable it (as there is no option to turn off MogoDB right now). The persistence will keep user credentials as well as statistics on long running queries. -- Denis On Tue, May 8, 2018 at 10:08 PM, vbm wrote: > Hi Denis, > > Just curious to know,

Re: Inconsistency reading cache from code and via REST?

Hi, qryexe doesn't work correct. At some reason it ignores _key and _value in 2.4. You can use qryfldexe as it was describe here: http://apache-ignite-users.70518.x6.nabble.com/Example-of-SQL-query-td21427.html BR, Andrei -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Example of SQL query

Hi again, We already discussed about it recently. At the moment some things works incorrect in 2.4: 1)Rest API only support String as key and value. And looks like you can't use affinity key on strings for the same issue. But if you can setup it using AffinityKeyMapper anotation: public

Backup and Restore of Ignite Persistence

hi, I am planning to have some important tables on Apache Ignite Persistence and therefore am looking for best practices and recommendations around backup and restore of Ignite Persistence layer. As I understand, Ignite stores data in standard files. Will just taking a backup of these files

Re: Local Client not connecting to Server deployed in azure cloud.

Hi, Please check that 47101 port is accessible and try to run with argument -Djava.net.preferIPv4Stack=true Thanks, Pavel 2018-05-09 5:55 GMT+03:00 JP : > Hi, >I have running ignite servers and clusters running in Azure cloud West > US > region. > > I am trying to