[jira] [Commented] (IGNITE-3333) IGFS: Allow for ATOMIC data cache.
[ https://issues.apache.org/jira/browse/IGNITE-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15523664#comment-15523664 ] ASF GitHub Bot commented on IGNITE-: Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1108 > IGFS: Allow for ATOMIC data cache. > -- > > Key: IGNITE- > URL: https://issues.apache.org/jira/browse/IGNITE- > Project: Ignite > Issue Type: Sub-task > Components: IGFS >Affects Versions: 1.6 >Reporter: Vladimir Ozerov >Assignee: Taras Ledkov >Priority: Critical > Labels: performance > Fix For: 1.8 > > > Currently data cache must be transactional. It means that some updates even > on single key will require 2PC. Instead, it makes sense to try change update > logic to work always on single keys. In this case we will be able to switch > to ATOMIC cache, what could improve performance dramatically. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-3333) IGFS: Allow for ATOMIC data cache.
[ https://issues.apache.org/jira/browse/IGNITE-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15516296#comment-15516296 ] Taras Ledkov commented on IGNITE-: -- The fix contains only new tests for ATOMIC mode and changes at the validation of IGFS data cache configuration. [Tests|http://195.239.208.174/project.html?projectId=IgniteTests&tab=projectOverview&branch_IgniteTests=pull%2F1108%2Fhead] results > IGFS: Allow for ATOMIC data cache. > -- > > Key: IGNITE- > URL: https://issues.apache.org/jira/browse/IGNITE- > Project: Ignite > Issue Type: Sub-task > Components: IGFS >Affects Versions: 1.6 >Reporter: Vladimir Ozerov >Assignee: Taras Ledkov >Priority: Critical > Labels: performance > Fix For: 1.8 > > > Currently data cache must be transactional. It means that some updates even > on single key will require 2PC. Instead, it makes sense to try change update > logic to work always on single keys. In this case we will be able to switch > to ATOMIC cache, what could improve performance dramatically. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-3333) IGFS: Allow for ATOMIC data cache.
[ https://issues.apache.org/jira/browse/IGNITE-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15516268#comment-15516268 ] ASF GitHub Bot commented on IGNITE-: GitHub user tledkov-gridgain opened a pull request: https://github.com/apache/ignite/pull/1108 IGNITE- IGFS: Allow for ATOMIC data cache. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite- Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/1108.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 #1108 commit 29f508b17eb383a1c910c72e7d5056564acc37c2 Author: vozerov-gridgain Date: 2016-09-23T07:59:55Z IGNITE-3925: Output process ID to the log on node start. commit 40f647258a10fa8b42ac6fda67d6fa4db71b8100 Author: Anton Vinogradov Date: 2016-09-08T15:58:31Z IGNITE-3874 sync putIfAbsent forever blocked on all nodes after one node is stopped commit 062ecd75908131084e27883f3f160f3504e92165 Author: tledkov-gridgain Date: 2016-09-23T11:05:17Z IGNITE-3931: IGFS: Test fixes for PROXY mode. This closes #1102. commit 4ff401b555f067dbbdf810f1a43228d174d2f238 Author: vozerov-gridgain Date: 2016-09-23T11:05:27Z Merge remote-tracking branch 'upstream/ignite-1.6.9' into ignite-1.6.9 commit cac4720ca49922cc96b526d94820f42d38789e4c Author: tledkov-gridgain Date: 2016-09-23T08:42:00Z IGNITE- IGFS: Allow for ATOMIC data cache > IGFS: Allow for ATOMIC data cache. > -- > > Key: IGNITE- > URL: https://issues.apache.org/jira/browse/IGNITE- > Project: Ignite > Issue Type: Sub-task > Components: IGFS >Affects Versions: 1.6 >Reporter: Vladimir Ozerov >Assignee: Taras Ledkov >Priority: Critical > Labels: performance > Fix For: 1.8 > > > Currently data cache must be transactional. It means that some updates even > on single key will require 2PC. Instead, it makes sense to try change update > logic to work always on single keys. In this case we will be able to switch > to ATOMIC cache, what could improve performance dramatically. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
