[
https://issues.apache.org/jira/browse/IGNITE-9785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16637070#comment-16637070
]
ASF GitHub Bot commented on IGNITE-9785:
----------------------------------------
GitHub user glukos opened a pull request:
https://github.com/apache/ignite/pull/4907
IGNITE-9785 Introduce read-only state in local node context
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9785
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/4907.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 #4907
----
commit 9a40d52662a115755d3e89931ff24c55ca4b377c
Author: Aleksey Plekhanov <plehanov.alex@...>
Date: 2018-10-03T15:11:08Z
TDR-18 Read-only mode
Signed-off-by: Ivan Rakov <[email protected]>
----
> Introduce read-only state in local node context
> -----------------------------------------------
>
> Key: IGNITE-9785
> URL: https://issues.apache.org/jira/browse/IGNITE-9785
> Project: Ignite
> Issue Type: New Feature
> Reporter: Ivan Rakov
> Assignee: Aleksey Plekhanov
> Priority: Major
> Fix For: 2.8
>
>
> It would be useful to have option to switch "read-only" state on Ignite node.
> Under read-only state:
> 1) Any attempt to update data via Cache API should throw exception
> 2) Any attempt to update data via DataStreamer should throw exception
> Local read-only state may be helpful in further implementing global read-only
> cluster state, which can be switched via user API.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
