Hi, You wrote you use persistence=enabled. Looks like you try to start cache with changed (backup=2) configuration without recreating the cache, grid restore cache from store with its config and doesn't apply a new one.
Looks weird that neither new number of backups wasn't applied nor error occurs. Can you confirm if it is so and recreate cache resolve the issue? On Thu, Oct 19, 2017 at 9:29 PM, blackfield <[email protected]> wrote: > Here, I am trying to ascertain that I set backup == 2 properly as I > mentioned > above that I do not see query performance difference between backup ==1 and > backup == 2. > > I want to make sure that I configure my cache properly. > > When I set the backup==2 (to have three copies), I notice the following via > visor. > > The Affinity Backups is still equal to 1. Is this a different property than > number of backups? If it is not, how do one see the number of backups a > cache is configured for? > > Invoking "cache -a" to see the detail cache stat, with backup==2, under the > size column, the sum of entries on all nodes is equal to the number of rows > in the table * 2. It appears this is the case for backup >= 1? > > As in, only one set of backup will be stored in off heap regardless the > number of backups are specified? > > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ > -- Best regards, Andrey V. Mashenkov
