Hi, Actually, you cache is splitted to partitions that distributed among cache data nodes. With no of backups > 0, you will just have additional partition copies in grid and there is a guarantee you will never have more than 1 copy of data within every single node. Also, every node can be either "primary node" for a partition or "backup node" for a partition (or it have no copy of the partition).
SQL query works only with primary data. So, you will not get any scale with increasing of replication factor. >From 1.9 you can *setQueryParallelism* level to scale-up SQL query. Note, it will work only with query on partitioned caches with same query-parallelism-level. Distributed joins "partitioned with partitioned" and "partitioned with replicated" supports this feature as well. On Mon, Apr 17, 2017 at 12:19 PM, tuco.ramirez <[email protected]> wrote: > Thanks, a follow up. > If i have 2 replicas(no of backups =2), then will each SQL query still use > all masters/slaves or a combination. > Basically i am trying to find out if the reads can scale with SQL query if > we increase the replication factor. > > > > -- > View this message in context: http://apache-ignite-users. > 70518.x6.nabble.com/Basic-question-on-scaling-of-reads- > with-ignite-sql-queries-tp11975p11992.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. > -- Best regards, Andrey V. Mashenkov
