[
https://issues.apache.org/jira/browse/IGNITE-22247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Puchkovskiy updated IGNITE-22247:
---------------------------------------
Description:
Sometimes, a partition cannot be started during node startup (due to a bug). In
tests, it makes sense to fail node start to make the problem visible. But in
production it probably makes sense to start whatever partititions we can and
let the user know that some partitions are in a 'broken' state.
Currently, we just ignore such errors.
The proposal is to make this 'brokenness' information available via partition
state API and partition state metrics. In tests, we can query the API/metrics
and fail the node if some partition is broken.
> Handle 'partition cannot be started at Ignite node startup' situation
> ---------------------------------------------------------------------
>
> Key: IGNITE-22247
> URL: https://issues.apache.org/jira/browse/IGNITE-22247
> Project: Ignite
> Issue Type: Improvement
> Reporter: Roman Puchkovskiy
> Priority: Major
> Labels: ignite-3
>
> Sometimes, a partition cannot be started during node startup (due to a bug).
> In tests, it makes sense to fail node start to make the problem visible. But
> in production it probably makes sense to start whatever partititions we can
> and let the user know that some partitions are in a 'broken' state.
> Currently, we just ignore such errors.
> The proposal is to make this 'brokenness' information available via partition
> state API and partition state metrics. In tests, we can query the API/metrics
> and fail the node if some partition is broken.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
