ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Taras Ledkov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-7778) User's authentication data must be persisted on cluster with disabled persistence
Date Fri, 01 Jun 2018 14:34:00 GMT

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

Taras Ledkov commented on IGNITE-7778:
--------------------------------------

The root cause of the performance drop is acquire checkpoint read lock for in-memory cache
operations.

[~vozerov], [~gvvinblade], [~agoncharuk], please review the changes of the checkpoint read
lock usage.
General purpose: don't acquire checkpoint read lock when only in-memory caches are affected.

The patch has no performance drop for in-memory cache operations when compared to the master
branch. 


> User's authentication data must be persisted on cluster with disabled persistence
> ---------------------------------------------------------------------------------
>
>                 Key: IGNITE-7778
>                 URL: https://issues.apache.org/jira/browse/IGNITE-7778
>             Project: Ignite
>          Issue Type: Task
>            Reporter: Taras Ledkov
>            Assignee: Taras Ledkov
>            Priority: Major
>
> The ticket is related to the: IGNITE-7436 (introduce users in Ignite)
> {{IgniteAuthenticationProcessor}} uses metastorage to persist user data. But metastorage
works only with persistent cluster. We have to support user authentication for in-memory cluster.



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

Mime
View raw message