Best way to update the partition id in database after rebalancing

[Sumanta Ghosh <su...@yahoo.com>]

Hi,
In the documentation, it is mentioned that in order to ensure that a
particular node only loads the data relevant for the partitions it has, it
is advisable to store the partition id in the database. In that case, what
would be the best practice to update the partition id when new node is added
and the data gets re-balanced.



--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Best-way-to-update-the-partition-id-in-database-after-rebalancing-tp11026.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Best way to update the partition id in database after rebalancing

[Sumanta Ghosh <su...@yahoo.com>]

Hi Val,
Thanks a lot. I was thinking of data streamer - data loader is good enough
for now it seems :).



--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Best-way-to-update-the-partition-id-in-database-after-rebalancing-tp11026p11042.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Best way to update the partition id in database after rebalancing

[vkulichenko <va...@gmail.com>]

There is no need to do this. Key to partition mapping is constant and doesn't
depend on how many nodes are in topology.

-Val



--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Best-way-to-update-the-partition-id-in-database-after-rebalancing-tp11026p11033.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.