Hello, Basically this is a mechanism to implement custom logical/network split-brain protection. Segmentation resolvers allow you to implement a way to determine if node has to be segmented/stopped/etc in method isValidSegment() and possibly use different combinations of resolvers within processor.
If you want to check out how it could be done, some articles/source samples that might give you a good insight may be easily found on the web, like: https://medium.com/@aamargajbhiye/how-to-handle-network-segmentation-in-apache-ignite-35dc5fa6f239 http://apache-ignite-users.70518.x6.nabble.com/Segmentation-Plugin-blog-or-article-td27955.html 2-3 are described in the documentation, copying the link just to point out which one: https://apacheignite.readme.io/docs/critical-failures-handling By default answer to 2 is: Ignite doesn't ignote node FailureType SEGMENTATION and calls the failure handler in this case. Actions that are taken are defined in failure handler. AbstractFailureHandler class has only SYSTEM_WORKER_BLOCKED and SYSTEM_CRITICAL_OPERATION_TIMEOUT ignored by default. However, you might override the failure handler and call .setIgnoredFailureTypes(). Links: Extend this class: https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/failure/AbstractFailureHandler.java — check for custom implementations used in Ignite tests and how they are used. Sample from tests: https://github.com/apache/ignite/blob/master/modules/core/src/test/java/org/apache/ignite/failure/SystemWorkersBlockingTest.java Failure processor: https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/internal/processors/failure/FailureProcessor.java Best regards, Anton -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
