Hi, To avoid any downtime here I would recommend to load the new data set in the same cache and remove the old entries from there once the preloading is finished. This approach assumes that both old and new entries can co-exist in the cache.
— Denis > On Oct 23, 2017, at 7:13 AM, blackfield <charles.kat...@maxpoint.com> wrote: > > > The use case is similar to OP. > > We have a large table that we import/load from a dataset. > > This dataset is generated periodically such that we need to re-load this > whole dataset to Ignite. > > If we re-load the new dataset against the same Ignite table, the users will > be impacted during that window. > > We are looking for ways to minimize the impact, e.g. load the data to > another table->perform swap, etc. > > Let me know if there are existing capabilities to minimize the above > scenario. > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/
