[
https://issues.apache.org/jira/browse/IGNITE-17515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mirza Aliev updated IGNITE-17515:
---------------------------------
Description:
Currently, {{tablesByIdVv}}, which is holding the mapping for table ids and
table implementations, is updated through the mechanism of versioned values,
and {{tablesByIdVv}} is dependent on a list of other versioned values, like
schema versioned value, calcite versioned value and etc. If one of this
versioned value is completed exceptionally, {{tablesByIdVv}} will also be
completed exceptionally, and that means that we cannot access to the the
mapping for table ids and tables, and actually that means, that all tables will
be unreachable.
Also, that means, that tables can't be properly stopped, which can lead to
resource leaking.
Expected behaviour is when exceptional situations for {{tablesByIdVv}} updates
are handled, tables, that weren't participated in the updated, still
accessible, and tables, that were affected, properly stopped.
was:
Currently, {{tablesByIdVv}}, which is holding the mapping for table ids and
table implementations, is updated through the mechanism of versioned values,
and {{tablesByIdVv}} is dependent on a list of other versioned values, like
schema versioned value, calcite versioned value and etc. If one of this
versioned value is completed exceptionally, {{tablesByIdVv}} will also be
completed exceptionally, and that means that we cannot access to the the
mapping for table ids and tables, and actually that means, that all tables will
be unreachable.
Also, that means, that tables can't be properly stopped, which can lead to
Expected behevio
> tablesByIdVv exceptional completing can lead to resource leaking
> ----------------------------------------------------------------
>
> Key: IGNITE-17515
> URL: https://issues.apache.org/jira/browse/IGNITE-17515
> Project: Ignite
> Issue Type: Task
> Reporter: Mirza Aliev
> Priority: Major
> Labels: ignite-3
>
> Currently, {{tablesByIdVv}}, which is holding the mapping for table ids and
> table implementations, is updated through the mechanism of versioned values,
> and {{tablesByIdVv}} is dependent on a list of other versioned values, like
> schema versioned value, calcite versioned value and etc. If one of this
> versioned value is completed exceptionally, {{tablesByIdVv}} will also be
> completed exceptionally, and that means that we cannot access to the the
> mapping for table ids and tables, and actually that means, that all tables
> will be unreachable.
> Also, that means, that tables can't be properly stopped, which can lead to
> resource leaking.
> Expected behaviour is when exceptional situations for {{tablesByIdVv}}
> updates are handled, tables, that weren't participated in the updated, still
> accessible, and tables, that were affected, properly stopped.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
