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

ASF GitHub Bot commented on IGNITE-9270:
----------------------------------------

GitHub user Jokser opened a pull request:

    https://github.com/apache/ignite/pull/4587

    IGNITE-9270 Thread-per-partition during Tx commit

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/gridgain/apache-ignite ignite-9270

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/ignite/pull/4587.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #4587
    
----
commit c396b4e7d682c45aa2ce70bbe1aa22a30a668a63
Author: Pavel Kovalenko <jokserfn@...>
Date:   2018-08-16T16:09:01Z

    IGNITE-9270 WIP

commit 4c8ebbd5e8176c93583e1d6dd808608a0fa69c3d
Author: Pavel Kovalenko <jokserfn@...>
Date:   2018-08-16T17:23:43Z

    IGNITE-9270 WIP

commit 1778b8e8b71d748f5305cc3f0e4a21c35c7b3067
Author: Pavel Kovalenko <jokserfn@...>
Date:   2018-08-16T17:41:21Z

    IGNITE-9270 WIP

commit f6c7621704a63b411e71e87fd0d048ff1a80755e
Author: Pavel Kovalenko <jokserfn@...>
Date:   2018-08-21T13:10:04Z

    IGNITE-9270 WIP

----


> Design thread per partition model
> ---------------------------------
>
>                 Key: IGNITE-9270
>                 URL: https://issues.apache.org/jira/browse/IGNITE-9270
>             Project: Ignite
>          Issue Type: Sub-task
>          Components: cache
>            Reporter: Pavel Kovalenko
>            Assignee: Pavel Kovalenko
>            Priority: Major
>              Labels: thread-per-partition
>             Fix For: 2.7
>
>
> A new model of executing cache partition operations (READ, CREATE, UPDATE, 
> DELETE) should satisfy following conditions
> 1) All modify operations (CREATE, UPDATE, DELETE) on some partition must be 
> performed by the same thread. 
> 2) Read operations can be executed by any thread.
> 3) Ordering of modify operations on primary and backup nodes should be same.
> We should investigate performance if we choose dedicated executor service for 
> such operations, or we can use a messaging model to use network threads to 
> perform such operations.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to