![]() ![]() For machine-level repairs you do not need either of these if you want to automatically schedule machine repair jobs based on node health states alone (like, Error state, specifically). Note that you can use FabricHealer if you don't also employ FabricObserver or FabricHealerProxy. Repair workflow starts when FabricHealer detects supported error or warning health events reported by FabricObserver or FabricHealerProxy, for example. ![]() Repair workflow configuration is written as Prolog-like logic with supporting external predicates written in C#.įabricHealer's Configuration-as-Logic feature requires Guan, a Prolog-like logic programming library for. All repairs are safely orchestrated through the Service Fabric RepairManager system service. ![]() These repairs mostly employ a set of Service Fabric API calls,īut can also be fully customizable (like Disk repair). NET 6 Service Fabric application that attempts to automatically fix a set of reliably solvable problems that can take place in Service FabricĪpplications (including containers), host virtual machines, and logical disks (scoped to space usage problems only). FabricHealer 1.2.11 Configuration as Logic and auto-mitigation in Service Fabric clustersįabricHealer (FH) is a. ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |