[
https://issues.apache.org/jira/browse/IGNITE-21205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Bessonov updated IGNITE-21205:
-----------------------------------
Description:
Current implementation blocks meta-storage watch thread (doesn't allow new
watch events to be processed, to be precise) until new schema version is
written into the meta-storage. This is an expensive IO operation, and it might
introduce unexpected turbulence.
Some scenarios greatly suffer from it. For example, we can't process lease
updates while we're writing into meta-storage, which shouldn't be the case.
was:
Current implementation blocks meta-storage watch thread until new schema
version is written into the meta-storage. This is an expensive IO operation,
and it might introduce unexpected turbulence.
Some scenarios greatly suffer from it. For example, we can't process lease
updates while we're writing into meta-storage, which shouldn't be the case.
> Don't store table versions in meta-storage in SchemaManager
> -----------------------------------------------------------
>
> Key: IGNITE-21205
> URL: https://issues.apache.org/jira/browse/IGNITE-21205
> Project: Ignite
> Issue Type: Improvement
> Reporter: Ivan Bessonov
> Assignee: Ivan Bessonov
> Priority: Major
> Labels: ignite-3
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Current implementation blocks meta-storage watch thread (doesn't allow new
> watch events to be processed, to be precise) until new schema version is
> written into the meta-storage. This is an expensive IO operation, and it
> might introduce unexpected turbulence.
> Some scenarios greatly suffer from it. For example, we can't process lease
> updates while we're writing into meta-storage, which shouldn't be the case.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
