Hi, ignite split every cache into some number of partitions and store partitions on cluster nodes. It decide where to store data by two step: 1) calculate partitionId by key (long in your case) 2) calculate affinity function by partitionId and cluster topology. For every partition affinity function return list of nodes: master, backup1, backup2,... (if you specify backups in cache configuration). Ignite will store partition accordingly this list. If you specify node filter in cache configuration - ignite will use only appropriate nodes (i.e. it will use only filtered nodes in affinity function) and if you use standard affinity finction - it will try to distribute equivalent numbers of partition to all nodes. In docs we have pretty pictures for it: https://apacheignite.readme.io/docs/cache-modes#partitioned-mode . What exactly are you interested in?
2017-05-18 13:16 GMT+07:00 rushi_rashi <[email protected]>: > Hi, > > I have a cache partitioned on 4 nodes and having 6 ignite instance per > node. > The key used for storing data is of type long. > I want to know how ignite decides where to store data. > > > > -- > View this message in context: http://apache-ignite-users. > 70518.x6.nabble.com/How-Cache-Management-Works-tp12987.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. >
