[IGNITE-17062] Add ability to process local events asynchronously

• Type: Task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Labels: ignite-3
• Assignee: Denis Chudov
• Reporter: Alexander Lapin
• Created: 31/May/22 10:24
• Updated: 01/Nov/22 17:12
• Resolved: 07/Jul/22 12:44

Description

Local events (org.apache.ignite.internal.manager.Event) logic should be reworked a bit in order to await all subscribers to process corresponding event before publishing the action. Let's check an example of an expected behavior:

1. TableManager prepares table for creation.
2. TableManager notifies all subscribers with Table.CREATE event propagating to-be-created table.
3. TableManager (with the help of org.apache.ignite.internal.manager.Producer) awaits all subscribers to acknowledge that Table.CREATE event was successfully processed. E.g.  SqlQueryProcessor prepares calcite schemes and sends ack by completing event's Future like it's done within ConfigurationRegistry events.
4. TableManager on Compound-Like-Future.allOff(events) publishes corresponding action, e.g. makes table visible to everyone.

Proposed solution is very similar to what we already have in ConfigurationRegistry

public interface ConfigurationListener<VIEWT> {
    /**
     * Called on property value update.
     *
     * @param ctx Notification context.
     * @return Future that signifies the end of the listener execution.
     */
    CompletableFuture<?> onUpdate(ConfigurationNotificationEvent<VIEWT> ctx);
}

Issue Links

• links to: GitHub Pull Request #906
• links to: PR