[jira] [Resolved] (IGNITE-20536) No-op handlers for StripedDisruptor.StripeEntryHandler#subscribers

["Vladislav Pyatkov (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/IGNITE-20536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vladislav Pyatkov resolved IGNITE-20536.
----------------------------------------
    Fix Version/s: 3.0.0-beta2
       Resolution: Duplicate

This issue is not a real duplicate of IGNITE-15568, but the descition that had been applied in the tiket above resolved it. 

> No-op handlers for StripedDisruptor.StripeEntryHandler#subscribers
> ------------------------------------------------------------------
>
>                 Key: IGNITE-20536
>                 URL: https://issues.apache.org/jira/browse/IGNITE-20536
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Sergey Uttsel
>            Assignee: Vladislav Pyatkov
>            Priority: Major
>              Labels: ignite-3
>             Fix For: 3.0.0-beta2
>
>
> h3. Motivation
> In https://issues.apache.org/jira/browse/IGNITE-20397 we discussed that it is possible to get null handler in StripedDisruptor.StripeEntryHandler#onEvent on a table drop. And we start to use a log warning instead of an assert.
> But this is not the best solution. We still need to assert that handler is not null on first event for the partition. And we need to skip events if the partition was removed. So we need:
>  # to add assert that `handler != null`,
>  # on StripedDisruptor.StripeEntryHandler#unsubscribe put a no-op handler to a subscribers map instead of remove it,
>  # to remove the no-op handler when there are no events for this handler.
> h3. Definition of done:
>  # assert that `handler != null` is added,
>  # no-op handler on StripedDisruptor.StripeEntryHandler#unsubscribe,
>  # remove handler when it is not needed



--
This message was sent by Atlassian Jira
(v8.20.10#820010)