[
https://issues.apache.org/jira/browse/IGNITE-28069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksey Plekhanov updated IGNITE-28069:
---------------------------------------
Description: Currently, consistency repair ({{control.sh --consistency
repair}}) requires event EVT_CONSISTENCY_VIOLATION to be enabled statically in
configuration, which requires cluster restart on if event was not configured
properly (by default). But we can enable this event in runtime during this
command execution and avoid cluster restart or enable it by default. (was:
Currently, consistency repair ({{control.sh --consistency repair}}) requires
event EVT_CONSISTENCY_VIOLATION to be enabled statically in configuration,
which requires cluster restart on if event was not configured properly (by
default). But we can enable this event in runtime during this command execution
and avoid cluster restart.)
> Automatically enable EVT_CONSISTENCY_VIOLATION event on consistency repair
> --------------------------------------------------------------------------
>
> Key: IGNITE-28069
> URL: https://issues.apache.org/jira/browse/IGNITE-28069
> Project: Ignite
> Issue Type: Improvement
> Reporter: Aleksey Plekhanov
> Assignee: Aleksey Plekhanov
> Priority: Major
> Labels: ise
> Fix For: 2.19
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Currently, consistency repair ({{control.sh --consistency repair}}) requires
> event EVT_CONSISTENCY_VIOLATION to be enabled statically in configuration,
> which requires cluster restart on if event was not configured properly (by
> default). But we can enable this event in runtime during this command
> execution and avoid cluster restart or enable it by default.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
