ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexey Goncharuk (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-3456) Make sure EntryProcessor is always running on a OWNING partition
Date Fri, 08 Jul 2016 19:02:11 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-3456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15368206#comment-15368206

Alexey Goncharuk commented on IGNITE-3456:

Linking the late affinity assignment ticket.

> Make sure EntryProcessor is always running on a OWNING partition
> ----------------------------------------------------------------
>                 Key: IGNITE-3456
>                 URL: https://issues.apache.org/jira/browse/IGNITE-3456
>             Project: Ignite
>          Issue Type: Improvement
>          Components: cache
>            Reporter: Alexey Goncharuk
> Let's say I need to maintain some sort of an aggregate function over a partition. This
aggregate is maintained using an entry processor, and before an update this entry processor
queries this local aggregate.
> If an entry processor is applied on a partition with a MOVING state, the state of the
local aggregate is not valid because not all data has been preloaded. If entry processor is
applied on an OWNING partition, the result is guaranteed to be correct.
> Given that we have implemented late affinity assignment when a new node is assigned primary
only when rebalancing is finished, this should be already maintained. We just need to add
tests verifying the partition state in EntryProcessor.

This message was sent by Atlassian JIRA

View raw message