[
https://issues.apache.org/jira/browse/IGNITE-21387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17837121#comment-17837121
]
Mikhail Efremov commented on IGNITE-21387:
------------------------------------------
At the current state, the following changes are done:
* In {{ItDistributionZonesFiltersTest}} the single
testFilteredDataNodesPropagatedToStable test was divided on 3 separate
tests:{color:#6b2fba}
{color}
**
{{testDataNodesByFilterPropagatedToStable}} that tests only by attribute
filtering by specified region and storage filter;
**
{{testDataNodesByProfilePropagatedToStable}} that tests only by matching
profile name;
**
{{testDataNodesByFilterAndProfilePropagatedToStable}} tests both cases
together: attribute filters and profile both.
* In {{TableManager}} was done refactoring:
** exctracting assignments creation into the separate method
{{createOrGetLocallyAssignmentsAsync}} along as
{{writeTableAssignmentsToMetastore;
}}
> Recovery is not possible, if node have no needed storage profile
> ----------------------------------------------------------------
>
> Key: IGNITE-21387
> URL: https://issues.apache.org/jira/browse/IGNITE-21387
> Project: Ignite
> Issue Type: Improvement
> Reporter: Kirill Gusakov
> Assignee: Mikhail Efremov
> Priority: Major
> Labels: ignite-3
>
> Looks like any table try to create storages on the recovery node, even if is
> shouldn't be here, because of zone storage profile filter.
> The isssue is reproducing by
> ItDistributionZonesFiltersTest#testFilteredDataNodesPropagatedToStable. So,
> test must be enabled or reworked by this ticket.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
