Hello, How often will end users invoke this functionality? It sounds somewhat like an administrative function.
If it won't be invoked frequently, and its function is not on par with get(), put(), etc., I would propose to add the method to IgniteCacheEx instead, to avoid excessively polluting IgniteCache. Raúl. On 13 Jan 2016 13:23, "Vladimir Ershov" <[email protected]> wrote: > Igniters! > > Since we are going to add stronger data loss check IGNITE-1605 > <https://issues.apache.org/jira/browse/IGNITE-1605> I'm about to add new > method for the manual resetting state of the lost partition in IgniteCache > IgniteFuture<?> *resetLostPartitions*(); > just near #rebalance(). > > And would like to ask the community: Does *resetLostPartitions *naming > sound good? > Thoughts appreciated, > Thanks! >
