Hi, In case of rebalance the reserves aren't recalculated. So the next values will be in the range [1001,1000+reserveSize]. After the local reserve exceeds, the node reserves a new range starting from the global last sequence number. The main idea IgniteAtomicSequence is to generate unique numbers but it doesn't guarantee ordering. If you need ordering you could set the reserve size to 1 or use IgniteAtomicLong.
Thanks, Pavel вс, 25 окт. 2020 г. в 05:00, narges saleh <[email protected]>: > Hi All, > What is the consequence of data rebalancing across nodes as far as > IgniteAtomicSequence and the reserve on each node is concerned? For > example, if the last sequence number is 6000 in one node and the record > moves to a node whose last sequence number is 1000? Do the reserves on both > nodes get recalculated? > > Are there best practices for generating and using these sequences? > > Is IgniteAtomicSequence the right approach if I want to keep track of the > records on each node for a partitioned cache? > > thanks. > -- Regards Pavel Vinokurov
