[jira] [Created] (IGNITE-4680) Properly split batch atomic cache operations between stripes (putAll, removeAll, etc)

[Anton Vinogradov (Jira)]

Yakov Zhdanov created IGNITE-4680:
-------------------------------------

             Summary: Properly split batch atomic cache operations between stripes (putAll, removeAll, etc)
                 Key: IGNITE-4680
                 URL: https://issues.apache.org/jira/browse/IGNITE-4680
             Project: Ignite
          Issue Type: Improvement
          Components: cache
            Reporter: Yakov Zhdanov
            Assignee: Yakov Zhdanov
             Fix For: 2.0


Need to revisit keys/requests mapping procedure and map the update directly to stripe on remote node.
Here are some points:
# Abovementioned will require adding stripes count attribute to node's attribute list
# Need to make sure we take all benefits of biased locking and stripes never get mutually blocked
# locking all entries before processing request can be removed since it does not make too much sense to atomic cache



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[Константин Дудков]

Yakov,

If you don't mind I would like to do this ticket.

10.02.2017, 16:31, "Yakov Zhdanov (JIRA)" <[hidden email]>:

> Yakov Zhdanov created IGNITE-4680:
> -------------------------------------
>
>              Summary: Properly split batch atomic cache operations between stripes (putAll, removeAll, etc)
>                  Key: IGNITE-4680
>                  URL: https://issues.apache.org/jira/browse/IGNITE-4680
>              Project: Ignite
>           Issue Type: Improvement
>           Components: cache
>             Reporter: Yakov Zhdanov
>             Assignee: Yakov Zhdanov
>              Fix For: 2.0
>
> Need to revisit keys/requests mapping procedure and map the update directly to stripe on remote node.
> Here are some points:
> # Abovementioned will require adding stripes count attribute to node's attribute list
> # Need to make sure we take all benefits of biased locking and stripes never get mutually blocked
> # locking all entries before processing request can be removed since it does not make too much sense to atomic cache
>
> --
> This message was sent by Atlassian JIRA
> (v6.3.15#6346)

--
С уважением,
Константин Дудков
[hidden email]

[yzhdanov]

Konstantin, please go ahead.

--Yakov

2017-02-11 20:18 GMT+03:00 Константин Дудков <[hidden email]>:

> Yakov,
>
> If you don't mind I would like to do this ticket.
>
> 10.02.2017, 16:31, "Yakov Zhdanov (JIRA)" <[hidden email]>:
> > Yakov Zhdanov created IGNITE-4680:
> > -------------------------------------
> >
> >              Summary: Properly split batch atomic cache operations
> between stripes (putAll, removeAll, etc)
> >                  Key: IGNITE-4680
> >                  URL: https://issues.apache.org/jira/browse/IGNITE-4680
> >              Project: Ignite
> >           Issue Type: Improvement
> >           Components: cache
> >             Reporter: Yakov Zhdanov
> >             Assignee: Yakov Zhdanov
> >              Fix For: 2.0
> >
> > Need to revisit keys/requests mapping procedure and map the update
> directly to stripe on remote node.
> > Here are some points:
> > # Abovementioned will require adding stripes count attribute to node's
> attribute list
> > # Need to make sure we take all benefits of biased locking and stripes
> never get mutually blocked
> > # locking all entries before processing request can be removed since it
> does not make too much sense to atomic cache
> >
> > --
> > This message was sent by Atlassian JIRA
> > (v6.3.15#6346)
>
> --
> С уважением,
> Константин Дудков
> [hidden email]
>