Denis, it seems noone is working.
чт, 22 мар. 2018 г. в 21:26, Denis Magda :
> Igniters,
>
> Is anybody working on this bug? There is a high chance we can add a fix to
> 2.5 if the community agrees to release it earlier.
>
> --
> Denis
>
> On Thu, Mar 15, 2018 at 11:04 AM, Denis Magda wrote:
>
>
Igniters,
Is anybody working on this bug? There is a high chance we can add a fix to
2.5 if the community agrees to release it earlier.
--
Denis
On Thu, Mar 15, 2018 at 11:04 AM, Denis Magda wrote:
> I dared to set fix version to 2.5 and increased the severity. It's
> important to fix the race
I dared to set fix version to 2.5 and increased the severity. It's
important to fix the race since we've just released the partition loss
functionality in 2.4 and it's already broken.
Andrey, please keep us posted. If you didn't fix it, we would need to find
another contributor.
--
Denis
On Thu,
Hi Andrew Mashenkov,
would you like to pick up issue?
Sincerely,
Dmitriy Pavlov
чт, 15 мар. 2018 г. в 6:23, Dmitriy Setrakyan :
> Completely agree, we must fix this. I like the proposed design. We should
> also specify that resetLostPartitions() method should return true and
> false.
>
> Val, d
Completely agree, we must fix this. I like the proposed design. We should
also specify that resetLostPartitions() method should return true and false.
Val, do you mind updating the ticket with new design?
https://issues.apache.org/jira/browse/IGNITE-7832
D.
On Tue, Mar 13, 2018 at 5:31 PM, Valen
This indeed looks like a bigger issue. Basically, there is no clear way (or
no way at all) to synchronize code that listens to partition loss event,
and the code that calls resetLostPartitions() method. Example scenario:
1. Cache is configured with 3rd party persistence.
2. One or more nodes fail
Just in case here is you can find the present documentation:
https://apacheignite.readme.io/docs/cache-modes#partition-loss-policies
Let us know what needs to be updated once the issues reported by you are
addressed.
--
Denis
On Mon, Mar 12, 2018 at 3:33 AM, Andrey Mashenkov <
andrey.mashen...@g
Dmitry,
Not yet, it looks like architectural issue.
Ignite provide a error prone method for resetLostPartition state in public
API.
However, IGNITE-5302 is about issue during node startup. I'd think we can
use some internals (e.g. topology version) to workaround this.
If you are sure IGNITE-5302
Hi Andrey,
I remember some issue was also found in tests:
https://issues.apache.org/jira/browse/IGNITE-5302
Is this a consequence of the same problem?
Sincerely,
Dmitriy Pavlov
пн, 12 мар. 2018 г. в 13:34, Andrey Mashenkov :
> Hi Igniters,
>
> I've found we no documentation how user can recov
Hi Igniters,
I've found we no documentation how user can recover cache from cacheStore
in case of partition loss.
Ignite provides some instruments (methods and events) that should help user
to solve this problem,
but looks like these instruments have an architecture lack.
The first one is an usab
10 matches
Mail list logo