Adding OSS Notification Classes for SMIGRATING and SMIGRATED. Handling of SMIGRATING is completed and covered with tests. #3849
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge. Suggestion cannot be applied right now. Please check back later.
In this PR the following changes are introduced:
OSS Notification Classes: New
OSSNodeMigratingNotificationandOSSNodeMigratedNotificationclasses that track slot migration events with source/destination nodes and affected slotsThread-Safe Handler:
OSSMaintNotificationsHandlerprovides thread-safe management of maintenance notifications with automatic expiration cleanupParser Integration: Seamless integration with existing parser infrastructure to recognize and route OSS maintenance notifications
Testing: Full unit test coverage for all notification classes ensuring proper behavior across initialization, equality, hashing, and collection operations
Out of scope for the current PR: initializing the nodes manager handler that will react on SMIGRATED notifications.